--- title: "Document \"OperationBukh\" (Operation) - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-operaciyabuh-operaciya-tehnicheskoe-opisanie-en source: BuhGPT --- # Document "OperationBukh" (Operation) - Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Document (Documents) Name OperationAccounting Full Name Document.OperationAccounting Alias “Operation” Configuration Accounting for Kazakhstan, ed. 3.0 (3.0.74.2) Where to find Section “Operations” → “Operation” Navigation Link e1c --- 1. Identification Parameter Value Object Type Document (Documents) Name OperationAccounting Full Name Document.OperationAccounting Alias “Operation” Configuration Accounting for Kazakhstan, ed. 3.0 (3.0.74.2) Where to find Section “Operations” → “Operation” Navigation Link e1cib/list/Document.OperationAccounting Purpose. “Operation” is a universal document for registering arbitrary accounting entries and business operations that are not described by standard documents of the configuration. It is used for manual entry of non-standard operations, correcting errors from previous periods, generating reversing (adjusting) entries, and creating operations based on templates from the “Standard Operations” directory. The document supports simultaneous accounting (BU) and tax accounting (NU) and can record movements across a large number of accumulation and information registers. The main users are chief accountants and accounting department specialists; the accounting currency is tenge (₸). 2. Attributes of the Header and Table Parts 2.1 Header Attributes Attribute Purpose Mandatory Organization The organization for which the operation is registered Yes ReversedDocument Reference to the document whose movements are reversed/adjusted (for reversing operations) Yes* Date Date and time of entry formation (determines the period and chronology) Yes Number Sequential document number Auto Responsible User responsible for the operation No Comment Arbitrary text explanation for the operation No Content Brief description of the business operation (general for the document) No Operation Amount Total amount for control/reflection in the list No * “ReversedDocument” is mandatory for reversing mode; for a regular manual operation, the field is not filled. If a mandatory field is not filled, 1C will not allow the document to be processed and will issue an error “Field … is not filled”. 2.2 Table Parts (movements are formed directly in the form) Feature of the document: entries are not stored in a separate table part “goods”, but are entered directly into the sets of records of the accounting registers through the form. Movements.Standard — accounting (AccountingRegister.Standard): Field Purpose DebitAccount, CreditAccount Corresponding accounts according to the chart of accounts of the RK SubaccountDebit1–3, SubaccountCredit1–3 Analytics for debit and credit Amount Amount of the entry in the accounting currency (₸) Quantity Quantitative indicator (for quantitative accounting) Currency, CurrencyAmount Currency and amount in currency (for foreign currency accounts) StructuralSubdivisionDebit / Credit Subdivision for debit/credit Movements.Tax — tax accounting (AccountingRegister.Tax): Field Purpose DebitAccount, CreditAccount Tax accounting accounts TypeOfAccountingDebit, TypeOfAccountingCredit Type of accounting for debit/credit (NU, PR, VR, etc.) SubaccountDebit1–3, SubaccountCredit1–3 Tax analytics for debit and credit Amount Tax entry amount Quantity Quantitative indicator StructuralSubdivisionDebit / Credit Subdivision for debit/credit Additionally, the document can record movements in up to 80 accumulation and information registers, the list of which is configured through the settings form (see sections 5 and 6.3). 3. Forms Form Purpose DocumentForm Main input form: header + tabs for manual entries of BU (Standard) and NU (Tax) ListForm List of “Operation” documents (opens via navigation link) SettingsForm Configuration of the list of registers into which the document writes movements (selection from ~80 registers) SelectForm Selecting the “Operation” document in the field of related objects The select form and the list form can be auto-generated unless explicitly overridden in the configuration. 4. Key Module Procedures The document does not have a standard procedure ProcessingProcedure in the object module — entries are formed directly from the form through sets of records of the registers. The logic of filling based on templates is concentrated in the object module. Procedure / Location What it does ObjectModule / FillBasedOnStandardOperation Fills BU and NU entries based on the selected standard operation: executes the algorithm “before forming entries” (AlgorithmOnInput), checks the conditions for forming each entry (BU and NU), forms records, and executes the algorithm “after forming entries” (OperationAlgorithm) ObjectModule / FieldValue Calculates the value of the entry field according to the specified formula of the standard operation template Error message texts (verbatim from code, release 3.0.68.1): 1C Message Where it occurs Condition Standard operation algorithm (before forming entries): %1 FillBasedOnStandardOperation Not EmptyString(AlgorithmOnInput) Standard operation algorithm (after forming entries): %1 FillBasedOnStandardOperation Not EmptyString(OperationAlgorithm) Error calculating field value by formula: %1 - %2 FieldValue — Condition for forming entry (NU) №%1 %2 FillBasedOnStandardOperation Not ConditionMet Condition for forming entry №%1 %2 FillBasedOnStandardOperation Not ConditionMet When such a message appears, check the corresponding condition/algorithm in the settings of the standard operation. 5. Processing and Movements Since ProcessingProcedure is absent, entries are manual (or filled by template) records that the user enters in the form and which are recorded when the document is processed: - AccountingRegister.Standard — accounting; - AccountingRegister.Tax — tax accounting; - up to 80 accumulation/information registers — connected through SettingsForm (for example, VAT, PIT registers, etc.), allowing the operation to affect specialized accounting on par with standard documents. Standard Examples of Entries (chart of accounts RK, amounts in ₸) Sale of goods (manual reflection), VAT at the current RK rate 16%: Debit Credit Amount Content 1210 6010 Cost including VAT Accrued receivable from the buyer (short-term receivable) on revenue from sales 6010 3130 16% of the base Accrued VAT payable to the budget 7010 1330 Cost Cost of sold goods written off Example: sale for 1,160,000 ₸ including VAT → base 1,000,000 ₸, VAT 160,000 ₸ (16%). Entries: Debit 1210 Credit 6010 — 1,160,000 ₸; Debit 6010 Credit 3130 — 160,000 ₸; Debit 7010 Credit 1330 — for the amount of cost. Writing off future expenses, correcting errors from previous periods, adjusting balances — are documented with arbitrary correspondences according to the chart of accounts of the RK. Application Scenarios - Manual operation — entry of an entry not provided by standard documents. - Operation based on standard — recurring parameterized operation (monthly write-offs, accruals, reallocations) from the “Standard Operations” directory. - Reversing operation — reversal/correction of a previously processed document through the attribute “ReversedDocument”. - Synchronization of BU and NU — automatic duplication of entries from BU to NU (or vice versa). - Configuration of movement registers — limiting the set of registers into which the document writes (for example, only VAT and PIT). 6. Related Objects and Input Based On Relation Object Role Template source Directory StandardOperations Stores algorithms, formulas, and conditions for auto-filling entries Reversal Any processed document Through the attribute “ReversedDocument” Chart of accounts ChartOfAccounts.Standard (RK) Accounts 1210, 6010, 7010, 1330, 3130, etc. Registers AccountingRegister.Standard, AccountingRegister.Tax + up to 80 accumulation/information registers Receivers of movements Electronic documents ESF (IS ESF), SNT A manual operation itself does not generate ESF/SNT; electronic documents are issued by relevant documents of sales/receipts The document can be entered based on a standard operation; and serve as a basis/source for reversing other documents. 7. Extension Points - Directory “Standard Operations” — the main mechanism for customization: algorithms “before/after forming entries”, field formulas (FieldValue), conditions for forming BU and NU entries. - SettingsForm — managing the composition of movement registers without changing the configuration. - Configuration extensions — adding header attributes, additional checks in the object/module form. - Event subscriptions and additional processing — response to recording/processing of the document. - Algorithms in the built-in language in standard operations — flexible parameterization without removing the configuration from support. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_