1. Identification
| Parameter | Value |
|---|---|
| Object type | Document (Documents) |
| Name | ОПВВозвратВзносов |
| Full name | Документ.ОПВВозвратВзносов |
| Synonym (interface) | “Pension contributions refund from funds” |
| Configuration | Accounting for Kazakhstan, rev. 3.0.74.2 |
| Country | Kazakhstan (accounting currency — tenge, ₸) |
Purpose. The document is intended for recording operations of refunding mandatory pension contributions (OPV) from Kazakhstan's pension funds to the organization. It is used by accountants and HR specialists when receiving a refund of overpaid or erroneously transferred contributions from the ENPF (Unified Accumulative Pension Fund) or professional pension funds. The document is, as a rule, entered on the basis of a previously created document “OPV Transfer to Funds” and contains a list of individuals with refund amounts.
By its role, this is a registration source document: it records the fact and composition of the refund per individual and serves as a data source for subsequent cash flow operations and adjustment of settlements with pension funds. Frequency of use — usually several times a year, depending on the number of adjustments in the accounting of pension contributions.
Where to find it in 1C: section “Tax accounting” → “Pension contributions refund from funds”.
Navigation link: e1cib/list/Документ.ОПВВозвратВзносов
2. Header attributes and tabular sections
2.1 Header attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Организация |
The organization to which the contributions are refunded; defines the accounting policy and accounting dimension | Mandatory |
ПериодРегистрации |
The period (month) to which the registration of the contribution refund relates; used for reflection in tax/pension reporting | Mandatory |
ВидОперации |
Refund type (e.g., OPV / OPPV). Defines the composition of movements and the logic for filling the tabular section | Mandatory |
Ответственный |
User responsible for the document (standard attribute) | Filled automatically |
Комментарий |
Arbitrary text explanation | Optional |
If a mandatory field is not filled in, the platform will not allow the document to be posted and will issue an error of the type “Field … is not filled in”.
2.2 Tabular section “ПенсионныеВзносы”
Contains a line-by-line list of individuals with refund amounts.
| Column | Purpose | Mandatory |
|---|---|---|
ФизЛицо |
Individual (employee) for whom the contribution refund is registered | Mandatory |
Сумма |
Amount of the contribution refund for this individual, ₸ | Filled in |
ДокументОснование / link attribute |
Reference to the line/document of the transfer from which the refund is made | According to the filling scenario |
The OPV rate to which the document relates is 10% of the employee's income with a base cap of 50 MZP (at MZP = 85,000 ₸ for 2026). The document registers amounts already being refunded rather than recalculating them anew.
3. Forms
| Form | Purpose |
|---|---|
Document form (ФормаДокумента) |
Main input form: filling in the header, working with the “ПенсионныеВзносы” tabular section, selecting and manually adding individuals |
List form (ФормаСписка) |
Viewing and filtering refund documents; entry point via the link e1cib/list/Документ.ОПВВозвратВзносов |
Selection form (ФормаВыбора) |
Selecting a document from other objects (e.g., when entering on the basis of or in reports) |
| Group change form | Bulk changing of attributes of several documents from the list (change of responsible person, department, etc.) |
4. Key module procedures
The attached evidence lacks specific BSL fragments (path:line). Below are typical handlers for a document of this kind in the “Accounting for Kazakhstan” configuration; the actual implementation is to be verified against the module of the specific version.
Document form module:
ОрганизацияПриИзменении— setting/recalculating dependent attributes when the organization changes.ВидОперацииПриИзменении— processing the change of operation type; per scenario 3.4, when the refund type changes (e.g., from OPV to OPPV), the “ПенсионныеВзносы” tabular section is cleared with a warning to the user.ПенсионныеВзносыФизЛицоПриИзменении— control and auto-filling of line attributes when an individual is selected.- “Selection” command — adding individual employees without clearing the already existing list (scenario 3.3).
ЗаполнитьНаОсновании(in the object module) — filling the tabular section based on the source document “OPV Transfer to Funds” (scenario 3.1).
Object module:
ОбработкаЗаполнения— filling when entering on the basis of.ОбработкаПроверкиЗаполнения— control of mandatory fields (Организация, ПериодРегистрации, ВидОперации; in the lines — ФизЛицо).ОбработкаПроведения— see section 5.
5. Posting and movements
Important (per evidence). In the document metadata, the list of register records (register_records) is empty, and the posting procedure does not generate accounting entries or register movements directly in this module. The document plays the role of a registration source document: it records the composition of the refund per individual, while the actual movement of money and adjustment of settlements with pension funds are performed by related operations (see section 6).
In other words, when posting, the document:
- does not make accounting entries;
- does not write movements to accumulation/information registers at the level of its own
ОбработкаПроведения; - serves as a data source for subsequent cash flow and settlement documents.
Reflection of the cash refund (standard RK logic, by related documents). When the actual refund of funds arrives in the organization's account, the cash flow movement is reflected under the standard RK chart of accounts:
| Operation | Debit | Credit |
|---|---|---|
| Receipt of refunded contributions to the current account | 1030 (money in current accounts) | settlement account with the fund / personnel |
Rates and thresholds relevant for Kazakhstan for 2026 (for reference, to reconcile amounts and link with the payroll circuit): OPV 10% (base cap 50 MZP), OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%; IPN 10% up to 8,500 MRP of annual income and 15% above; basic IPN tax deduction 30 MRP per month (no more than 360 MRP per year); MRP = 4,325 ₸, MZP = 85,000 ₸.
The specific settlement account with the fund and the flag for generating movements may depend on the operation type and settings — this is a version-specific point requiring verification in the particular revision.
6. Related objects and entry on the basis of
Source document (entry “on the basis of”):
Документ.ОПВПеречислениеВФонды(“OPV Transfer to Funds”) — the main source; the list of individuals and refund amounts is filled from it.
Related objects:
- Catalog
ФизическиеЛица— source of the tabular section lines. - Catalog
Организации— accounting dimension. - Cash flow documents (receipt to current account 1030) — reflect the actual refund.
- Registers/documents of settlements with pension funds (ENPF) — adjustment of settlements.
Typical work scenarios:
- Creation on the basis of a transfer — upon receiving a fund's notification of the refund of erroneously or excessively transferred contributions.
- Manual filling by list of employees — when the refund does not fully correspond to the source document or there is no direct link to the transfer.
- Adding employees via selection — supplementing the existing list without clearing it.
- Changing the operation type with clearing of the tabular section — when changing the refund type (e.g., OPV → OPPV).
- Group change of documents from the list — bulk editing of attributes (responsible person, department, etc.).
7. Extension points
- Configuration extensions: adding header/tabular section attributes, additional columns in “ПенсионныеВзносы”, custom form commands.
- Form event handlers: overriding/supplementing
ВидОперацииПриИзменении,ПриСозданииНаСервере, reactions to individual selection. - Object module: supplementing
ОбработкаЗаполнения(custom rules for filling on the basis of),ОбработкаПроверкиЗаполнения(additional amount control), andОбработкаПроведенияif custom movements need to be added. - Event subscriptions: adding cross-object logic during posting/writing without modifying the document itself.
- Additional reports and data processors (external): generating printed forms and reconciliations for refunds.
- SSL mechanisms: bulk object change, versioning, additional attributes and information.
