Document "Statement for the Transfer of Other Payments" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document generates a statement for the transfer of other payments to the organization's employees — payments that are not related to the main salary (material assistance, compensations, one-time and irregular payments, etc.). It is used by accountants and payroll specialists to prepare a list of amounts to be transferred to the accounts of individuals. The document serves as a basis for creating payment orders for bank transfers and, according to the standard logic of the configuration, acts as a register/list for controlling payments, rather than a source of accounting entries (see section 5). It is used monthly or as needed.

Where to find in 1C: section “Payroll” → “Statement on the transfer of other payments”. Navigation link: e1cib/list/Document.StatementOnTransferOfOtherPayments

2. Attributes of Header and Table Parts

Header Attributes

Table Part “OtherPayments”

If at least one of the mandatory attributes is not filled, the platform will not allow the document to be processed and will display the error “Field … is not filled”.

3. Forms

The standard set of forms for documents of this type:

4. Key Procedures of Modules

The provided evidence does not include the source code of the modules (BSL) with exact addresses path:string. Below are typical handlers characteristic of this type of document in BK 3.0; specific procedure names should be clarified according to the module of the form/object of the specific version.

Document Form Module:

• OnCreationOnServer — initial initialization, substitution of the default organization, visibility settings.
• Handler for the “Fill” command — automatic filling of the table part by debt for SettlementPeriod according to MethodOfCalculationOfAmountsToBeTransferred (scenario 3.2).
• Handler for the “Select” command — opening the form for selecting individuals from the directory and adding them to the table part (scenario 3.4).
• Table part event handlers (OtherPaymentsIndividualOnChange etc.) — recalculation and filling of dependent columns of the line.

Object Module:

• FillProcessing — filling when inputting based on / from accrual data.
• CheckFillProcessing — control of filling mandatory attributes (TypeOfOtherPayments, Organization, SettlementPeriod, MethodOfCalculationOfAmountsToBeTransferred, as well as Individual and SettlementPeriod in lines).
• ConductingProcessing — not present in the provided modules (see section 5).

5. Conducting and Movements

Important feature. According to the metadata, the document does not contain conducting processing — the array of registrars (register_records) is empty. This means that the statement itself does not generate accounting entries and does not make movements in accumulation/summary registers. Its function is a register/list for transfer and a basis document.

The actual movements are performed by the payment order (outgoing), created based on the statement. It is this document that, when funds are withdrawn, generates the entry for the transfer of money to individuals according to the standard chart of accounts of the RK:

• Debit 3350 “Short-term liabilities for labor payment” (or another account for settlements with personnel for other payments) — Credit 1030 “Cash in current bank accounts” — for the amount of the transfer.

“Requires verification”: the specific debited account for settlements with individuals for other payments depends on the configuration of TypeOfOtherPayments and the accounting policy of the organization in the specific database.

For reference, the parameters relevant for the RK in 2026 that may participate in the calculation of related payroll accruals (but not in the statement itself):

6. Related Objects and Input Based On

Data sources (filling the statement):

• Directory Individuals — recipients of payments (selection in the table part).
• Accruals of other payments for SettlementPeriod — basis for auto-filling by debt.

Input based on (the document acts as a basis):

• Outgoing payment order — bank document for transferring funds to individuals (scenario 3.3). It is this document that performs movements in the registers and the entry Debit for settlements with personnel / Credit 1030.

Typical work scenarios:

1. Creating a new statement manually — one-time/irregular payments.
2. Automatic filling by debt — regular payments for already accrued amounts.
3. Creating a payment order based on the statement — after approval.
4. Selecting individuals in the table part — during manual formation.
5. Editing an existing statement — adjusting amounts/composition before conducting.

Electronic documents (RK). The statement itself is not related to the ESF (ESF IS) and SCT — these documents pertain to the sale/movement of goods, not to the transfer of payments to individuals.

7. Extension Points

• Configuration extensions for the document form: adding attributes/columns (e.g., additional analytics by types of payments), custom filling commands, and printed forms without removing from support.
• Event subscriptions (FillProcessing, BeforeSaving, OnSaving) — for integration with external payment registers and validation of amounts.
• Redefining the auto-fill algorithm through MethodOfCalculationOfAmountsToBeTransferred — adding custom methods for calculating amounts to be transferred.
• Input based on — expanding the composition of documents created based on the statement (e.g., custom regulatory documents).
• Additional attributes and information (mechanism of common attributes/additional information) — for storing signs without changing metadata.

“Requires verification”: the exact composition of built-in filling commands and names of module procedures is version-specific; verify with the document module in database 3.0.74.2.