RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Document "Data Reconciliation of Goods in the SIBU" - Technical Description (Accounting for Kazakhstan 3.0.74.2)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Версия статьи:📘 Для бухгалтера⚙️ Для тех-специалиста

Document "Data Reconciliation of Goods in the SIBU" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

Applies to: 1С:Бухгалтерия для Казахстана, release 3.0.74.2 · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — Эксперт по 1С и бухгалтерскому учёту, преподаватель-практик

1. Identification

Parameter Value
Full name Document.DataVerificationOfGoodsInSIBU
Navigation link e1cib/list/Document.DataVerificationOfGoodsInSIBU
Synonym not set (displayed by name in the metadata tree)
Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2
Object type The object is registered in the "Documents" branch; in terms of actual implementation, it is a verification tool (report) based on the standard reporting mechanism (analogous to SCD)

Purpose. The object is intended for reconciling data on inventory (TMC) between accounting (inventory accounts, primarily 1330) and data from virtual warehouses — a register that supports inventory accounting in the context of the ESF / SNT system (traceability system of goods in the RK). It is used by accountants and controllers to identify discrepancies in inventory balances between two data sources: the accounting contour and the electronic document contour (ESF, SNT, virtual warehouses).

Reconciliation is usually performed during periodic checks (monthly, quarterly closing) or when discrepancies in balances are detected. The analysis is built by nomenclature in terms of accounting accounts, warehouses, and sources of goods.

Where to find in 1C: section "Nomenclature and Warehouse" → "Reconciliation of TMC according to accounting data and VS" (command "Reconciliation of data on inventory items in virtual warehouses with accounting data").

Important: despite being registered in the "Documents" branch, the object is not a posted primary document — it does not generate accounting entries and movements in registers, but reads data for comparison. More details in section 5.


2. Attributes and table parts

2.1 Header attributes (reconciliation parameters)

Name Type Mandatory Purpose
StartPeriod xs:dateTime DontCheck The start date of the analysis period. Must be validated in BeforeLayoutCompilation. Defines the moment from which TMC balances are analyzed.
EndPeriod xs:dateTime DontCheck The end date of the period. Forms the upper limit of the time range for sampling from registers.
OrganizationListRepresentation xs:string DontCheck String representation of selected organizations for the report header and interface.
AdditionalFieldsPlacement xs:decimal DontCheck Method of placing additional fields in the layout (in rows, in columns, etc.).
DetailingMode xs:boolean DontCheck Flag for detailing mode when double-clicking on a value.
AccountList ValueList(ChartOfAccountsRef.Standard) DontCheck List of accounting accounts for filtering (multiple selection from the "Standard" chart of accounts). Narrows the analysis to specific TMC accounting accounts (typically — 1330).
ByAccounts xs:boolean DontCheck Grouping/detailing by accounting accounts.
BySourcesOfOrigin xs:boolean DontCheck Grouping/detailing by sources of origin of goods (receipts from different suppliers, batches, SNT).
ReportType xs:string DontCheck Identifier of the report generation variant (set of indicators and groupings).

2.2 Table parts

Grouping — management of groupings and detailing (analogous to SCD dimensions):

Name Type Purpose
Usage xs:boolean Whether the grouping is included in the report generation.
Field xs:string Identifier of the grouping field (Nomenclature, Warehouse, etc.).
Representation xs:string User representation of the field for the interface and report.
GroupingType EnumRef.StandardReportDetailingType Level of detailing: grouping, detailed records, etc.

AdditionalFields — additional analytical dimensions added to the report (set of columns beyond the standard ones). Each row describes a field, its representation, and placement according to the attribute AdditionalFieldsPlacement.


3. Forms

Form Purpose
Main form (settings and results form) Input of reconciliation parameters (period, organizations, AccountList, flags ByAccounts / BySourcesOfOrigin), launching compilation and outputting results in a tabular document with discrepancies.
Variant / settings form Setting up groupings (table part Grouping), additional fields, and report type (ReportType, AdditionalFieldsPlacement).

Forms are built according to the model of standard reports in the configuration: the user sets the selection and groupings, and the result is output in a layout with support for detailing (DetailingMode).


4. Key procedures of modules

From evidence, one key point is confirmed; the others are standard handlers for this type of object.

  • BeforeLayoutCompilation — performs validation before building: checks the filling of StartPeriod (mandatory parameter of the analysis period), forms the time range StartPeriod … EndPeriod, applies selection by AccountList and organizations, sets groupings from the table part Grouping. Manages the placement of additional fields according to AdditionalFieldsPlacement.

