The reason for rejecting a Notification can be viewed directly in the notification itself in the IS ESF — the system marks the error with a red flag (indicator) on the tab of the document card that contains the discrepancy. It is enough to open the problematic document in view mode and go to the marked tab to understand which section or attribute needs to be corrected.
How to find and view the reason for rejection
The sequence of actions in the IS ESF is as follows:
- Log in to the IS ESF, open the ESF tab and select VAT Offset.
- Find the document that caused the rejection and select it.
- Click View.
- The document card will open — on the tab that contains the error, a red spot (indicator) will be displayed. This is the indication of the problematic spot due to which the notification was rejected.
- After reviewing the marked tab, you will see exactly which section or attribute of the document contains the discrepancy and will be able to make corrections.
Why a Notification gets rejected
A Notification is a document by which the recipient (or the system) informs the sender of disagreement with the data of an issued or received ESF. Rejection means that the document contains a discrepancy that does not allow it to be accepted in the form in which it is drawn up. The red flag on the tab is a way for the IS ESF to quickly show the accountant exactly where the problem lies, without forcing them to re-read the entire document.
Most often, discrepancies are related to one of the blocks of the document card:
- details of the parties (participants of the transaction) — name, BIN/IIN, counterparty status;
- data on goods, works, services — name, units of measurement, codes;
- value and amount indicators — quantity, price, amounts, VAT reflection;
- information on VAT offset and related documents.
The specific nature of the error is always indicated by the system itself — be guided by the tab with the red indicator, not by assumptions.
What to do after the reason is found
Once you have identified the problematic tab and attribute, the further steps depend on where the error was made:
- Determine the source of the data. If the ESF is generated from 1C:Accounting for Kazakhstan, the details must be corrected in the primary document of the accounting system, not only in the ESF form, otherwise the error will return upon re-uploading.
- Make corrections. Bring the problematic attribute into line with the actual data of the transaction and the counterparty data.
- Re-issue or resend the document in accordance with the procedure established for the ESF, so that the recipient can accept it.
- Coordinate with the counterparty. If the discrepancy arose due to a different understanding of the terms of the transaction, clarify the correct values with the other party before re-issuing.
Checking compliance with 1C data
To prevent rejections from recurring, it is useful to reconcile what is sent to the IS ESF with the accounting data:
- check the counterparty card in 1C:Accounting for Kazakhstan — the correctness of the BIN/IIN, name and VAT payer status;
- make sure that the nomenclature, units of measurement and codes are filled in and correspond to the reference books;
- reconcile the amount indicators of the basis document with what is reflected in the ESF;
- check that the date and number of the document do not duplicate previously issued ESF.
If the ESF is uploaded from 1C, it is more convenient to eliminate the error in the primary document itself, and then re-transmit the data to the IS ESF.
Common mistakes
- The accountant sees the fact of rejection but does not open the document card and does not look at which tab has the red indicator — and wastes time searching for the error "blindly".
- Corrections are made only to the ESF form, whereas the data source is the document in 1C; upon re-uploading, the error returns.
- A discrepancy in the counterparty details (BIN/IIN, name) is ignored, which causes the document to be rejected again.
- The document is resent without actually correcting the problematic attribute — simply by resending.
- Disputed values are not coordinated with the counterparty if the reason for rejection is related to the data of the other party.
What to check
- Whether you opened the document card via ESF → VAT Offset → View and found the tab with the red flag.
- Whether the specific attribute or section that caused the discrepancy is clear.
- Whether the data has been corrected in the primary document (including in 1C:Accounting for Kazakhstan), and not only in the ESF form.
- Whether the details of the parties, nomenclatures and amounts correspond to the actual data of the transaction.
- Whether the re-issuance or resending of the document has been performed after correction.
- Whether the disputed values have been coordinated with the counterparty if the discrepancy depends on the other party.