Document "EPTransferToFunds" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document registers the transfer of the unified payment (UP) to state funds and the budget of the RK for the organization's employees. As part of the unified payment, the following are withheld and transferred from wages: PIT, OPE, OPEI, VOSMS, OOSMS (employer's contribution), OSMS, and social contributions (SC). The document is used by accountants and HR specialists monthly when forming payments to funds, as well as when processing refunds of erroneously credited amounts.

Current rates and parameters of the RK for 2026 that the document works with:

2. Header Attributes and Table Parts

2.1 Header Attributes

Other attributes typical for documents of this type: Date, Number, Comment, Responsible, BasisDocument (when entered based on), attributes of bank/budget payment.

2.2 Table Part “UnifiedPayments”

If any of the mandatory fields (header or table part) are not filled, the system will not process the document and will issue an error of the type “Field … is not filled”.

3. Forms

4. Key Module Procedures

Evidence by BSL code of modules is not attached (in meta only facets purpose, entries, attributes, scenarios are present). Below are typical handlers for documents of this type; signatures correspond to the standard model “BSP + industry logic”.

Object module:

• FillProcessing(BasisForFilling, StandardProcessing) — filling attributes when entering based on (for example, from PenaltyCalculationOPEandSC) or when creating a new one.
• CheckFillingProcessing(Refusal, CheckedAttributes) — control of mandatory fields: PaymentType, Organization, RegistrationPeriod, CalculationMethodForAmountsToBeTransferred and columns of the table part.
• Processing(Refusal, ProcessingMode) — according to standard movement logic, entries are not formed (see section 5).

Form module:

• OnCreationOnServer(Refusal, StandardProcessing) — form initialization, setting default values.
• Handlers PaymentTypeOnChange, CalculationMethodForAmountsToBeTransferredOnChange — clearing/re-filling the table part when changing parameters (scenario 3.5).
• Filling commands — FillByCalculations() / Fill() — automatic calculation of amounts to be transferred based on the data of calculation registers (scenario 3.3).
• Selection command — adding individuals manually (scenario 3.4).

Requires verification on a specific version: exact names of filling and selection commands may differ between releases of the 3.0.7x line.

5. Processing and Movements

The document does not generate movements in registers. In the metadata of the object, the list of receiving registers (register_records) is empty.

This document is a primary registration of the transfer of the unified payment: it records the fact and composition of the payment and serves as a source for printed forms (applications/registers). Reflection in accounting and tax records is performed by other documents:

• actual cash movement — document withdrawal from the current account (entry on the credit of account 1030 “Cash on current bank accounts”);
• accrual of taxes and contributions — payroll/tax calculation documents (closing liabilities on budget and fund accounts).

Thus, the entries of “ESFPaymentToFunds” are not created; in the standard accounting scheme of the RK, it precedes the payment document, which debits liability accounts and credits 1030.

6. Related Objects and Entry Based On

Usage scenarios (from evidence):

1. Creating a new document manually — typical monthly registration of UP without basis.
2. Creating based on PenaltyCalculationOPEandSC — penalty transfer.
3. Automatic calculation of amounts to be transferred based on the data of registers.
4. Manually adding employees through selection — when auto-filling is incomplete.
5. Clearing the table part when changing PaymentType or CalculationMethodForAmountsToBeTransferred.

7. Extension Points

• Configuration extension: overriding FillProcessing, CheckFillingProcessing to add custom checks; adding attributes/columns to the table part.
• Forms: through extending the document form — additional filling commands, custom handlers OnChange of header attributes, additional printed forms.
• Event subscriptions (BeforeSaving/OnSaving) — integration with external systems, logging of transfers.
• Additional reports and processes (BSP): external printed forms of applications/registers without changing the configuration.
• Exchange rules: exporting data on transfers to external accounting/payment systems.

When adding custom processing logic (if it is necessary to generate entries), the RK chart of accounts should be used (1030 for cash, liability accounts of the budget and funds) and movements generated by payment documents should not be duplicated.