1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | ReturnStatementForOtherPayments |
| Full Name | Document.ReturnStatementForOtherPayments |
| Synonym | Return statement for other payments |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Main Section | “Payroll” (accounting for settlements with personnel) |
Purpose. The document is intended for accounting the return of funds from individuals to the organization for previously transferred other payments (social, compensatory, one-time, etc.). It is used when an employee has been overpaid or there is a need to return the payment for other reasons. The document is usually prepared by the accountant-calculator based on the “Statement for the Transfer of Other Payments,” after which it is linked to the incoming payment order (actual receipt of money through the bank).
Key Feature. The document is reference-distribution: it does not independently generate movements in the registers (see section 5). It records which individuals, for which period, and in what amount the return is expected/made for a specific type of other payments, and serves as the basis for the banking document.
Where to find in 1C: section “Payroll” → “Return statement for other payments”.
Navigation link: e1cib/list/Document.ReturnStatementForOtherPayments
2. Header Attributes and Table Parts
2.1 Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Organization |
The organization on behalf of which the accounting of settlements is conducted and to which funds are returned. | Mandatory |
TypeOfOtherPayments |
The type of other payment (social, compensatory, one-time, etc.) for which the return is made. Determines the analytics of settlements. | Mandatory |
Date |
The date of the document (standard attribute), determines the moment in the chronology of settlements. | Automatically filled |
Number |
The document number (standard attribute), assigned by the numbering system. | Automatically |
Responsible |
The user responsible for the document (used in the scenario of group changes). | Optional |
OrganizationSubdivision / Subdivision |
The structural subdivision (used in the scenario of group changes). | Optional |
Comment |
Arbitrary text comment. | Optional |
2.2 Table Part “OtherPayments”
The main table part containing a line-by-line breakdown of the return by individuals.
| Column | Purpose | Mandatory |
|---|---|---|
Individual |
The individual returning funds to the organization. | Mandatory |
SettlementPeriod |
The period (month) of settlements to which the returned amount relates. Ensures correct linking to the period of accrual/transfer. | Mandatory |
Amount |
The return amount for the line, in tenge (₸). | Mandatory |
If any of the listed mandatory fields are not filled, the platform will not allow the document to be processed and will issue an error of the type “Field … is not filled”.
3. Forms
For documents of this type, the standard configuration provides the following set of forms:
| Form | Purpose |
|---|---|
Document Form (DocumentForm) |
The main editing form: header (Organization, Type of other payments) and table part “OtherPayments”. Contains commands for filling, selecting individuals, and creating related documents. |
List Form (ListForm) |
A list of all return statements filtered by organization, type of payments, period. Opens via navigation link e1cib/list/Document.ReturnStatementForOtherPayments. |
Select Form (SelectForm) |
Used when selecting a document as a value of an attribute in other objects (for example, when linking from an incoming payment order). |
The specific composition of managed forms and the presence of auxiliary forms (for example, the group change of attributes is called by the standard processing “Group Change of Attributes”) is version-specific — requires verification in the specific delivery 3.0.74.2.
4. Key Procedures of Modules
Evidence with BSL export (path: line) for this object is not attached, so below is a typical set of handlers for the object module and form module for documents of this type.
Object Module:
FillProcessing(FillingData, ...)— filling during input based on (for example, from “Statement for the Transfer of Other Payments” Organization, Type of other payments, and lines of the table part with individuals and amounts are transferred).CheckFillingProcessing(Refusal, CheckedAttributes)— control of filling mandatory fields (Organization,TypeOfOtherPayments, as well asIndividual,SettlementPeriod,Amountin lines). If not filled — refusal with a message.ConductProcessing(Refusal, ConductingMode)— for this document, the body does not actually generate movements (the list of movements is empty), as the document is reference-distribution (see section 5).
Form Module:
OnCreateOnServer(Refusal, StandardProcessing)— initial form initialization, setting visibility and availability of elements.FillByDebt(...)— command to fill the table part by the actual debt of individuals to the organization for the selected type of other payments (scenario 3.2).- Handlers for commands to create/link with the incoming payment order (scenario 3.3).
Exact names, signatures, and coordinates of procedures — require verification by the configurator version 3.0.74.2 (evidence BSL not provided).
5. Conducting and Movements
The document does not independently generate entries and movements in the registers — in the metadata, the set of registrars (register_records) is empty. This is confirmed by the reference-distribution nature of the object: it records the planned/actual structure of the return by individuals, but accounting entries and movements in the registers of settlements are generated in the related incoming payment order.
Therefore, there are no “entries of this document.” For completeness, below is how the return of funds is reflected in the related banking document according to the standard Chart of Accounts of the RK:
- Receipt of money from an individual to the organization's current account (incoming payment order / receipt to the settlement account):
- Debit 1030 (money in current accounts) — Credit of the account of settlements with the individual for other payments (analytics — individual, type of other payments).
Specific amounts are taken from the lines of the table part of the statement in tenge (₸). The return statement does not generate any tax movements (individual income tax, social tax, etc.) — it only corrects settlements for the type of other payments.
For reference, the current parameters for the RK 2026 calculation (used in documents of accrual/transfer, not here): VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for individual income tax 30 MRP/month (not more than 360 MRP/year), individual income tax 10% up to 8,500 MRP annual income and 15% above, social tax 10% (base ceiling 50 MSP), social tax rate 3.5%, etc.
6. Related Objects and Input Based On
Input based on (the document is created based on):
- Statement for the Transfer of Other Payments — the main scenario (3.1): when an error is found in the transfer amount or the need to return previously paid. When inputting based on, Organization, Type of other payments, and lines with individuals/amounts are transferred.
Related documents (created based on the return statement or linked to it):
- Incoming Payment Order — records the actual receipt of money from individuals through the bank (scenario 3.3); it is the one that generates movements (Debit 1030).
General Mechanisms:
- Group Change of Attributes (scenario 3.4) — mass change of
Responsible,Subdivision, etc. for the selection of statements. - Copying (scenario 3.5) — creating a new statement based on an existing one while preserving the structure.
Analytical Objects (directories) involved in attributes:
Directory.OrganizationsDirectory.Individuals- Directory/list of types of other payments (analytics
TypeOfOtherPayments).
7. Extension Points
- Configuration Extension (adopt/&Insert/&Instead): adding handlers
CheckFillingProcessing,FillProcessingwithout removing from support — for additional validation rules for return amounts or restrictions on the type of other payments. - Event Subscriptions:
BeforeWriting,OnWritingof the document — for integration with external systems or additional logging of returns. - Additional Attributes and Information (property mechanism
PlanOfCharacteristicTypes) — adding custom analytics without changing the object's metadata. - Form Attributes / Document Form Extension — adding custom filling commands (for example, loading debt from an external source), columns, and checks in the form.
- Additional Reports and Processes (external) assigned to this document — for group formation, printing, and export.
- Since the document does not generate movements, it is impractical to extend the conducting logic; custom accounting logic should be placed in the related incoming payment order.