Reference Guide "Types of Primary Documents" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog maintains a classifier of types of primary accounting documents used in the organization's accounting and tax reporting according to the standards of the RK. It systematizes the types of primary documents (invoice/e-invoice, waybill, act of completed work, SNK, waybill for inventory release, etc.) for selection during the registration of business transactions and printing forms. The catalog has a normative-reference nature: it is filled during the initial system setup and rarely changed — usually when introducing new types of documents into the organization's accounting policy.

Where to find in 1C: section “Main Activity” → “Types of Primary Documents”. Navigation link: e1cib/list/Catalog.DocumentTypes.

2. Attributes and Table Parts

2.1 Header Attributes

The catalog uses only standard attributes of the 1C catalog — custom attributes in the metadata are absent.

The absence of additional attributes indicates an intentionally simple structure of the classifier catalog, operating only through the standard fields Code and Description.

2.2 Table Parts

Table parts are absent (tabular_sections is empty).

3. Forms

The catalog contains three standard forms:

4. Key Module Procedures

The provided evidence does not include the original BSL code of the modules. For a catalog of this structure (without attributes and table parts), standard handlers of this type of object are applied:

Object Module (ObjectModule):

• CheckFilling(Refusal, CheckedAttributes) — control of filling mandatory fields (Name) before saving.
• BeforeSaving(Refusal) — pre-saving control (if additional business logic is present; usually minimal or absent for classifiers).
• OnNewCodeSet(StandardHandler, Prefix) — managing the formation of the code for the new element (if necessary).

Element/List Form Module:

• OnCreateOnServer(Refusal, StandardHandler) — initial setup of the form (availability of fields, conditional formatting).
• Selection/Matching handlers in SelectForm — returning the selected element to the calling object.

“Requires verification” (version-specific): the presence of predefined elements and service procedures for their matching may differ between releases; verify with the specific build 3.0.74.2 if the catalog is used in standard mechanisms for auto-filling document types.

5. Posting and Movements

The catalog is not a document and does not generate movements — it is not posted and does not directly create records in registers and postings. Its elements act as classifier values: they are substituted into document attributes and printed forms, as well as used in analytics and report selections.

Indirectly, the type of primary document participates in the execution of business transactions, which already generate movements according to the standard Chart of Accounts of the RK. Examples of typical postings of transactions where the type of primary document is indicated (numbers — according to the norms of Kazakhstan 2026, VAT 16%):

• Sale of goods (waybill / e-invoice), amount 1,160,000 ₸ (including VAT 16% = 160,000 ₸):

  • Dr 1210 “Short-term receivables from customers” — Cr 6010 “Revenue from sales” — 1,000,000 ₸
  • Dr 1210 — Cr 3130 “VAT payable” — 160,000 ₸
  • Dr 7010 “Cost of goods sold” — Cr 1330 “Goods” — write-off of cost

• Receipt of goods from the supplier (waybill / e-invoice), 580,000 ₸ (including VAT 16% = 80,000 ₸):

  • Dr 1330 “Goods” — Cr 3310 “Short-term payables to suppliers” — 500,000 ₸
  • Dr 1420 (VAT to be refunded) — Cr 3310 — 80,000 ₸

• Payment from the customer to the current account:

  • Dr 1030 “Cash in current bank accounts” — Cr 1210 — 1,160,000 ₸

The type of primary document also appears in the exchange of electronic documents: e-invoice (IS e-invoice) and SNK, where the type of document being processed affects the content of the export.

6. Related Objects and Input Based On

• Documents of goods movement and services — sales, receipts, acts of completed work: the attribute “Type of primary document” determines the name of the printed form and the content of e-invoice/SNK.
• Electronic documents (e-invoice, SNK) — the type of document affects the format and attributes of the exported file in IS e-invoice.
• Reports and analytics — used as a measure/filter when grouping primary documents.

The catalog does not have an input based on mechanism (not a document). Input of new elements is performed manually through ElementForm or programmatically during the initial filling/updating of the configuration.

7. Extension Points

• Configuration Extension: adding custom attributes (e.g., indicator “Electronic document”, link to the print form template, e-invoice format code) without removing from support.
• Additional attributes and information: connection through the “Properties” mechanism (when the properties subsystem is enabled), if classification is required without changing the metadata.
• Event subscriptions: processing BeforeSaving/OnSaving for integration synchronization of the catalog with external systems.
• Overridable modules: default document type substitution in document forms through procedures of common modules “...Overridable”.
• Conditional formatting and functional options: managing the visibility/accessibility of catalog elements depending on accounting settings.

“Requires verification” (version-specific): the composition of predefined elements and the participation of the catalog in specific standard mechanisms for auto-filling document types may differ between releases of the 3.0.7x line — verify with the metadata of build 3.0.74.2.