Cancel a consolidated e-invoice, and get its receipts reported again
Step 5 of cancelling and correcting a validated e-invoice: what changes when the e-invoice you need to cancel is a consolidated one. A consolidated e-invoice has no single sales document behind it, so the choice you make in Step 3 works differently, and cancelling it leaves its receipts unreported until support pushes them back to the Batch Pool and the next consolidation run picks them up. It follows Steps 2 to 4, and it is the one step of this task that cannot wait.
- Step 5: if it is a consolidated e-invoice, act immediately.
Step 5: If it is a consolidated e-invoice, act immediately
Outcome: the cancellation is under way despite the extra constraint consolidated e-invoices carry.
A consolidated e-invoice has no single sales document behind it — it reports hundreds of receipts at once. Only cancel for edit and resubmit works — and the other three fail in three different ways. Void original document is refused with “Can not void the generic document” before LHDN is called: nothing happens, and you have lost only time. Regenerate new e-invoice is the dangerous one. It cancels the e-invoice at LHDN first, then tries to rebuild it from a source document a consolidated e-invoice does not have — so the month’s consolidated e-invoice is Cancelled at LHDN and nothing replaces it. New reversal document fails on the same missing document, and that failure is only written to the log: no Request Error on the queue row, no e-mail, nothing on the screen.
Afterwards, the receipts that were inside the cancelled consolidated e-invoice still need reporting, and they will not come back on their own. Cancelling changed the e-invoice record and nothing else: every receipt still carries the cancelled e-invoice’s number, still shows as matched to it, and its Batch Pool row was used up when the month was first submitted. No scheduled run will pick those receipts up again, because the run only looks at Batch Pool rows that have not been used.
What has to happen is that a fresh Batch Pool row is created for each of those receipts, named one by one, after which the ordinary consolidation run gathers exactly those and nothing else. There is an endpoint that does precisely this, push-gendoc-to-batch-pool, and it refuses to give a receipt a second row if one is already open, so asking twice cannot double-report anything. It is not on any screen. This is support’s job, not a self-service action — ask for it in the same request, and ask for it in those words: “please push these documents back to the batch pool”, not “please re-run consolidation for March”, which would sweep in everything else in the month as well.
What success looks like for this part
The e-invoice reads Cancelled, and your support request said it is consolidated and asked for its receipts to be pushed back to the Batch Pool. Support has confirmed the receipts are back in the Batch Pool, and the next consolidation run has consolidated exactly those receipts; until then, the e-invoice reading Cancelled is the record that tells you they are unreported. When you are done, run the whole task’s success check.
Common mistakes in this part
| Mistake | What you see | Fix |
|---|---|---|
| Using void original document on a consolidated e-invoice | “Can not void the generic document”, and LHDN was never called | Use cancel-for-edit-and-resubmit, or raise a support request immediately |
| Checking the Discrepancies Report after a consolidated e-invoice was cancelled, and reading a clean month as proof | Nothing appears under Exists in ERP, Missing in E-invoice — but the receipts are unreported at LHDN | The report counts a receipt as reported when it is attached to an e-invoice, whatever that e-invoice’s status. Check the e-invoice record itself: if it reads Cancelled, every receipt inside it needs pushing back to the Batch Pool |
| Using regenerate new e-invoice on a consolidated e-invoice | The e-invoice reads Cancelled at LHDN and no replacement appears — every receipt inside it is now unreported | Never choose it on a consolidated e-invoice. If it has already happened, raise a support request the same day and say the consolidated e-invoice was cancelled and not regenerated |
The mistakes that span the whole task are on the front page.
Related documentation
- Cancelling and Correcting a Validated E-Invoice: the whole task, with its success check.
- My E-Invoice Admin Applet: where the receipts are after a consolidated cancellation, and what puts them back.
- The Month-End E-Invoice Cycle: where most wrong e-invoices are discovered.