Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You issued an electronic invoice (ESF) to the buyer for 1,160,000 ₸, closed the month calmly — and suddenly an incoming notification lights up in the ESF information system (IS ESF): the system has compared your electronic documents with the counterparty's data (or with the SNF in the virtual warehouse) and found a discrepancy. You have one VAT amount in your invoice, the buyer has another in their data; the quantity according to the SNF does not match the sale; the nomenclature of the traceable goods is "stuck." There is a limited time to process such a notification, and if you remain silent — the next step of desk audit will come. To take this notification into account, analyze it line by line, and record the results of the processing, the configuration has a document "Notification of Discrepancies in the IS CEDM".
1. Purpose
The document records the incoming notification of discrepancies received from the state information system of electronic document management (IS ESF / SNF / virtual warehouse). In it, you see a list of disputed documents, compare your data with the system's data, and mark how the discrepancy has been processed. The document itself is a registration document, a "card" of the notification within the EDM; it usually does not create accounting entries.
2. Where to find
Menu path: section "Sales" (or "Purchases") → block "Electronic Invoices (IS ESF)" → journal of electronic documents and notifications → button "Create" → "Notification of Discrepancies". Some releases also place the list in the section "Reports" → "Electronic Documents".
1C navigation link (the most reliable way to open the list — "Service" → "Go to navigation link," paste and click "Go"):
e1cib/list/Document.NotificationOfDiscrepanciesInISCEDM
The link opens the document journal directly, even if the menu command is hidden in your interface due to rights settings.
2a. How to know your release
Menu "Help" → "About the program" (or the ℹ️ icon in the upper right corner). In the opened window:
- Platform version — for example,
8.3.24.xxxx; - Configuration — "Accounting for Kazakhstan, version 3.0";
- Release — for example,
3.0.74.2.
If your release is lower — some fields and verification rules may differ; update through "Administration" → "Update Configuration".
3. How to fill
The document is short: header + table part with discrepancies. Let's break it down by fields.
| Field | Mandatory | Why and what will happen in case of error |
|---|---|---|
| Organization | ✅ Yes | Data from your accounting is pulled for verification. If you make a mistake in the organization — the notification will go "to the wrong place," and the verification will show false discrepancies. |
| Date | ✅ Yes | Date of receipt of the notification for accounting. It affects selection by period. Enter the actual date of receipt. |
| Number | ✅ Yes | Internal number, assigned automatically. Do not touch it manually. |
| Incoming number / number in IS | ✅ Yes | Notification number in the state system. It identifies the notification when responding. An empty or incorrect field — you won't link your response to the original notification. |
| Date of notification (incoming) | ✅ Yes | Date when the system generated the notification. The execution period is counted from it. |
| Execution period / response period | Preferably | Deadline for processing. Delay = transition to the next stage of desk audit. Keep it in sight. |
| Counterparty | As needed | Filled in if the discrepancy is with a specific partner (discrepancy in ESF). It can be empty if the discrepancy is with SNF/warehouse. |
| Table part "Discrepancies" | ✅ Yes | The core of the document. Each row is one disputed document. |
| — Document (ESF/SNF), its number and date | ✅ | Link to the disputed electronic document. Without it, it is unclear what exactly to correct. |
| — Amount/quantity according to your data | ✅ | What is in your accounting. |
| — Amount/quantity according to IS data | ✅ | What the system/counterparty sees. The difference between these two columns is the discrepancy. |
| — Reason / comment | Preferably | Where you write, where the difference came from, and how it was processed. This is your protection during the review. |
| Status of processing | Preferably | "Received" → "In progress" → "Processed". The status shows that the notification is not forgotten. |
| Responsible | Preferably | Who is handling the processing. Convenient for control. |
The set of header attributes may differ slightly between sub-releases 3.0.74 — this is the only point that should be double-checked in your database; the logic of filling remains the same.
Order of work:
- Create the document, specify the organization and date.
- Transfer the incoming number and date of the notification from IS ESF.
- Fill in the table part: for each disputed ESF/SNF — your data and the system's data.
- For each row, decide: is the discrepancy technical (input error on your part), real (correction/additional ESF needed), or on the counterparty's side.
- Set the status, if necessary — enter a correcting/additional electronic document based on it.
- Post and save.
4. Analyzed example with numbers and entries
Situation. LLP "Astana-Trade" (VAT payer) sold goods to LLP "Esil" on January 15, 2026, and issued ESF No. 121 for 1,000,000 ₸ without VAT, VAT 16% = 160,000 ₸, total 1,160,000 ₸.
On February 3, a notification of discrepancy came from IS ESF: the buyer has taxable turnover of 900,000 ₸ and VAT 144,000 ₸ in their data. The difference is that you shipped an additional item for 100,000 ₸ + VAT 16,000 ₸, but forgot to include it in the ESF.
Filling out the notification:
| Document | According to your data | According to IS data | Discrepancy |
|---|---|---|---|
| ESF No. 121 dated 15.01.2026 | Turnover 1,000,000 / VAT 160,000 | Turnover 900,000 / VAT 144,000 | Turnover +100,000 / VAT +16,000 |
You analyze: the sale in your accounting is correct (1,000,000 + 160,000), but the issued ESF went out with an error — 100,000 less. Therefore, you process the notification with the status "In progress" (it does not create entries), and based on it, you issue a supplementary ESF for the missing amount.
Entries of the notification itself: none — this is a registration document of EDM.
Entries that the original sale has already made (for completeness):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Income from sale of goods |
| 1210 | 3130 | 160,000 | VAT 16% payable |
| 7010 | 1330 | (cost) | Cost of goods written off |
If the discrepancy revealed that you understated the sale (did not reflect the revenue), the correction would look like this — additional accrual of 100,000 ₸ + VAT 16,000 ₸:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 100,000 | Accrued income from sale |
| 1210 | 3130 | 16,000 | Accrued VAT 16% |
In summary: the notification recorded the fact, the additional ESF closed the discrepancy in IS, and the accounting for accounts 6010/3130 was brought into compliance. Change the status of the notification to "Processed."
5. Types of operations
There is no separate field "Type of operation" with entries for the document — it is singular in purpose. However, based on the nature of the discrepancy, the work is divided into scenarios:
- Discrepancy in ESF — turnover/VAT/details do not match between your and the counterparty's invoice.
- Discrepancy in SNF / virtual warehouse — quantity, nomenclature of traceable goods, balances do not match.
- Technical input error — typo in amount/BIN, duplication of document.
- Discrepancy on the counterparty's side — your data is correct, the partner corrects it; you record this in the comment.
6. What is formed upon posting
- No accounting entries. The document is informational and registration.
- Movements in EDM registers — the notification is registered in the journal of electronic documents, linked to disputed ESF/SNF, changes its processing status.
- Electronic documents do not send it themselves. Based on the results of the analysis, you enter based on a correcting response or additional/corrected ESF, which is already sent to IS ESF.
- No movements in VAT, mutual settlements, and warehouse the notification does not directly create — they are created by related accounting documents.
7. Printed forms
- Print of the notification of discrepancies — a list of disputed documents with columns "according to the organization's data / according to IS data / discrepancy".
- Register of discrepancies — tabular export for reconciliation with the counterparty.
Printed forms are called by the "Print" button in the document form. The exact composition depends on the sub-release; if the button is absent, use the output of the table part through "More" → "Output list".
8. Common errors
"The field 'Organization' is not filled" The organization is not selected. Fill it in — without it, the verification does not work.
"Mandatory fields are not filled: Incoming number" The notification number from IS ESF has not been transferred. Copy it from the cabinet exactly.
"The table part 'Discrepancies' is empty" You cannot post the document without rows — a notification without a subject of dispute is meaningless. Add at least one row with the disputed ESF/SNF.
"Document ... is not an electronic document of the organization" You inserted someone else's ESF or a document of another organization. Select the ESF where your organization is the sender/recipient.
"Discrepancy equals zero" (warning) Your data and IS data matched — the row is unnecessary. Delete it or double-check the amounts: you may have made a mistake when entering the "according to IS data" column.
Execution period is overdue 1C does not block posting, but the deadline from the header shows that you are late. Process it by the date in the "Execution period" field.
9. FAQ
Does this document create accounting entries? No. This is a registration document of electronic document management. Entries are created by related documents — sales, correcting or additional ESF, which you enter based on.
What VAT rate is used in the examples? The one in effect in 2026 in the RK — 16%. If you see 12% in old materials — this is an outdated norm, do not apply it for calculations.
Where does the notification itself come from? From the state IS (ESF / SNF / virtual warehouse): the system compares your electronic documents with the data of counterparties and finds discrepancies in turnover, VAT, quantity, or traceable nomenclature.
What to do if the discrepancy is due to an error by the counterparty? Leave your data as is, write the reason in the row, status — "Processed," and the correction is made by the partner in their IS. Your task is to record the position.
What to do if you made a mistake (understated ESF)? Based on the notification, issue a supplementary ESF for the missing amount (in the example: 100,000 ₸ turnover + 16,000 ₸ VAT) and, if necessary, correct the sale — the accrual goes through Dr 1210 Cr 6010 and Cr 3130.
Is the table part mandatory? Yes. Without at least one row of discrepancies, the document cannot be posted — the notification is always "about something."
Does the document affect the VAT declaration (form 300.00)? Directly — no. The declaration is affected by sales and ESF. However, properly processed discrepancies bring your turnovers on 6010/3130 in line with the IS data, and thus with the reporting.
Where to check the deadline for response? In the header — the "Execution period" field, counted from the date of the incoming notification. Delay leads to the next stage of desk audit.
How to quickly open the list of all notifications?
"Service" → "Go to navigation link" → paste e1cib/list/Document.NotificationOfDiscrepanciesInISCEDM.
Can the notification be deleted?