--- title: "Product data reconciliation in SIBU in 1C:Accounting for Kazakhstan 3.0 — how to fill out, example, entries" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/sverka-dannyh-tovarov-v-sibu-v-1s-buhgalteriya-dlya-kazah-en source: BuhGPT --- # Product data reconciliation in SIBU in 1C:Accounting for Kazakhstan 3.0 — how to fill out, example, entries > **TL;DR:** Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0). You uploaded the SNT, sent a batch of product data to the state system — and got a discrepancy. For one item, your 1C shows 100 units, but 95 went through in SIBU. Or the other way around: the system shows --- Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0). You uploaded the SNT, sent a batch of product data to the state system — and got a discrepancy. For one item, your 1C shows 100 units, but 95 went through in SIBU. Or the other way around: the system shows a balance that you no longer have in your warehouse. Until the figures match, you won't be able to calmly issue new SNTs for this product, and during an audit the tax authority will see the gap. This is exactly when the "Reconciliation of product data in SIBU" document is opened — to match your accounting with what is actually recorded in the state system in a single pass, and to find exactly where the units got lost. 1. Purpose The document matches the data on products in your 1C (balances, HS codes, units of measure) with the data on the same products in SIBU. It reveals discrepancies in quantity and attributes so that you can resolve them before issuing the next electronic documents (SNT/ESF). By itself it does not create accounting entries — it is an auxiliary reconciliation document, but on its basis you correct your accounting. 2. Where to find it The list of documents can be opened in two ways. - Through the menu. The section where you have your electronic documents and work with the virtual warehouse (SNT/ESF) → the "Reconciliation / Virtual warehouse" group → "Reconciliation of product data in SIBU" → the "Create" button. The exact location of the item in the menu may differ across releases and interface settings — this is the only thing worth double-checking in your database; the object itself is unchanged. - Through a navigation link (the most reliable way). The "Service" → "Go to navigation link" menu (or the corresponding "File → Open by link" command), paste: e1cib/list/Документ.СверкаДанныхТоваровВСИБУ The list of documents will open immediately, bypassing the menu search. 2a. How to find out your release The "Help" → "About the program" menu. In the window that opens you can see the platform version (for example, 8.3.xx.xxxx) and the configuration release — the line "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". If your release is older, some fields may look different; go by your own number, not by screenshots from the internet. 3. How to fill it in Fill it in from top to bottom — that way the document will pull in the correct data for comparison itself. Field Required Why it matters and what happens on error Number Filled in automatically Don't touch it. Manual editing breaks the numbering and the subsequent search for the document. Date Yes The balance for reconciliation is taken as of this date. Set the wrong day — and you will compare accounting with SIBU at different moments and get false discrepancies. Organization Yes (if there are several in the database) The organization's IIN/BIN and data from SIBU are pulled in based on it. Make a mistake — and you will reconcile someone else's products. Warehouse Yes, if accounting is kept by warehouses Determines which 1C balances to take. The wrong warehouse — and there is a "shortage" where everything is fine. Responsible person Desirable Who carried out the reconciliation. Will come in handy when investigating discrepancies a month later. Comment No Write in the reason for the reconciliation ("before submitting a report", "after inventory") — you will be helping yourself. Tabular part (products). Filled in with the "Fill" button — there are usually options "Fill by 1C balances" and "Load data from SIBU". Use both so that two figures appear in one row: - Item — the product. Matching is done by HS code / GSVS and name. - HS code — a key attribute. If the code in 1C and in SIBU is different, the product will not "collapse" into a single row, and you will see a phantom discrepancy. Check the codes first. - Unit of measure — must match the one in which the product is registered in SIBU. Pieces against kilograms will give an absurd difference. - Quantity according to 1C data — how much is recorded on your side. - Quantity according to SIBU data — how much is in the state system. - Discrepancy — the difference, calculated automatically. This is exactly the column you work with. After filling in, check the rows with a non-zero discrepancy, investigate the cause of each, and post the document with the "Post and close" button. 4. Worked example with entries Situation. LLP "Astana Stroy" (VAT payer), on September 3, 2026 reconciles the product "VVG cable 3×2.5". - According to 1C data (account 1330 "Goods"): 100 coils at a cost of 20,000 ₸ = 2,000,000 ₸. - According to SIBU data: 95 coils. - Discrepancy: –5 coils (fewer in SIBU). The reconciliation document shows the difference but makes no entries. You investigate: 5 coils were sold to a customer, the ESF and SNT were issued (which is why the state system wrote them off), but the sale was not posted in accounting. The selling price is 25,000 ₸/coil excluding VAT. On the basis of the reconciliation you create the missing sales document for 5 coils. It is what generates the entries: Dr Cr Amount, ₸ Description 1210 6010 125,000 Income from sales (5 × 25,000) 1210 3130 20,000 VAT 16% on the sale (125,000 × 16%) 7010 1330 100,000 Cost of goods written off (5 × 20,000) Total receivable from the customer: 145,000 ₸. After posting the sale, a repeat reconciliation will show 0 for the cable — the 1C and SIBU balances have matched (95 = 95). If the discrepancy had a "+" sign (100 in SIBU, 95 in 1C — that is, the state system "knows" about a product that is not in the accounting), you would, on the contrary, record the surplus: Dr 1330 Cr 6280 for 5 × 20,000 = 100,000 ₸. 5. Types of operation The document does not switch operation types like sales or receipt — it works in a single reconciliation mode, but by result it closes three types of discrepancy: - Shortage in 1C relative to SIBU (fewer in the state system) — the product has been disposed of but not written off. You fix it with a sale or a write-off of goods. - Surplus in 1C relative to SIBU (fewer in the state system through your fault — an SNT was not issued) — either you record it or you complete the accompanying waybill. - Discrepancy in attributes (HS code, unit of measure, name) — with matching quantity. You correct the item card so that the data matches SIBU. 6. What is generated upon posting - Accounting entries — the reconciliation document does NOT generate them. This is fundamental: it records the result of the comparison, not the movement across accounts. Entries appear only in the documents that you create on its basis (sale, write-off, recording of surplus, adjustment). - Movements in information registers — the recorded result of the reconciliation is saved: 1C balances, SIBU balances, and the discrepancy as of the document date. This is your trail for the auditor and for the next reconciliation. - Electronic documents (ESF/SNT) — the reconciliation itself does not issue them. But it is exactly from its results that you understand where you need to complete an SNT or ESF via the ESF IS so that the virtual warehouse matches the accounting. 7. Printed forms - "Reconciliation of product data in SIBU" — the main form with the columns "Quantity per 1C", "Quantity per SIBU", "Discrepancy". It is printed and filed with the investigation report. - "List of discrepancies" — only the rows where the difference is not equal to zero; convenient to give to the storekeeper or manager for explanations. Printing is invoked with the "Print" button on the document form. 8. Common mistakes - "Item not matched: HS code not found". This means the product's HS code in 1C is not filled in or differs. Open the item card, specify the code exactly matching SIBU, and refill the tabular part. - "Discrepancy in all items". Almost always — the wrong date or the wrong warehouse: you compared balances at different moments. Check the document date and the "Warehouse" field. - "No connection to the ESF IS / SIBU data not loaded". Authorization in the service has not been passed or the internet is unavailable. Check the exchange settings with the ESF IS and repeat the SIBU data load. - "Unit of measure does not correspond to SIBU data". In 1C the product is in pieces, in SIBU — in a different unit. Bring the unit of measure into line with the one registered in the state system. - The discrepancy "collapsed", but the quantity is actually different. Two different items have the same HS code and merged into one row. Separate the codes or reconcile by a specific item. 9. FAQ Does the "Reconciliation of product data in SIBU" document make entries? No. It is an auxiliary reconciliation document. Entries are generated by the documents you enter based on its results: sale, write-off, recording of surplus, adjustment. What is a discrepancy with a "minus" sign? There is less product in SIBU than in your 1C. Usually this means: the product was disposed of (sold, written off), this went to the state system via SNT/ESF, but the document was not posted in accounting. Look for an unclosed sale or write-off. And a discrepancy with a "plus" sign? There is less product in 1C than in SIBU. Either you have not recorded a surplus, or you did not issue an SNT for the disposal. Investigate by the specific item. By which attribute are products matched? By the HS code (GSVS) and name, taking the unit of measure into account. If the code in 1C and SIBU is different — the product will not be matched, and you will see a false discrepancy. As of what date is the balance taken? As of the document date. Therefore, set the date as of which you want to reconcile accounting with SIBU (usually — the end of the period or the inventory date). Do I need to post the document if there are no discrepancies? Yes, it is worth posting and saving: you will record the fact that as of this date the accounting and SIBU matched. This is your argument during a tax audit. How do I fix a discrepancy in the unit of measure? Bring the unit of measure in the item card into line with the one in which the product is registered in SIBU, and refill the tabular part of the reconciliation. Why is data not loading from SIBU? Most often — authorization in the ESF IS has not been passed, the digital signature certificate has expired, or there is no internet. Check the exchange settings and repeat the load. Does the VAT rate affect this document? The reconciliation itself — no, it compares the quantity and codes of products. But VAT will appear in the documents you create based on its results: for a sale in 2026 a rate of 16% is applied (entry Dr 1210 Cr 3130). Can I create a corrective document straight from the reconciliation? Yes, use the "Create based on" button — from there you enter the sale, write-off, or recording of surplus of goods that will close the discrepancy with entries. 10. Related documents What it is entered on the basis of / what it is linked to: - Inventory of goods — the reconciliation is often done after an inventory in order to match the actual balance not only with the accounting but also with SIBU. - SNT and ESF (ESF IS) — they are exactly what generates the data in SIBU that the comparison is made against. What is entered on the basis of the reconciliation (the "Create based on" button): - Sale of goods and services — to close a shortage with goods that were sold but not posted. - Write-off of goods — if the shortage is due to spoilage/shortfall without a sale. - Recording of surplus goods — to formalize a surplus that exists in SIBU but not in the accounting. - Adjustment / change of item attributes — to eliminate discrepancies in the HS code and units of measure. How to find out your release: "Help" → "About the program" — there the platform version and configuration release are indicated. The guide was prepared for 1C:Accounting for Kazakhstan, edition 3.0, release 3.0.74.2. The numerical norms are given as of 2026 (VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_