1. Identification
| Parameter | Value |
|---|---|
| Full name | Document.OPVTransferToFunds (Documents.OPVTransferToFunds) |
| Metadata object type | Document |
| Name | OPVTransferToFunds |
| Synonym | Not specified in the metadata card; appears in the interface as "Pension contributions transfer to funds" |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Country of accounting | Kazakhstan (₸) |
Purpose. The document reflects operations for the transfer of mandatory pension contributions (OPV) and related deductions to the state funds of Kazakhstan. It is used by accountants and HR specialists to record payments to the funds based on previously accrued contributions. It can be created independently or based on the document "CalculationOfPenaltiesForOPVAndSOC" (calculation of penalties for OPV and social deductions). It is used regularly — monthly or as needed for fund transfers.
Where to find in 1C: section "Tax Accounting" → "Pension contributions transfer to funds". Navigation link: e1cib/list/Document.OPVTransferToFunds.
Payment context for 2026 in the RK: basic OPV rate — 10% (base ceiling 50 MZP = 50 × 85,000 = 4,250,000 ₸/month), OPVR — 3.5%, VOSMS — 2%, OSMS — 3%, SO — 5%, social tax — 6%. MRP = 4,325 ₸, MZP = 85,000 ₸.
2. Header attributes and table parts
2.1 Header attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Organization |
The payer organization on behalf of which the contributions are transferred | Mandatory |
RegistrationPeriod |
The period (month) of contribution accrual for which the transfer is made | Mandatory |
PaymentType |
The type of payment being transferred (OPV, OPVR, SO, VOSMS/OSMS, etc.) — determines the receiving fund and classification of the payment | Mandatory |
OperationType |
The type of document operation; manages the filling scheme and the composition of filled data | Mandatory |
CalculationMethodForAmountsToTransfer |
The algorithm for calculating amounts to be transferred (by debt, by proportion of accrued amounts, manually, etc.) | Mandatory |
If any of the listed attributes are not filled, the platform will not allow the document to be processed and will display the message "Field ... is not filled".
2.2 Table part "PensionContributions"
The rows contain a list of individuals and the amounts of contributions to be transferred.
| Column | Purpose | Mandatory |
|---|---|---|
Individual |
Individual (employee) for whom the contribution is transferred | Mandatory |
Amount (amount to be transferred) |
The amount of the contribution for this individual in tenge | Filled according to the selected calculation method |
Other service columns (period, type of contribution, share) are filled by auto-fill mechanisms according to the calculation method; the key mandatory field of the row is
Individual.
3. Forms
| Form | Purpose |
|---|---|
Document form (DocumentForm) |
Main form for input/editing: header, table part "PensionContributions", auto-fill commands and employee selection |
List form (ListForm) |
List of transfer documents, selection by organization/period, opens via link e1cib/list/Document.OPVTransferToFunds |
Selection form (SelectionForm) |
Document selection when substituting into other objects (for example, when entering a payment order based on) |
4. Key module procedures
The attached evidence does not provide the source code (BSL) of the modules, so below are the typical document handlers of this type in BK 3.0. Exact names and contents of procedures should be clarified according to the specific version of the configuration.
Object module:
FillProcessing(FillingBasis, StandardProcessing)— filling in attributes when entering based on "CalculationOfPenaltiesForOPVAndSOC" (transferring organization, period, individuals, and amounts).CheckFillingProcessing(Refusal, CheckedAttributes)— control of mandatory attributes (PaymentType,Organization,RegistrationPeriod,CalculationMethodForAmountsToTransfer,OperationType,Individualin rows).ConductProcessing(Refusal, ConductingMode)— according to the standard logic of this document, movements are not formed (see section 5).
Document form module:
OnCreateOnServer— initialization of default values (organization, registration period, operation type).- Auto-fill commands for the table part according to the calculation method (
CalculationMethodForAmountsToTransfer): filling by debt, distribution by proportion of accrued amounts. - Handler for employee selection for manual filling of "PensionContributions" rows.
<Attribute>OnChange— recalculation/re-filling of rows when changing the payment type, period, or calculation method.
5. Conducting and movements
According to the metadata card, the document does not have register records (register_records: []). This means:
- When conducting, the document does not independently generate automatic accounting entries and movements in the registers.
- The actual transfer of funds and corresponding entries are generated by payment documents (for example, "Payment Order (outgoing)"/debit from the bank account), which can be created based on this document.
For reference, the standard scheme for reflecting the actual transfer of contributions in the typical chart of accounts of the RK (formed by the payment document, not by the "OPVTransferToFunds" itself):
| Dr | Cr | Description |
|---|---|---|
| 3220 "Liabilities for pension deductions" (liabilities to funds) | 1030 "Cash in current bank accounts" | Transfer of OPV/OPVR and social deductions to funds |
Cash and settlement accounts are presented according to the typical chart of accounts of the RK: 1030 — cash in current accounts, liability accounts of group 3200 — settlements with the budget and funds. The document "OPVTransferToFunds" serves as a registering/preparatory link before the payment.
6. Related objects and input based on
- Input basis: document "CalculationOfPenaltiesForOPVAndSOC" — when entering based on, the organization, period, list of individuals, and calculated amounts are transferred.
- Input based on (descendants): payment documents for transfers to the budget/funds (payment order, debit from the bank account), forming actual entries Dr liabilities — Cr 1030.
- Adjacent objects: directories "Organizations", "Individuals", information registers by types of payments and parameters of OPV/OSMS/SO.
Typical usage scenarios:
- Creating a transfer based on the calculation of penalties for OPV.
- Independent creation with auto-fill based on accumulated debt.
- Calculation of amounts to be transferred by proportion of accrued amounts (partial payment).
- Manual filling with selection of specific employees.
- Viewing and correcting a previously created document.
7. Extension points
- Configuration extensions: overriding/adding
FillProcessing,CheckFillingProcessingto add custom checks and auto-fill rules. - Event subscriptions:
BeforeSaving/OnSaving/ConductProcessingof the document for integration with external payment registers or additional movements. - Forms: adding attributes and commands to the document form through extension (for example, a button for exporting the register or additional selection).
- Additional processes (BSP): designated filling/printing processes for the document.
- Exchange rules: inclusion of the document in exchange/conversion plans when synchronizing with payroll or banking systems.