Reference Guide "Acquiring Agreements" (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. The catalog stores information about acquiring contracts — agreements between an organization and an acquiring bank for providing services for accepting cashless payments from customers through payment terminals and bank cards. It is used by accountants and cashiers when setting up points of sale and processing transactions for cashless payment of goods and services. The catalog element links the acquirer (bank), the settlement agreement, the connected equipment (terminal), and the bank's commission rates for servicing. This is a basic element of the accounting system for the correct reflection of settlements through acquiring and the calculation of bank commissions.

Where to find in 1C: section "Bank and Cash" → "Acquiring Contracts". Navigation link: e1cib/list/Catalog.AcquiringContracts

2. Attributes and Table Parts

2.1 Header Attributes

The standard attributes of the catalog (Code, Name, DeletionMark, Predefined) are present in the overall composition.

2.2 Table Parts

TariffsForSettlementService

Purpose: stores the commission rates of the acquiring bank depending on the type of payment instrument (debit card, credit card, corporate card, etc.).

3. Forms

4. Key Module Procedures

The attached evidence程 BSL code (paths and lines) is not provided, so below are typical handlers characteristic of a catalog of this type in configurations on BSP. Specific procedure names in your version require verification according to the object modules.

Object Module (FillHandler, CheckFillHandler, BeforeSave):

• FillHandler — pre-filling attributes when creating a new element (for example, substituting the acquirer/agreement from the passed fill parameter).
• CheckFillHandler — control of filling mandatory attributes Acquirer and SettlementAgreement (the mandatory property ShowError already sets the platform check); additional check for the consistency of the rows in the table TariffsForSettlementService (uniqueness of PaymentType, correctness of the percentage).
• BeforeSave — service logic before saving (normalization of the name, control of duplicates by the acquirer + agreement pair).

Element Form Module:

• OnCreateOnServer — setting visibility and availability of fields; in particular, managing the availability of the attribute ConnectedEquipment depending on the flag UseWithoutConnectedEquipment.
• Event handler UseWithoutConnectedEquipmentOnChange — when the flag is set, clears/makes the field ConnectedEquipment unavailable.
• AcquirerOnChange / SettlementAgreementOnChange — agreement coordination with the selected counterparty-acquirer (filtering agreements by counterparty).
• Event handlers for the tariff table (TariffsForSettlementServiceOnChange, ...PaymentTypeOnChange) — control of duplication of payment types.

5. Posting and Movements

The catalog is not a document and does not independently generate movements in registers — the catalog has no posting procedure. It serves as analytics (conditionally permanent information) on which payment documents and acquiring settings rely.

Movements are generated by documents that reference an element of this catalog (payment by card, retail sales report, receipt to the current account for acquiring). Below is the standard logic for reflecting an acquiring operation according to the typical chart of accounts of the RK.

1. Customer payment by card through the terminal (transaction amount, for example, 116,000 ₸, including VAT 16%):

Settlements for acquiring before receiving money from the bank are accounted for on the sub-account of settlements "in transit" (analytics — acquirer and agreement from the catalog AcquiringContracts).

2. Receipt of funds from the acquiring bank minus the trade discount (commission on TradeDiscountPercentage, for example, 1.5% = 1,740 ₸):

The account for accounting the commission depends on the accounting policy (period expenses 7210 or cost 7010); in the typical accounting for the RK, the acquiring commission is charged to expenses. The exact sub-account requires verification in your setup.

Analytics of movements. The element AcquiringContracts determines: the counterparty-acquirer and the settlement agreement (for sub-account settlements), the trade discount percentage (for calculating the commission amount), as well as the terminal (ConnectedEquipment) for matching operations with the point of sale.

Sales are subject to VAT at the current rate of 16% (Kazakhstan, 2026). Electronic registration of sales — electronic invoice (ESF) (ESF IS) and, if necessary, SNF; the acquiring contract itself does not generate electronic documents but serves as a source of analytics for retail/cashless sales.

6. Related Objects and Input on Basis

References to (attributes):

• Catalog.Counterparties — acquirer;
• Catalog.CounterpartyContracts — settlement agreement;
• Catalog.ConnectedEquipment — terminal;
• Catalog.PaymentTypesForAcquiring — payment type in the tariff table.

Used in (typical consumers):

• payment documents by card / acquiring operations;
• retail sales documents (retail sales report) and settings for cash registers/points of sale;
• documents for receipt of funds to the current account for acquiring;
• exchange with connected trading equipment (terminals).

Input on basis. For the catalog, input on basis is not typically provided (the catalog is analytics, not a document). The element is usually selected in payment documents, not created "on the basis of".

7. Extension Points

• Configuration extension (Extensions): adding custom attributes (for example, transfer period, merchant number/MID, operation limit) and columns in the table TariffsForSettlementService without removing from support.
• Event subscriptions (BeforeSave, OnSave) — for controlling duplicates of contracts or synchronization with an external payment system.
• Redefinable BSP modules — integration with the "Connected Equipment" subsystem for new terminal models.
• Element form module — adding service checks and auto-filling through extending event handler procedures.
• Additional attributes and information (subsystem "Properties") — if the object has support for PVC/sets of additional properties enabled, attributes can be added without changing metadata.

Version-specific details (exact procedure names in modules, composition of additional attributes, account for commission) require verification in the specific delivery 3.0.74.2.