Document "УдалитьКорректировкаЗаписейРегистров" (Accounting for Kazakhstan 3.0)

1. Object identification

Purpose. A service (technical) document for adjusting — deleting, restoring, or deactivating — records of accumulation registers and information registers without recalculating the postings of the main business transactions. The Delete... prefix in the name and the “(not used)” mark in the synonym directly indicate an obsolete/service status: the object is kept in the metadata for compatibility and for the operation of data exchange mechanisms, but is not intended for manual use by users in normal mode.

Where to find it. In the standard configuration the document has no commands of its own in subsystems and the command interface (metadata.commands is empty). The list can be opened only via the navigation link:

e1cib/list/Документ.УдалитьКорректировкаЗаписейРегистров

Current replacement. For manual adjustment of register movements in current releases, the document “Operation (accounting and tax accounting)” with manual register adjustment is used.

2. Header attributes and tabular sections

2.1 Header attributes

If Organization is not filled in, the platform issues the standard “The ‘Organization’ field is not filled in” and blocks recording.

2.2 Tabular sections

The document does not store business lines (items, amounts, VAT). Instead, it stores a description of the composition of the adjusted registers:

The movements themselves are not calculated by the document logic — they are loaded or copied from outside (exchange, document copying, loading from an external system). The document acts as a “container-carrier” of the set of movements for the listed registers.

3. Forms

The set of forms is minimal — a consequence of the object’s service status.

The object contains no specialized user forms (input wizards, selection forms).

4. Key module procedures

Below are the handlers confirmed by evidence, with verbatim message texts (release 3.0.68.1; in 3.0.74.2 the logic is identical).

4.1 Object module — BeforeWrite

Implements “protection against manual changes.” If recording is performed not in the data-exchange loading mode, the document prohibits changes:

Изменение документов данного вида не поддерживается.
Для корректировки движений по регистрам накоплений регистрам сведений
необходимо использовать документ "Операции".

• Where: ObjectModule / BeforeWrite handler.
• Condition: DataExchange.Load is checked. Recording is allowed only when DataExchange.Load = True (that is, during synchronization/loading).

4.2 Document form — OnCreateAtServer

Prohibits the manual creation of new documents:

Добавление новых документов запрещено!

• Where: Form.DocumentForm / OnCreateAtServer handler.
• Condition: Parameters.Key.IsEmpty() — that is, the form is opened for a new (not yet recorded) object.

4.3 Movement generation logic (in loading mode)

When recording in loading mode:

1. The system reads the composition of registers from AccumulationRegistersTable and InformationRegistersTable.
2. For each register a set Set = Movements[RegisterName] is generated.
3. Record activity is controlled by a call to SetMovementsActivity() — it allows movements to be deactivated without physical deletion (a reversible operation) or reactivated.
4. There is no automatic calculation of movements — the data must be explicitly loaded or copied.

4.4 Standard posting handlers

The Posting handler is absent. The document does not generate postings in the traditional sense — it merely carries pre-prepared sets of register movements (see §5).

5. Posting and register movements

5.1 Feature

The document does not perform Posting and does not generate accounting postings on its own. It manages register movements:

• Accumulation registers — according to the evidence in metadata.register_records, 68 registers are listed, among them VAT, excise, mutual settlements, output/depreciation of fixed assets and intangible assets, inventory balances, employee payments, and others.
• Information registers — object states, depreciation parameters, tax rates, etc.

The sets of movements are not calculated but loaded/copied; activity is controlled by the SetMovementsActivity() method.

5.2 How this relates to the RK chart of accounts

The document does not create its own postings. But the registers it manages are the same ones that regular configuration documents fill in. For reference, we provide typical correspondences under the standard RK chart of accounts, reflected by ordinary documents (sales, receipt, payment) whose movements the service document could theoretically “carry”:

The VAT rate in Kazakhstan from 2026 is 16 % (₸ — tenge). The VAT/ESF registers operated by the document are designed for the current rate.

For reference (RK 2026 values, applied in related payroll/tax registers, not in the document itself): MCI = 4,325 ₸, minimum wage = 85,000 ₸; IIT 10 % up to 8,500 MCI of annual income and 15 % above; the basic IIT deduction is 30 MCI/month (no more than 360 MCI/year); OPC 10 % (base cap 50 minimum wages), OPCE 3.5 %, CHIC 2 %, CHI 3 %, SD 5 %, social tax 6 %.

5.3 Electronic documents

Through the VAT registers the document is indirectly related to the RK electronic document management subsystems — ESF (IS ESF) and SNT. Adjusting the corresponding registers can affect the data that goes into ESF/SNT, so it should be applied only in controlled loading/restoration scenarios.

6. Related objects and entry based on

• Entry based on is not provided for the document (there are no “create based on” commands).
• Related objects: numerous accumulation and information registers of the configuration (listed in metadata.register_records), as well as data exchange mechanisms (exchange plans, RIB) within which the document is recorded.
• Functional replacement: the “Operation” document — the standard tool for manual adjustment of register movements in current releases.

Use scenarios (by evidence)

Typical errors

7. Extension points

• Object module: the BeforeWrite, OnWrite handlers — control/logging points during exchange loading. Changing the ban on manual recording is not recommended.
• Document form: OnCreateAtServer — if diagnostics are required, an external processor/extension can be added without removing the standard ban.
• Registers: correct operation is ensured by the composition of AccumulationRegistersTable / InformationRegistersTable; extensions that add new registers to the scope must consistently supplement these tables.
• Exchange rules (CD 2/3): the main standard channel through which the document is created; logic extensions are appropriate at the level of conversion rules, not the document itself.

Requires verification (version-specific): the exact list of 68 accumulation registers in metadata.register_records and the presence/signature of the SetMovementsActivity() method may differ between releases 3.0.68.1 and 3.0.74.2 — verify against the specific configuration delivery.