If, when generating a “Notice of Correction” in 1C:Accounting for Kazakhstan, not all electronic invoices are pulled into the document, the most common reason is that the “missing” ESFs have no entries on the DT/CT tab. A document without account movements does not appear in the Notice. The solution is simple: such ESFs need to be reposted — after this the entries will be generated, and when the Notice is filled in again the invoices will be pulled in correctly.
Why this happens
The Notice of Correction is filled in based on posted documents and the movements they generate. If an ESF for some reason did not generate entries on the DT/CT tab, then as far as the fill-in mechanism is concerned such a document “does not exist” — it does not participate in the selection. The absence of entries can occur for various reasons:
- the document was saved (recorded) but not actually posted;
- the entries were “lost” after posting was cancelled, accounting settings were changed, or the configuration was updated;
- the document was entered or edited in a non-standard order, and the movements were not regenerated;
- bulk loading/transfer operations, during which some documents were left without movements.
How to fix it step by step
- Identify which ESFs are not included in the Notice (compare the list of pulled-in invoices with the actual ones for the period).
- Open each problematic ESF and go to the DT/CT tab (document movements).
- If there are no entries there — repost the document (post button / “Post and close”).
- Make sure that after reposting the entries appear on the DT/CT tab.
- Generate (refill) the “Notice of Correction” again — now the document should be pulled in automatically.
- Check the final list of ESFs in the Notice: it should be complete.
If the problem is widespread
When there are many “empty” ESFs, reposting them one by one is inconvenient. In this case:
- repost the documents one by one or use batch document reposting processing, if it is used in your database;
- limit the processing to the required period and document type so as not to affect anything unnecessary;
- after reposting is complete, generate the Notice again — it should collect the full list.
Batch reposting is convenient because in a single run it restores the movements for all selected documents. However, do it deliberately: reposting may affect other registers as well, so it is advisable to make a backup copy of the database beforehand and, if possible, perform the operation at a time when other users are not working with the database.
How to verify that the entries are indeed the cause
Before reposting everything indiscriminately, make sure the issue is really the absence of movements and not something else (wrong period, document status, accounting flag). To do this:
- open one of the “missing” ESFs and look at the DT/CT tab — is it empty;
- compare it with a “normal” ESF of the same period that was included in the Notice — it has entries;
- if the problematic document has entries in place but still is not pulled in, the cause is different (see the section on typical mistakes below), and reposting will not help.
Typical mistakes
- The document is recorded but not posted. Recording a document does not create movements — posting is exactly what is required.
- Refilling without reposting. Refilling the Notice will not create entries for the ESF — you first need to restore the movements in the invoices themselves.
- Incorrectly specified period. Make sure the ESF date falls within the period for which the Notice is being generated.
- Bulk reposting without a backup copy. Before batch processing, save a backup of the database so you can roll back.
- Ignoring the reconciliation of totals. After fixing, be sure to check the completeness of the ESF list in the Notice, and not just the fact that “there are more of them now”.
What to check
- The DT/CT tab of the problematic ESFs — whether there are entries; if absent, repost the document.
- Document status: whether all the required ESFs are actually posted and not just recorded.
- The correspondence between the document date and the Notice generation period.
- The presence and correctness of the batch reposting processing mechanism, if the fix is widespread.
- The completeness of the final ESF list in the Notice after refilling — reconciliation with the actual invoices for the period.
- A backup copy of the database before bulk reposting operations.