Document "SNT" — Electronic Invoice Accompanying Goods (Accounting for Kazakhstan 3.0.74.2)

1. Identification of the Object

Purpose. The SNT document provides electronic support for the movement of goods in the Republic of Kazakhstan as part of the integration with the Electronic Invoice Information System (ESF IS) and the Goods Marking and Traceability System (MPT IS). It is used for import/export operations, movement of goods, including excise goods (alcohol, tobacco, petroleum products, biofuels) and goods with digital marking. The document is used daily by trade and logistics organizations — primarily for inter-warehouse, export, and import operations.

Where to find in 1C: section “ESF/EAVR” → “SNT”. The lists are divided into two subsystems:

• “Electronic Invoices for Goods (received)” — incoming SNT;
• “Electronic Invoices for Goods (issued)” — outgoing SNT.

All monetary operations are conducted in tenge (₸); the VAT rate for 2026 is 16%.

2. Attributes of the Header and Table Parts

2.1. Mandatory Attributes of the Header

If any of the listed fields are not filled in — 1C will not process the document and will issue an error of the type “Field … is not filled in”.

2.2. Table Parts

Origin indicator classifies the goods (produced in the RK, imported from the EAEU/third countries, etc.) and affects the data transmitted to the ESF IS.

2.3. Service Structure “Typical Errors”

Used for registering validation errors when checking the document before sending:

3. Forms

For documents of this type in the standard configuration, the following are provided:

• Document Form — main form for entering/editing SNT: header, table parts, commands for sending/receiving from the ESF IS, statuses of electronic document flow.
• List Form — separate lists of received and issued SNT with filtering by status, counterparty, period.
• Selection Form — selection of SNT when entering based on and matching.

Commands for working with the electronic document (send, receive, confirm, reject, issue corrected) are placed in the command panel of the document form.

4. Key Procedures of Modules

The attached evidence does not include the source code (BSL) of the modules. Below are the typical handlers for the SNT document of this configuration according to the standard logic of the object type.

• ProcessingConduct(Refusal, ProcessingMode) — generates movements in the accumulation registers of the virtual warehouse (see section 5). Does not generate accounting entries.
• ProcessingFilling(FillingBasis, ...) — fills the header and table parts when entering based on sales/receipts.
• FillingCheck / control of mandatory attributes — validation before processing and sending to the ESF IS; errors accumulate in the “Typical Errors” structure (Text, Field).
• Electronic Document Flow Handlers — generation of XML for the ESF IS, sending/receiving SNT, processing statuses (confirmed/rejected/corrected), obtaining product identifiers from the ESF IS.

5. Processing and Movements

Important: the SNT document does not generate accounting entries (Dr/Cr). It is intended for electronic support of the movement of goods, not for reflecting business transactions in accounting. The financial result is reflected in accompanying documents (sales, receipts).

The document generates movements only in two accumulation registers:

For Reference: Accompanying Accounting Entries

The entries are not generated by the SNT itself, but by related documents. According to the standard chart of accounts of the RK, the following are used for sales/receipts (numbers — according to RK rates for 2026, VAT 16%):

Sale of Goods (document-basis for outgoing SNT):

• Dr 1210 Cr 6010 — revenue from sales;
• Dr 1210 Cr 3130 — VAT payable at the rate of 16%;
• Dr 7010 Cr 1330 — write-off of the cost of goods.

Receipt of Goods (according to incoming SNT):

• Dr 1330 Cr 3310 — receipt of goods;
• Dr 1420 Cr 3310 — incoming VAT 16%.

Payment: Dr 1030 Cr 1210 (receipt of money) / Dr 3310 Cr 1030 (payment to supplier).

6. Related Objects and Entry Based On

Typical scenarios in which the SNT document is involved:

• 3.1. Creation of Outgoing SNT Based on Sale of Goods — when shipping to the buyer, when a supporting invoice is needed for transportation. SNT is entered based on the sales document.
• 3.2. Confirmation of Incoming SNT by the Recipient — after the actual receipt of goods for confirmation of acceptance.
• 3.3. Issuance of Corrected SNT — when an error is found in a previously registered SNT (amount, quantity, counterparty details).
• 3.4. Rejection of Incoming SNT by the Recipient — when the actual received goods do not match the data of the SNT (shortage, mis-sorting, defects).
• 3.5. Obtaining Product Identifiers from the ESF IS — linking the nomenclature to system identifiers for goods registered in the ESF IS.

Related Objects: documents of sales/receipts of goods (basis), ESF document (electronic invoice), directories “Counterparties”, “Nomenclature”, virtual warehouse registers, exchange mechanisms with the ESF IS and MPT IS.

7. Extension Points

• Event Subscriptions / Extensions for ProcessingConduct and ProcessingFilling — adding custom logic for reservation or filling from atypical bases.
• Additional Attributes and Information — expanding the composition of data transmitted to the ESF IS.
• Extension of Table Parts — adding columns for industry accounting of marked products.
• Validation Handlers — expanding the list of checks with recording in the “Typical Errors” structure.
• Exchange Formats ESF IS/MPT IS — the relevance of XML schemas and package compositions depends on the version of the state system regulations. Requires verification when updating exchange regulations.