--- title: "Reference \"Types of Operations Subject to Excise Tax\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-vidyoperaciyoblagaemyhakcizom-tehnicheskoe-op-en source: BuhGPT --- # Reference "Types of Operations Subject to Excise Tax" - Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name TypesOfOperationsSubjectToExcise Full Name Catalog.TypesOfOperationsSubjectToExcise Synonym — (no separate synonym assigned; displayed in the interface as “Types of operations subject to excise”) Configuration Accounti --- 1. Identification Parameter Value Object Type Catalog Name TypesOfOperationsSubjectToExcise Full Name Catalog.TypesOfOperationsSubjectToExcise Synonym — (no separate synonym assigned; displayed in the interface as “Types of operations subject to excise”) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Type Classifier (predefined set of values) Purpose. The catalog classifies operations subject to excise tax in accordance with the Tax Code of the RK. It contains a list of typical types of operations with excise goods (sales within the RK, import of excise goods, transfer for own needs, spoilage/loss, etc.). The values are used as analytics when registering operations with excise goods (alcohol, tobacco, petroleum products, spirits) and when preparing tax reporting on excise taxes. The catalog is used by accountants and tax specialists of manufacturing organizations and participants in the turnover of excise goods. Where to find in 1C: section “Analytical Information” → “Types of operations subject to excise”. Navigation link: e1cib/list/Catalog.TypesOfOperationsSubjectToExcise 2. Attributes and Tabular Parts 2.1 Header Attributes Specific attributes in the metadata structure are absent (the array attributes is empty). The catalog uses only standard attributes, which is typical for a classifier-list. Name Type Mandatory Purpose Code String Mandatory Unique code of the type of operation for systematization and references from excise reporting Name String Mandatory Text description of the type of operation (e.g., “Sales within the RK”, “Import of excise goods”) 2.2 Tabular Parts Tabular parts are absent (tabular_sections is empty). The structure is flat — typical for a classifier of operations. 3. Forms The catalog contains three standard forms: Form Purpose ElementForm View and edit a specific type of operation SelectionForm Select a value from the list when filling out documents and settings for excise accounting — key form in daily operations ListForm View the entire list of types of operations, group editing 4. Key Module Procedures The attached evidence does not include the source code of the modules (BSL) — only the metadata structure and the composition of forms are provided. Therefore, below are described typical handlers for the classifier catalog of this type; specific lines cannot be indicated (evidence code is absent). Object module (typical set): - BeforeWriting(Refusal) — control of filling mandatory attributes (Code, Name), prohibition of empty values. - FillingProcessing(FillingData, FillingText, StandardProcessing) — setting default values when creating a new element. - For predefined elements, recording/deletion marking is usually limited — the classifier is changed along with the configuration update. Element form module (typical set): - OnCreateOnServer(Refusal, StandardProcessing) — setting the availability of fields (predefined elements are usually protected from modification). - FillingCheckProcessing(Refusal, CheckedAttributes) — control of filling before closing the form. Requires verification on a specific version: the presence and exact composition of the object module procedures depend on the delivery 3.0.74.2 (evidence code is absent). 5. Posting and Movements The catalog is not a document and does not perform postings — it does not generate movements in registers and accounting entries. It is an analytical classifier: its elements serve as values of dimensions/attributes in documents and registers that record operations with excise goods. Movements are generated by documents that use this catalog as analytics. According to the standard accounting logic of the RK, the typical entries of such documents (for reference, the chart of accounts of the RK): Sale of excise goods (with excise and VAT 16%): Dr Cr Content 1210 6010 Customer debt / income from sales 1210 3130 VAT payable at the rate of 16% 7010 1330 Write-off of the cost of sold goods 7210/expenses 3140 (excise) Accrual of excise by type of operation Receipt / import of excise goods: Dr Cr Content 1330 3310 Receipt of goods / debt to supplier 1420 (VAT to be credited) 3310 / 3130 VAT on acquisition Electronic support of operations: ESF (ESF Information System) and SNT (accompanying invoices for goods) — are mandatory for excise goods. Calculations and currency — tenge (₸). The specific account for excise accounting and the composition of movements are determined by the registering document and its settings, not by the catalog itself. 6. Related Objects and Input Based On - Use as analytics. The values of the catalog are substituted into documents and registers reflecting operations with excise goods and participate in the formation of the excise declaration (form 400.00 and attachments). - Adjacent classifiers: catalogs of excise goods/nomenclature, excise rates, types of taxes. - Input based on. As a classifier, the catalog is not a basis for inputting documents and is not input based on other objects. Interaction is through value selection (SelectionForm) in the attributes of documents. 7. Extension Points - Configuration extension (Extension): adding custom attributes (e.g., grouping indicator for internal reporting), additional forms, handlers OnCreateOnServer/FillingCheckProcessing without removing from support. - Additional attributes and information (the “Properties” mechanism) — if support for characteristic types is enabled for the object. - Subscriptions to events of the object module (BeforeWriting, OnWriting) for integration logic. - Limitation: elements are usually predefined and synchronized with the update of the typical configuration — custom classifier values are better entered as undefined to avoid losing them during updates. Requires verification: the list of predefined elements and their composition may change between releases — check against the actual delivery 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_