Standard Transactions" Directory — Accounting for Kazakhstan 3.0

1. Identification

Purpose. The catalog stores customizable templates for accounting and tax entries. It automates the entry of recurring non-standard business operations that are not covered by the configuration's specialized documents (sales, receipts, payroll accrual, etc.). Each catalog item describes a set of entries with parameterization of accounts, subaccounts (subconto), amounts, and content; it supports formulas for calculating the amount and content, as well as algorithms in the built-in language (BSL) for complex logic. The main usage scenario is the substitution of a template into the "Operation (accounting and tax accounting)" document (Документ.Операция): the user selects a standard operation, responds to the parameter prompt, and the system generates a ready-made set of entries.

The object's users are accountants and chief accountants. The usage mode is periodic, as needed for entering non-standard operations.

2. Header attributes and tabular sections

2.1 Header attributes

In addition to the listed applied attributes, there are standard ones: Код, Наименование, Родитель (group), ЭтоГруппа, ПометкаУдаления, Предопределённый.

2.2 Tabular section "Parameters"

Stores the list of standard operation parameters requested from the user when creating a document based on the template. Parameter values are substituted into formulas, subaccounts (subconto), and algorithms.

2.3 Tabular section "Standard"

Entry templates for the standard (accounting) chart of accounts (ПланСчетов.Типовой). Each row is one entry.

2.4 Tabular section "Tax"

Analogous to the "Standard" table, but for the tax chart of accounts (ПланСчетов.Налоговый): the same fields СчетДт, СчетКт, subconto, amount and quantity formulas. Used to generate tax accounting movements in parallel with accounting entries.

3. Forms

4. Key module procedures

Evidence with exact paths path:line for this object's modules is not attached. Below is a typical set of handlers for a catalog of this kind in Accounting 3.0; for the actual placement of procedures, refer to the object module, manager module, and form modules of the specific version.

• ObjectModule — ОбработкаПроверкиЗаполнения — control of the correctness of formulas and the filling of mandatory rows in the entry tables before writing.
• ObjectModule — ПередЗаписью — validation of formula/algorithm syntax, normalization of references.
• ManagerModule — operation generation procedures — building the "Operation" document movements based on the "Standard"/"Tax" tabular sections: calculating formulas, substituting parameters and subconto, calculating amounts and content.
• Algorithm execution mechanism — sequential invocation of code from the attributes АлгоритмПередВводом → АлгоритмПриВводе → АлгоритмПослеВвода via Выполнить()/Вычислить() with the passing of a parameter structure.
• Element form module — ПриИзменении of formula fields — syntax control and hints when editing the content and amount formulas.
• Parameters form module — АлгоритмПриИзменении — execution of code from the field of the same name in the "Parameters" tabular section when the user enters values (recalculation of related parameters, application of the СвязьПоВладельцу/СвязьПоТипу links).

Requires verification (version-specific): the exact names and signatures of the entry generation procedures in the manager module may differ between releases of the 3.0 branch.

5. Posting and movements

The ТиповыеОперации catalog is not posted itself and does not generate movements — it is a template repository. Movements are generated by the "Operation (accounting and tax accounting)" document (Документ.Операция), into which the template is substituted.

Substitution logic:

1. In the "Operation" document, an item of the ТиповыеОперации catalog is selected.
2. АлгоритмПередВводом is executed, then the parameter dialog is shown (the "Parameters" table), then АлгоритмПриВводе.
3. For each row of the "Standard" tabular section, the formulas (Сумма, СодержаниеПроводки, quantities/currency, subconto) are calculated, and an entry of the accounting register РегистрБухгалтерии.Типовой is created.
4. Similarly, the rows of the "Tax" tabular section generate movements in the tax chart of accounts (РегистрБухгалтерии.Налоговый).
5. АлгоритмПослеВвода is executed.

Further movements are made by the "Operation" document itself upon posting. The standard operation itself has no specific additional registers.

Examples of entries by the standard RK chart of accounts (figures — according to Kazakhstan norms 2026):

Sale of goods to a customer for 1,160,000 ₸, including VAT 16%:

Receipt of goods from a supplier for 1,160,000 ₸, including VAT 16%:

Payment to the supplier from the current account:

* The input VAT account is provided for the completeness of the chain; in the template, use the account in accordance with the organization's accounting policy.

The calculation of the VAT amount in the template formula is performed at the rate of 16% (e.g., НДС = СуммаБезНДС * 0.16), and not at the outdated rate of 12%.

6. Related objects and entry based on

• Document "Operation (accounting and tax accounting)" (Документ.Операция) — the main consumer of templates; the standard operation is substituted into it to generate entries.
• Chart of accounts "Standard" (ПланСчетов.Типовой) — the source of accounts for the "Standard" tabular section; defines the subconto types.
• Chart of accounts "Tax" (ПланСчетов.Налоговый) — the source of accounts for the "Tax" tabular section.
• Accounting registers "Standard" and "Tax" — the recipients of movements (via the "Operation" document).
• Charts of characteristic types of subconto — define the composition of subconto available for parameterization (the НомерСубконто field).

Entry based on the catalog itself is not provided; the direction of the relationship is reverse — the standard operation is used within the "Operation" document. RK electronic documents (ESF in the ESF IS, SNT) are generated by sales/receipt documents and are not directly related to standard operations — when manually entering a sale via "Operation", the ESF/SNT are issued separately.

7. Extension points

• Formulas ФормулаСодержания, ФормулаСуммыОперации and the formulas in the entry rows — the main built-in configuration mechanism without changing code.
• Algorithms АлгоритмПередВводом, АлгоритмПриВводе, АлгоритмПослеВвода and the parameters' АлгоритмПриИзменении — built-in BSL for complex logic (e.g., automatic calculation of basic deductions and taxes: the basic IIT deduction of 30 MCI/month with an MCI of 4,325 ₸, IIT rates of 10%/15%, mandatory pension contributions (OPV) 10%, mandatory social health insurance contributions (VOSMS) 2%, compulsory social health insurance (OSMS) 3%, social contributions (SO) 5%, social tax 6%).
• Parameters (СвязьПоВладельцу, СвязьПоТипу, НомерСубконто) — configuring the interactive entry dialog without customization.
• Configuration extensions — overriding form/manager modules, adding attributes via an extension without removing the configuration from support.
• Event subscriptions of the "Operation" document — for processing movements generated from the template.

It is recommended to store constants (MCI, minimum wage, rates) in the corresponding configuration registers/constants and to reference them in algorithms, rather than "hardcoding" numbers into formulas — this will simplify the transition during the annual change of indicators.