Reference Guide "Types of Payment Acquiring" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog is intended for classifying types of cashless payments processed through the acquiring system (bank card acceptance terminals, QR codes, mobile payments, etc.). It allows for the separation of receipts by payment systems (Visa, MasterCard, "MIR", local QR services) and by payment method (card at the terminal, mobile payment) for accurate accounting of the acquiring bank's commission and sales analytics. The catalog is maintained by accountants and cashiers of organizations that use electronic payments from customers: it is filled out once during the setup of cash registers and retail outlets, after which it is used automatically during acquiring operations.

Where to find in 1C: section "Bank and Cash" → "Types of Acquiring Payments". Also available from the "Catalogs" section and from selection forms in payment documents by bank cards.

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes of the catalog (present in all hierarchical catalogs, not explicitly listed among own attributes):

2.2 Table Parts

Table parts are absent. The catalog has a simple structure: one additional attribute MobilePayment on top of the standard set.

3. Forms

The catalog contains 5 forms:

4. Key Module Procedures

The attached evidence does not include software modules (BSL texts), so below are typical handlers characteristic of a hierarchical catalog of this structure. Requires verification in the specific version 3.0.74.2 — the presence and content of the handlers below (not confirmed in evidence).

Object Module (CatalogObject.PaymentTypesAcquiring):

• FillProcessing(FillingData, ...) — filling in the attributes of a new element by default (including the value MobilePayment = False).
• CheckFillProcessing(Refusal, CheckedAttributes) — control of filling mandatory fields. The MobilePayment attribute is excluded from the check (DontCheck).
• BeforeWriting(Refusal) / OnCopy(CopyObject) — standard pre-writing logic.

Forms (ElementForm, ListForm):

• OnCreateOnServer(Refusal, StandardProcessing) — setting conditional formatting and visibility of form elements.
• Handler for the command "ModifySelected" in ListForm — bulk modification of attributes (including the MobilePayment attribute) for selected rows in the list.

The catalog does not contain its own business logic for processing — as a catalog, it does not perform movements independently (see section 5).

5. Processing and Movements

The catalog is not a document and does not independently generate movements in registers. It serves as analytics (attribute value) in documents and registers reflecting acquiring operations. Below is the standard logic of application in the chart of accounts of the RK.

5.1 Where Used as Analytics

• In documents for payment by bank card / reports on retail sales — attribute "Payment Type (Acquiring)".
• In settings for acquiring terminals and retail outlets — for matching the payment system and the acquiring agreement with the bank.

5.2 Typical Entries for Acquiring Operations (Chart of Accounts RK)

Payment by the customer with a card through a POS terminal (revenue not yet credited by the bank):

Bank crediting of revenue minus the acquiring commission:

Sale of goods paid for by card (retail):

VAT in the examples is at the rate of 16% (Kazakhstan, 2026). The analytics PaymentTypesAcquiring enters the movements of the corresponding documents as a measure/subaccount of settlements on acquiring, ensuring separate accounting of receipts and commissions for each payment system.

5.3 Electronic Documents

Sales made with card payment are accompanied by electronic invoices (ESF) (electronic invoice, ESF IS) and SNT (when moving/turning traceable goods) if necessary. The catalog itself does not participate in the formation of ESF/SNT, but the related sales document does.

6. Related Objects and Input Based On

• Documents for payment by bank cards / report on retail sales — use the catalog element as the value of the "Payment Type" attribute.
• Acquiring settings (trade equipment, agreements with the acquiring bank) — match the payment type with a specific terminal and agreement.
• Registers of settlements on acquiring — use the payment type as a measure for separate accounting of receipts and commissions.

Input based on this catalog is generally not provided (the catalog is a classifier-analytics, not a source of documents). It is filled in manually by the user through ElementForm/GroupForm.

7. Extension Points

• Configuration extension: adding custom attributes (e.g., "Default acquiring agreement", "Commission accounting account", "Payment system") and columns in ListForm/ElementForm without removing from support — through extension.
• Event subscriptions: BeforeWriting/OnWriting of the object for controlling the uniqueness of payment system names or auto-filling the group based on the MobilePayment attribute.
• Additional attributes and information: connection through the properties subsystem (characteristics plans) for storing non-regulated attributes without changing metadata.
• Handler for the "ModifySelected" command in ListForm — point for mass servicing of elements.
• Programmatic use: referencing the MobilePayment attribute in reports and algorithms for parsing acquiring receipts for separate analytics on mobile payments.