Document "Sources of Origin" — Accounting for Kazakhstan 3.0.74.2

1. Identification

Purpose. The object stores information about the origin of goods within the framework of Kazakhstani accounting: numbers of cargo customs declarations (CCD / goods declaration, GD), numbers of import and indirect tax payment applications (tax return form 328.00), numbers and dates of certificates of origin, HS codes, country of origin. The data is used when accounting for imported goods, maintaining batch accounting of goods, generating electronic invoices (ESF, ESF IS), accompanying invoices for goods (SNT), and filling out tax reporting on turnover within the Customs Union (EAEU).

Important about the object type. By the composition of attributes (see section 2) and purpose, the object acts as an information registrar of goods' origin and, according to the standard logic of the configuration, does not generate accounting entries (see section 5). VAT and cost entries are generated by related incoming documents that refer to the origin data. The specific metadata classification (Document or Reference) in the current version should be checked in the configurator — historically, the storage objects of CCD in BK 3.0 were implemented as elements of the information storage about the batch; this is the only version-specific point that requires verification.

2. Attributes

2.1 Header Attributes

Types Nomenclature, CountryOfOrigin, BatchDocument in evidence are marked as "not defined" — the most likely reference types of configuration are provided; verify in the configurator.

2.2 Table Parts

No table parts were identified in the attached evidence. According to the logic of the object, all information about the origin is stored in the header attributes linked to one nomenclature position/batch. If a table part is present in a specific version (for example, a list of declaration positions), it reflects a line-by-line breakdown of the CCD — check the composition in the configurator.

3. Forms

BSL/descriptions of forms in evidence are not attached. For this type of object in BK 3.0, a standard set of forms is used:

4. Key Module Procedures

Evidence with the BSL code of the module is not attached. Below are typical handlers characteristic of objects of this type (verify their presence and exact implementation in the configurator of the specific version):

• FillProcessing(DataFilling, …) — filling in attributes when entering based on the incoming document/CCD: substitution of nomenclature, country of origin, GD number, HS code from batch data.
• BeforeSaving / AfterSaving — control of the consistency of origin data (consistency of the CCD number, country, and type of origin), normalization of the GD/application number 328.00.
• FillCheckProcessing — when using data in ESF, checking the completeness of attributes required for the ESF line for imported/CU goods (CCD or application number 328.00, HS code).
• ConductProcessing — according to standard logic, empty or absent: the object does not generate movements (see section 5). If conducting is included, it serves only to record the status of the entry.

5. Conducting and Movements

According to standard logic, the object does not generate accounting entries and does not make movements in accounting/accumulation registers. This is a storage of reference information about the origin of goods; in accounting and tax records, data enters through related documents, and in external services — through the export of ESF (ESF IS) and SNT.

Accounting entries for goods to which sources of origin are linked are generated by related incoming/sales documents according to the standard chart of accounts of the RK:

The VAT rate in the RK for 2026 is 16% (the value is substituted in ESF/SNT and in the entries of related documents).

Where the information about the origin actually goes:

• ESF (ESF IS) — section G of the invoice: CCD/application number 328.00, HS code, virtual warehouse accounting flag, position number in the declaration.
• SNT — identification of the product within the CU, country and type of origin.
• Tax return form 328.00 / 300.00 — application number for import, position number.

6. Related Objects and Input Based On

References to:

• Reference.Nomenclature — accounting position of the product;
• Reference.GSVS_Nomenclature — identification within the CU;
• Reference.CountriesOfTheWorld — country of origin;
• Enumeration.OriginTypesWithinCU, Enumeration.DutyTypesWithinCU;
• batch document (BatchDocument) — incoming that forms the batch.

Used in / related to:

• incoming documents for imported and CU goods (receipt, CCD for import, application for import 328.00);
• batch accounting mechanism for goods (linking origin to the batch);
• generation of ESF and SNT (substitution of CCD number, HS code, virtual warehouse flag);
• regulated reporting: tax return form 328.00, 300.00 (VAT register).

Input based on. The typical scenario is filling in information about the origin from the incoming document/declaration through FillProcessing (substitution of nomenclature, country, GD number). Reverse input based on this object is not provided in the standard delivery.

7. Extension Points

• Configuration extension (Extension): adding attributes (for example, additional classifiers for labeling), filling rules via &After("FillProcessing").
• Event subscriptions: control/filling of attributes during BeforeSaving/AfterSaving without changing the standard module.
• Additional attributes and information (BSP): "Properties" mechanism for industry-specific attributes of origin.
• Form modification: adding form attributes and handlers through object/list form extension.
• Integration with ESF/SNT IS: overriding export rules for section G of ESF and SNT fields based on object data.
• Exchange/conversion rules: inclusion of origin information in exchange plans during synchronization.

When making modifications, do not transfer norms from other countries: RK parameters for 2026 — VAT 16%, MRP 4,325 ₸, MZP 85,000 ₸, OPV rates 10%, OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%, PIT 10%/15%.