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

1. Identification

Purpose. The document is intended for processing mandatory social contributions to the state funds of Kazakhstan — pension fund (OPV, OPVR), social health insurance fund (VOSMS, OSMS), as well as social deductions (SO). It is used by payroll accountants to account for liabilities to the funds and to record the fact of the transfer of funds. The document can be filled out manually or automatically based on the data of accruals/penalty calculations and is used regularly — usually monthly, after payroll calculation, or based on the results of penalty calculations.

Where to find in 1C.

• Section “Tax Accounting” → “Social Insurance Contributions Transfer”.
• Also available from the “Payroll and Personnel” block → “Social Contributions”.
• Direct navigation link: e1cib/list/Document.SocialContributionsTransfer

2. Attributes of Header and Table Parts

2.1 Header Attributes

If a mandatory attribute is not filled in, the platform will not process the document and will display a message like “Field … is not filled in”.

2.2 Table Part “SocialContributions”

Contribution and Deduction Rates (RK, 2026) used for calculating amounts:

Reference values 2026: MRP = 4,325 ₸, MZP = 85,000 ₸. Basic tax deduction for PIT — 30 MRP/month (not more than 360 MRP/year). PIT — 10% up to 8,500 MRP annual income and 15% above.

3. Forms

The specific composition of forms is version-dependent — in 3.0.74.2 it is specified in the configurator (branch “Forms” of the object).

4. Key Module Procedures

In the attached evidence, there are no BSL exports (path: line). Below are typical handlers for documents of this type in BK 3.0; verify the actual implementation in the configurator.

Document Form Module:

• OnCreateOnServer — form initialization, setting default values (organization, operation type, calculation method), configuring the availability of attributes.
• OperationTypeOnChange / CalculationMethodForAmountsToTransferOnChange — restructuring the form when changing the operation type/calculation method (scenario 3.5): managing visibility and composition of table parts.
• Fill (command) — automatic filling of the table part of amounts to transfer by the selected method: by accrual registers, by the list of employees of the department (scenario 3.4) or based on penalty calculation (scenario 3.2).
• Long operation handler (background task) — calculating amounts with a large volume of data (scenario 3.3), to avoid blocking the interface.

Object Module:

• FillProcessing — filling when entering based on (for example, from “PenaltyCalculationOPVandSO”).
• FillCheckProcessing — control of mandatory fields (PaymentType, Organization, CalculationMethodForAmountsToTransfer, OperationType, Individual in lines).
• ProcessingConducting — this document does not have (see section 5).

5. Conducting and Movements

Important. According to the evidence, the document SocialContributionsTransfer does not contain the procedure ProcessingConducting and does not generate movements in registers (metadata.register_records is empty). This is an accounting-fixing (“register-based” by purpose) document: it records the fact/preparation of the transfer of contributions, but does not reflect entries in accounting accounts by the document itself.

Where entries for contributions are formed. Accrual of liabilities to the funds and their repayment are reflected by other documents of the configuration:

• Accrual of contributions — documents for payroll calculation (reflection of accrued OPV/OPVR/VOSMS/OSMS/SO and taxes);
• Actual payment — payment documents (debit from the settlement account).

Approximate accounts according to the typical chart of accounts of the RK (formed by accompanying documents, not this one):

• 3210–3230 — liabilities for social payments and taxes to the budget/funds (credited upon accrual);
• 1030 “Cash on current bank accounts” — credited upon actual transfer;
• 7210/8110 and others — expenses for contributions (depending on the type of accrual).

Other accounts of the typical plan of the RK for related operations: 1210 (short-term receivables from buyers), 1330 (goods), 3310 (payables to suppliers), 3130 (VAT payable, rate 16%), 6010 (revenue from sales), 7010 (cost of sales).

Requires verification (version-specific): the exact set of registers involved in conducting in 3.0.74.2 — there are no movements in the evidence, but verify the specific configuration in the configurator.

6. Related Objects and Input Based On

Input Based On (in the document):

• PenaltyCalculationOPVandSO — filling in the penalty transfer for contributions based on calculated amounts (scenario 3.2).
• Data of payroll accruals / accounting registers — source for automatic calculation of amounts (scenarios 3.1, 3.3).

Related Objects:

• Directories “Organizations”, “Individuals”, “Departments” (filter by department, scenario 3.4).
• Documents for payroll calculation and contribution accruals (form actual entries and liabilities).
• Payment documents for debit from the settlement account (actual transfer of funds).

7. Extension Points

• Configuration Extensions. Adding attributes/columns and handlers without removing from support; overriding form modules.
• Form Event Handlers. OnCreateOnServer, *OnChange, command “Fill” — for custom logic of filling amounts.
• Object Module. FillProcessing, FillCheckProcessing — for additional rules of input based on and control.
• Methods of calculating amounts. Extending the list of values for CalculationMethodForAmountsToTransfer and corresponding algorithms (including through background tasks for large volumes).
• Printed Forms. Adding custom layouts for payment documents through the printing mechanism.
• Subscriptions to Events / BCP. Integration with common mechanisms (versioning of objects, additional processing).

When making modifications, consider that the document does not generate accounting movements — the logic of entries should be extended in the documents of accrual/payment, not here.