Document "Payment from Buyer by Payment Card" - Technical Description (BK 3.0.74.2)

1. Identification of the Object

Purpose. The document registers the receipt of funds from customers when paying for goods and services by card through acquiring (POS) terminals. It reflects settlements with the customer, the commission withheld by the bank (merchant discount of the acquirer), the offset of advances, and interacts with fiscal equipment for printing receipts if necessary. The main users are cashiers and accountants of retail outlets and service enterprises working with cashless cards. All amounts are recorded in tenge (₸).

2. Header Attributes and Table Parts

2.1 Mandatory Header Attributes

If any of the listed attributes are not filled in, the platform will not process the document and will display the message “Field … is not filled in”.

2.2 Table Part “PaymentBreakdown”

Breaks down the total amount by specific customers and settlement agreements.

The settlement currency rate cannot be selected until the agreement is filled in: if an attempt is made to select without filling in CounterpartyAgreement, the message “To select the settlement currency rate, you need to select the counterparty agreement” will be displayed.

3. Forms

4. Key Module Procedures

4.1 From evidence (document form)

• Form.DocumentForm → handler PaymentBreakdownSettlementCurrencyRateStartSelection — controls the selection of the settlement currency rate in the table part: if NOT ValueFilled(CurrentData.CounterpartyAgreement), it interrupts the selection and displays the message “To select the settlement currency rate, you need to select the counterparty agreement”.

4.2 Standard Handlers for Documents of This Type (Object Module)

• FillHandler — fills in attributes when entering based on (sales document/invoice), transfers customer, agreement, amount.
• CheckFillHandler — controls mandatory header attributes and columns of “PaymentBreakdown” before recording.
• PostingHandler — generates movements in registers (see section 5); calculates the merchant discount based on the terms of AcquiringAgreement.
• DeletePostingHandler — clears generated movements when canceling posting.

“Requires verification”: the exact composition of export procedures of the object module is version-dependent and may change between releases — when refining, refer to the module of the specific delivery 3.0.74.2.

5. Posting and Movements

When posted, the document generates movements in the accounting and tax registers, as well as in the payment accumulation register. Accounts are provided according to the standard chart of accounts of the RK.

5.1 Accounting Register “Standard”

After the net amount is credited to the current account by the bank, the closure of account 57.XX is performed by the bank statement entry Dr 1030 (money in current accounts) — Cr 57.XX.

5.2 Tax Accounting Register “Tax”

Generates similar monetary movements for CIT accounting if the document TaxAccountingType/ConsiderCIT = True. Income and expenses (merchant discount) are reflected in tax accounting for the same amounts as in BA.

5.3 Accumulation Register “PaymentOfInvoices”

• Receipt — registration of the fact of payment by invoice/sales document indicating the amount and VAT rate (the VAT rate of the RK for 2026 is 16%).

5.4 VAT and Electronic Documents

The payment document itself does not accrue VAT — the VAT obligation arises upon sale. The accrued VAT is reflected in account 3130 (VAT payable), taxable sale — in 6010, cost of goods sold — 7010 / 1330. For sales secured by payment, electronic documents ESF (in the ESF IS) and when moving goods — SNT are issued.

6. Related Objects and Entry Based On

Can be entered based on:

• Document of sale of goods and services (registration of payment by invoice);
• Invoice for payment to the customer.

Related Objects:

• Directories Counterparties, CounterpartyAgreements, Organizations;
• Acquiring agreement and directory of acquirers (banks);
• Documents of bank statements (closure of account 57.XX with receipt on 1030);
• Documents of sales and electronic documents ESF / SNT;
• Accumulation register “PaymentOfInvoices” (linking payment with source documents).

Typical Scenarios:

1. Registration of payment by card during the sale of goods (through POS terminal).
2. Direct payment by card without source document (payment for service at the time of provision).
3. Change of payment amount with recalculation of merchant discount (partial payment/correction).
4. Refund of payment to the customer’s card (when returning goods).
5. Group change of payment documents (for example, changing the acquiring agreement for all payments for the day).

7. Extension Points

• Object Module — overriding FillHandler, CheckFillHandler, PostingHandler (adjustment of merchant discount calculation, additional analytics for account 57.XX).
• Document Form — extension of handlers PaymentBreakdownSettlementCurrencyRateStartSelection and events for filling agreements/rates, adding custom checks.
• Event Subscriptions (BeforeRecording/OnPosting of the document) — integration with external fiscal equipment and accounting add-ons.
• Additional Attributes and Information — “Properties” mechanism for extending analytics without changing metadata.
• Configuration Extensions — adding attributes, forms, and handlers without removing the standard configuration from support.

“Requires verification”: the availability of specific subscriptions and names of predefined procedures depends on the release; when implementing extensions in 3.0.74.2, refer to the composition of the object in the current delivery.