Document "ILTransferToRecipients" (IL transfer to recipients) — Accounting for Kazakhstan 3.0.74.2

1. Identification

Purpose. The document registers the payment of funds to recipients based on enforcement orders — amounts withheld from employees' salaries by decisions of judicial and enforcement bodies (alimony, fines, compensation for damages, etc.). It is typically generated monthly after processing payroll documents and serves as the basis for the payment of collected amounts to recipients (for generating payment orders). The tabular part can be automatically filled based on the balances of mutual settlements as of the document date or the end of the payroll month.

Withholding based on IL is calculated from the employee's income after mandatory deductions and withholdings. For the context of RK 2026: PIT 10% (15% over 8,500 MRP annual income), OPE 10% (base ceiling 50 MZP = 50 × 85,000 ₸), VOSMS 2%, basic tax deduction for PIT — 30 MRP/month (MRP = 4,325 ₸), no more than 360 MRP per year. The payment document does not calculate these amounts — it operates with amounts already withheld based on IL.

2. Header Attributes and Tabular Parts

2.1 Header Attributes

The requirement for Organization, RegistrationPeriod, PaymentMethod is confirmed by evidence: if the field is not filled, the document is not processed with an error of the type “Field … is not filled”.

2.2 Tabular Part “EnforcementOrders”

The main tabular part is a line-by-line list of recipients and grounds for collection.

Important restriction (from evidence): in one document, it is not allowed to mix enforcement orders created during exchange and created manually. The statement must contain ILs of only one origin — otherwise, an error is issued during the filling check (see p. 4).

3. Forms

4. Key Procedures of Modules

Below are handlers based on the standard logic of this type of document; for filling verification, the actual control from evidence is provided.

Object Module (ObjectModule):

• CheckFilling(Refusal, CheckedAttributes) — control of mandatory attributes and homogeneity of IL. A check of the origin of the sheets is implemented: if the selection contains ILs created during exchange, and created manually at the same time (Selection.Count() > 1), an error is issued:

  “The document contains enforcement orders created during exchange and created manually. The statement may contain enforcement orders created only during exchange or created only …”

• FillProcessing(FillingData) — auto-filling the tabular part based on mutual settlement balances for IL as of the date/end of the month.
• ConductProcessing(Refusal, Mode) — formation of movements (see p. 5).

Manager Module (ManagerModule):

• Uses the common module MutualSettlementsOrganizationsWithILRecipients — calculation of mutual settlement balances with recipients based on enforcement orders, filling and recalculation of document amounts. This module encapsulates the business logic for obtaining amounts to be paid.

Form Module (DocumentForm):

• FillByBalances() / Fill() — command to fill rows based on balances as of the document date or the end of the month.
• Recalculate() — recalculation of amounts after adjustment of enforcement orders.
• FillIncomingAttributes() — filling the number and date of the incoming IL by rows.

Specific paths path:string in the source code in evidence are not provided; the list reflects the standard document handlers and confirmed logic of checks/mutual settlements.

5. Conducting and Movements

According to the metadata (register_records empty), the document does not generate accounting entries and movements in registers directly. It acts as:

• registrar/basis for calculations based on enforcement orders (through the common module MutualSettlementsOrganizationsWithILRecipients);
• data source for printed forms and processing of payment document formation.

Reflection in accounting is performed by related payment documents (payment order / cash expenditure order). Typical entries when actually paying the collected amount to the recipient according to the chart of accounts of the RK:

Accounts 1210, 1330, 3310, 3130, 6010, 7010, 3130 (VAT 16%), ESF/SNT do not relate to this document — it does not participate in sales and VAT.

Requires verification (version-wise): the specific sub-account of the obligation to the recipient (3390 or 3520) and whether service movements in settlement registers are formed during conducting — depends on accounting policy settings and release 3.0.74.2.

6. Related Objects and Input on Basis

• Document-basis of lines: enforcement order (document for IL accounting) — source DocumentBasis.
• Payroll documents — generate withholdings based on IL, the balances of which fill this document.
• Common module MutualSettlementsOrganizationsWithILRecipients — calculation of balances and amounts.
• Payment documents (outgoing payment order, cash expenditure order) — entered based on/from the registry for actual payment to recipients.
• Data exchange (EDO/upload): ILs created “during exchange” — a separate category of lines (see restriction in p. 2.2, 4).

7. Extension Points

• Subscriptions to events of conducting/filling verification — adding custom control (for example, checking recipient attributes before generating the registry).
• Extension of the common module MutualSettlementsOrganizationsWithILRecipients — changing the algorithm for calculating balances/amounts based on IL.
• Extension of forms of document/list — new auto-fill commands, additional columns, group processing in the list.
• Additional printed forms through the mechanism “Additional reports and processing” (registry for payment in the required bank format).
• Additional attributes and information (common BSP mechanism) — without changing the configuration.