Document "PaymentOrderReceiptOfFunds" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document records the receipt of funds into the organization's settlement (current bank) account from counterparties, banks, and third parties. It is used daily when processing a bank statement to reflect incoming payments on various grounds: payment from a buyer, refund of an advance from a supplier, receipt of a loan, cash collection, purchase/sale of currency. It is the main tool of bank accounting for receipts: it generates movements in the accounting and tax accounting registers, and also records payment of issued invoices. All amounts are in tenge (₸); accounting is maintained according to the standard chart of accounts of the RK.

2. Header attributes and tabular sections

2.1 Header attributes

Required for posting (if left blank, 1C displays "Field … is not filled in"):

Other standard header attributes: Дата, Номер, СтруктурноеПодразделение, СтатьяДвиженияДенежныхСредств (cash flow analytics), Комментарий, Ответственный, incoming bank details (number and date of the payer's payment document).

2.2 "РасшифровкаПлатежа" (Payment breakdown) tabular section

Allows the document amount to be distributed across several contracts/grounds.

All listed columns are required: if left blank, the document is not posted.

Additionally, a line may carry a reference to an Invoice for payment — used to control payment of issued invoices (see the ОплатаСчетов register in section 5).

3. Forms

The set of visible fields on the document form is controlled by the operation type: the set of attributes and columns dynamically changes to suit the selected scheme (for example, for currency purchase, currency account fields are added; for cash collection, details of the RKO basis).

4. Key module procedures

Code references are given for release 3.0.68.1 (configuration evidence); in 3.0.74.2 the handler names and conditions are preserved, line numbers may differ — requires verification when precisely binding to a line.

Manager module

• ЗаполнитьПоДокументуОснованию — filling in attributes when entering on the basis of another document. For the "Cash collection" operation type, it controls the source: the document is entered only on the basis of a Cash disbursement order with the operation type "Cash collection of funds". Otherwise, an error is displayed:

  "A payment order is entered only on the basis of a cash disbursement order with the operation type 'Cash collection of funds'" Condition: НЕ ДокументОснование.ВидОперации = Перечисления.ВидыОперацийРКО.ИнкассацияДенежныхСредств.

Object module

• ОбработкаПроверкиЗаполнения — reconciles the tabular section total with the document amount. In case of a discrepancy:

  "The document amount and its breakdown do not match" Condition: РасшифровкаПлатежа.Итог("СуммаПлатежа") <> СуммаДокумента.

• ПроверитьЗаполнениеТабличнойЧастиПострочно — line-by-line control of correct filling (including matching the contract currency to the document currency):

  "Contract currency %1 …"

• ОбработкаПроведения (standard handler) — generates movements in the registers (see section 5) depending on ВидОперации.

Form module

• Standard handlers: ПриСозданииНаСервере, ВидОперацииПриИзменении (rebuilding field visibility for the operation type), ПриИзмененииСуммыДокумента/РасшифровкаПлатежаПриИзменении (recalculation and amount control), account and contract selection handlers.

5. Posting and movements

When posted, the document generates movements in the registers depending on ВидОперации. Posting analytics: Organization, Structural unit, Counterparty, Contract, Cash flow item.

5.1 "Standard" accounting register (RK chart of accounts)

Note on accounts. In the standard RK chart of accounts, 1210 is short-term accounts receivable from buyers, 3310 is short-term accounts payable to suppliers. In the evidence these labels are in places given inaccurately; in the description the accounts are indicated in accordance with the current RK chart of accounts.

5.2 "Tax" accounting register

Similar postings are generated for tax accounting on the accounts of the "Tax" chart of accounts (the СчетУчетаРасчетовСКонтрагентомНУ, ВидУчетаНУ attributes are used).

5.3 "ОплатаСчетов" (Invoice payment) accumulation register

Records the fact of payment of an invoice for payment (receipt):

• СчетНаОплату — the invoice document from the breakdown line;
• СуммаОплаты — the amount from the line.

Used to control payment of issued invoices.

This document is a bank cash flow operation: it does not generate movements for VAT and IIT. The RK tax rates of 2026 (VAT 16%, IIT 10%/15%, basic deduction of 30 MCI at MCI = 4,325 ₸) do not apply to the postings of the payment order.

6. Related objects and entry on the basis

Entry bases (incoming):

• Cash disbursement order (operation type "Cash collection of funds") → receipt payment order for the "Cash collection" operation.
• Invoice for payment to buyer → filling in the payment breakdown and linking to the ОплатаСчетов register.

Related objects:

• Catalogs: Организации, Контрагенты, ДоговорыКонтрагентов, БанковскиеСчета, Валюты, СтатьиДвиженияДенежныхСредств, ПланСчетовБухгалтерского(Налогового)Учета.
• Enumerations: ВидыОперацийРКО (checking the cash-collection basis), the enumeration of receipt operation types.
• RK electronic documents (ESF in the IS ESF, SNT) are linked to sales/receipt documents, not directly to the payment order; the fact of payment is used for subsequent matching.

Entry on the basis (outgoing): typically, from the document, a transition to interrelated settlement documents is possible; the specific set of entry-on-the-basis commands — requires verification in the configurator of version 3.0.74.2.

7. Extension points

• Configuration extensions (Extensions): overriding/supplementing the ОбработкаПроверкиЗаполнения, ОбработкаПроведения, ЗаполнитьПоДокументуОснованию handlers for custom control and filling logic.
• Event subscriptions (ПередЗаписью, ПриЗаписи, ОбработкаПроведения) — for integration with external systems (client-bank, statement exchange).
• Additional attributes and information (SSL mechanism) — extending the header without changing metadata.
• Bank statement import / DirectBank — automatic creation of the document from the client-bank; an extension point for non-standard exchange formats.
• Additional data processors/commands (address extension, additional reports and data processors of the SSL) — for adding commands to the document and list forms.
• Exchange rules (CD 2/3, EnterpriseData) — synchronization of the document with other databases.