Document "Incoming Payment Order" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document registers the receipt of cashless funds to the organization's bank accounts in Kazakh accounting. It is used by accountants and treasurers daily when processing bank statements to reflect:

• payments from customers (according to the invoice or sale);
• refunds from suppliers (previously issued advance, overpayment);
• sale/purchase of foreign currency;
• refunds of mandatory pension contributions (MPC), social deductions (SD), wages, unified payments, other payments;
• internal transfers between departments.

Where to find in 1C: section “Bank and Cash” → “Incoming Payment Orders” → “Create”. Navigation link: e1cib/list/Document.IncomingPaymentOrder.

2. Attributes of the Header and Table Parts

2.1 Mandatory Attributes of the Header

2.2 Table Part “PaymentBreakdown”

Line-by-line breakdown of the receipt by contracts/documents of settlements.

2.3 Table Parts for Returns from Funds/Salaries

For operation types “refund …” the identically named table parts are used, each with columns Document (document-basis for accrual) and RefundAmount:

If a mandatory header/line field is not filled, the platform will not process the document and will display “Field … is not filled”.

3. Forms

4. Key Procedures of Modules (from evidence)

Object Module (ObjectModule)

• ProcessingConduct (≈76 lines). Calls PrepareConductParameters from the manager module, then generates movements through the universal mechanism ConductParameters. A single point of calculation of movements for all types of operations.
• CheckFillingProcessing. Controls the correctness of table parts before processing. In particular, when refunding other payments, it blocks the mixing of different types of payments in one document:

  “In the table part 'Lists for refunding other payments' there are statements with various types of other payments: … it is not possible to perform a refund with one document for different types of other payments” (condition: QueryResult.Count() > 1).

• CheckTablePartFillingLineByLine. Line-by-line check of currency compliance; in case of non-compliance — a message of the form “Currency of the contract %1”.

Manager Module

• PrepareConductParameters. Forms a set of conduct parameters (accounts, amounts, subaccounts, fund analytics, rates) — server logic extracted from the object module.

The texts of messages are quoted verbatim from the code (release 3.0.68.1). In 3.0.74.2, the formulations are identical in meaning — requires verification only the exact wording when working with the error handler.

5. Processing and Movements

ProcessingConduct generates movements across a set of registers depending on OperationType.

5.1 Accounting (register “Economic”, accounting plan BU RK)

Basic entry of receipt:

Debit BankAccount  —  Credit CounterpartyAccountingAccountBU
Subaccount Credit: Counterparty, Contract, Settlement Document

Examples according to the RK chart of accounts:

5.2 Tax Accounting

When ConsiderKPN = True, similar movements are generated according to the NU chart of accounts (tax accounting register), using CounterpartyAccountingAccountNU and TaxAccountingType.

5.3 Other Registers

5.4 VAT and Electronic Documents

The mere fact of receipt of funds does not accrue VAT — VAT is reflected in sales/receipt documents. At the same time, the incoming payment closes settlements related to sales for which VAT has been accounted at the current rate of RK 16% (2026), account 3130 “VAT payable”. Sales, the payment of which is registered by the document, are accompanied by electronic invoices (ESF) and, if necessary, SNF; the incoming payment of its own electronic documents does not generate, but participates in closing settlements for them.

For reference, accounts of related sales: 6010 “Revenue from sales”, 7010 “Cost of sales”, 1330 “Goods”.

6. Related Objects and Input Based on

• Input grounds: “Invoice to customer”, “Sale of goods and services”, “Withdrawal from current account” (for refunds) — fill in counterparty, contract, settlement accounts, and amounts.
• Bank statement: the document is uploaded/created from the bank statement processing (Client-bank, DirectBank).
• Counterparty Contracts, Bank Accounts, Organizations — sources of analytics.
• Documents of funds/salaries — sources of lines in the table parts of refunds.
• The document is a basis for settlements and participates in reports “Turnover and balance sheet for account 1210/1610”, “Analysis of subaccount Counterparties”.

7. Extension Points

• Manager module → PrepareConductParameters — preferred point for fine-tuning accounts/analytics of conduct without modifying the object module.
• ProcessingConduct (configuration extension) — adding custom movements (for example, to management registers).
• CheckFillingProcessing — adding industry checks for filling.
• Forms (DocumentForm) — extending handlers OnChange of the attribute OperationType to manage the visibility of table parts.
• Event subscriptions (BeforeWriting/OnWriting) — integration with external treasury systems.
• Mechanism ConductParameters — overriding the composition of registers through standard library logic of conduct.