Standard handlers (typical for the reconciliation/reporting tool):

  • OnResultCompilation / layout generation — selection of balances from two sources (accounting and virtual warehouses), matching by key (Organization + Nomenclature + Warehouse + [Source of origin]) and calculating the discrepancy column.
  • Detailing / DetailingProcessing — detailing the indicator down to the registering documents when DetailingMode is enabled.
  • OnPeriodChange / flag handlers — restructuring the composition of groupings when switching ByAccounts and BySourcesOfOrigin.

5. Posting and movements

The object is not posted and does not generate movements in accounting or accumulation registers. It is an analytical reconciliation tool: it only reads and matches data from two contours.

Source 1 — accounting (accounting register "Cost Accounting"): inventory balances by account 1330 "Goods" (if necessary — other accounts from AccountList) in terms of sub-accounts "Nomenclature" / "Warehouses". These accounts participate in standard postings of the inventory contour:

Operation Dr Cr
Receipt of goods from the supplier 1330 3310
Input VAT on receipt (16 %) 1420 3310
Sale of goods (income) 1210 6010
VAT on sale (16 %) 1210 3130
Cost of goods sold 7010 1330
Payment by the buyer 1030 1210

The VAT rate for the RK in 2026 is 16 % (3130 "VAT payable", input VAT — 1420).

Source 2 — virtual warehouses (goods accounting register of the ESF/SNT system): balances formed by issued ESF and SNT (accompanying invoices for goods). This contour records the movement of goods from the perspective of electronic document flow and traceability.

Reconciliation result — a table of balances "Accounting vs Virtual Warehouse" with a discrepancy column for each nomenclature item (and, when BySourcesOfOrigin is enabled, by sources/batches). A non-zero discrepancy indicates an unposted/unissued ESF or SNT, an error in assigning to the warehouse, or a discrepancy in quantity between primary accounting and electronic documents.


  • Register of virtual warehouses of the ESF system — the main source of the electronic document contour.
  • ESF (electronic invoice) and SNT (accompanying invoice for goods) — documents that generate movements in virtual warehouses.
  • Documents of the inventory contour of accounting: "Receipt of goods and services", "Sale of goods and services", "Transfer of goods", adjustments — generate balances on account 1330 (data source of accounting).
  • Chart of accounts "Standard" — source of values for the attribute AccountList.

Input based on for this object is not provided: reconciliation does not generate new documents. As a result, the user manually adjusts ESF/SNT or primary accounting documents until discrepancies are resolved.


7. Extension points

  • Configuration extension (without removing from support): adding intercepting handlers to compilation procedures for additional filtering or new discrepancy columns.
  • Additional fields / variants (ReportType) — standard mechanism for adding analytical dimensions without changing the code.
  • New groupings — through the table part Grouping and StandardReportDetailingType.
  • List of reconciliation accounts — parameterized through AccountList; in case of non-standard inventory accounting (for example, using additional sub-accounts to 1330), the composition is set without modification.
  • Integration with the ESF system — connection points to services for obtaining data from virtual warehouses (updated along with integration releases; version-dependent).

Requires verification on a specific release: the exact composition of the source register of virtual warehouses and API integration with the ESF system — they are accompanied by separate subsystems and may change between versions of the exchange platform.

Частые вопросы

Does "DataVerificationOfGoodsInSIBU" generate accounting entries?
No. Despite being placed in the "Documents" section, the object does not generate entries or movements. It only reads and matches the inventory balances from two systems — accounting (account 1330) and virtual warehouses of the ESF/SNT information system.
Which accounts are involved in the reconciliation?
The main inventory account is 1330 "Goods". The list of accounts is defined by the attribute ListOfAccounts from the "Standard" chart of accounts. Related accounts in the inventory system: 3310 (Accounts Payable), 1210 (Accounts Receivable), 6010 (Revenue), 7010 (Cost of Goods Sold), 3130 and 1420 (VAT payable and input VAT).
What does a non-zero discrepancy in the report mean?
A discrepancy between the balance in accounting and the balance in the virtual warehouse indicates an unprocessed or unregistered ESF/SNT, an error in assigning goods to the warehouse, or a difference in quantity between primary accounting and electronic documents. Corrections are made manually in the relevant documents.
What VAT rate is used in the inventory system entries for the RK in 2026?
16%. VAT payable is reflected in account 3130, and input VAT on receipts is recorded in 1420. The value of 12% pertains to previous periods and is not relevant in the 2026 configuration.

Read also

Источники

Была ли статья полезна?
💼 Нужна помощь с 1С или учётом? Слава КВЦ — многолетняя практика в 1С в Казахстане. Изучите разложенный НК РК 2026 или спросите в чате BuhGPT — ответит за секунды.