Report "Statement of Settlements with Individuals" (Accounting for Kazakhstan 3.0)

1. Identification of the Object

Purpose. The report generates a reference on the mutual settlements of the organization (taxpayer) with a specific individual for the selected period: it summarizes the accrued and paid amounts, withholdings, and the current state of settlements (opening balance → turnovers → closing balance). The reference can be conveniently issued to the individual for reconciliation or used internally within the organization during the inventory of settlements with individuals.

Users: accountants and calculators. The report is generated upon request — when an individual applies, during reconciliation, or at the end of the period.

Important: this is an analytical report “for reading only.” It does not conduct or record anything in the information database, does not generate entries or movements in registers. A specific individual is specified through selections (settings) of the report; there is no separate header attribute for selecting an individual, and the parameter Taxpayer indicates the organization from which the settlements are conducted.

2. Attributes of the Header and Table Parts

2.1 Header Attributes (DCS Parameters)

All attributes are report configuration parameters. None are marked as mandatory at the metadata level (fill_value_required = DontCheck).

2.2 Table Parts

Table Part Indicators

Configuration table of indicators in DCS: determines which summary/analytical indicators are displayed in the reference (for example, accrued, paid, withheld, balance). The specific list is formed by the composition scheme and is not fixed by name in the object card.

3. Forms

The object card has an empty list of forms (metadata.forms = []). The user has access to the standard report form in DCS (standard name of the platform — ReportForm) with a period field, settings panel (selections, indicators), and generation commands.

The exact name of the main form is not fixed in the card — (not defined); the actual composition of the form should be read from the “live” interface.

4. Key Module Procedures

No specific BSL procedures are attached in evidence. The standard handlers apply for the report in DCS:

• Object Module → OnResultComposition(ReportResult, StandardProcessing) — programmatic intervention in the output: additional formation of rows, substitution of organization/individual attributes, formatting the header of the reference.
• Form Module → OnCreationOnServer — setting the default period, selection values (current organization), configuring conditional formatting and visibility.
• Form Module → OnOpening / CheckFillingProcessing — control that the period is set and an individual is selected in the selections before generation.
• Data Composition Scheme (DCS) — main business logic: data sets (queries to the calculation/accumulation registers), parameters StartPeriod/EndPeriod/Taxpayer, resource-indicators, layout, and default settings.

Specific names and lines of procedures depend on the release — requires verification against the reference delivery 3.0.74.2.

5. Conducting and Movements

The object is a report, not a document. It:

• is not conducted and has no ConductingProcessing procedures;
• does not generate entries in the chart of accounts and does not create movements in registers;
• works only in read mode — selects already existing data from the calculation and accounting results registers.

The report only displays mutual settlements formed by primary documents. For the reference on settlements with an individual, the sources are accounts from the standard chart of accounts of the RK: 1210 (short-term receivables from buyers/debtors), 3310/3390 (liabilities), 1030 (cash in current accounts) — regarding payments, as well as accounts for settlements with personnel and accountable persons. The amounts (individual income tax, pension contributions, contributions) are formed by documents of accruals/payments according to the RK 2026 norms (see FAQ) and are only displayed in the report.

6. Related Objects and Input on the Basis

• Directory Organizations — parameter Taxpayer (legal entity from which the reference is built).
• Directory Individuals (and/or individual counterparties) — subject of the reference, specified through selections.
• Directory StructuralUnits/OrganizationDepartments — source for RepresentationOfListOfStructuralUnits.
• Source documents of calculations — receivers of detailing: sales/income documents, payment and cash documents, accruals and payments to individuals. Transition to them is performed through the detailing mode.

Input on the basis is not applied for reports. The report itself can be opened as a detailing/related command from the cards of the individual or organization.

7. Points of Extension

• Data Composition Scheme (DCS) — standard configuration point: adding data sets, indicators (resources), selection fields, report variants, and user settings without changing the code.
• Report Variants — saving ready-made settings (set of indicators, selections, groupings) for standard reconciliation scenarios.
• Handler OnResultComposition in the object module — programmatic adjustment of output (non-standard header of the reference, attributes of signatories).
• Configuration Extension — adding attributes/indicators and overriding form handlers without removing from support.
• BSF Mechanisms — integration with mailing/printing and access rights (RLS) to limit visibility of settlements by organizations.