/ THE SHORT ANSWER
- 01Confirm the taxpayer's notified wave before setting the project schedule.
- 02Reconcile invoice-level outcomes rather than accepting a successful batch message.
- 03Assign different owners to data errors, outages and commercial corrections.
/ dotSuper point of view
Invoice integration is operationally complete only when finance can reconcile accepted, pending, rejected and corrected documents.
Make recovery part of readiness
Finance needs a wider view: what was intended, what was sent, what the authority returned and whether the commercial record remains correct.
Agree that view before choosing dashboard colours.
The state model should describe events the business can evidence, rather than compressing preparation, submission and reconciliation into a single completed label.
Read the wave announcement narrowly
It states integration by 1 February 2027 for the targeted cohort and describes notification to affected taxpayers.
[1]
That announcement does not reset an earlier obligation or determine every company's situation.
Record the taxpayer's own notification and the finance owner's assessment.
Group-company schedules should not be copied merely because the entities use the same ERP.
The detailed ZATCA guide distinguishes invoice types and credit or debit notes, while its current portal links preparation and developer resources.
Build coverage from the documents your business actually issues and check current specifications before configuration.
[2] [3]
Keep the project schedule tied to those source records.
If the scope changes, update the document and test inventory together.
Otherwise the implementation can meet its internal schedule while missing a relevant transaction type.
Design three different exception routes
A service interruption needs the integration operator.
A commercial mistake needs finance review of the underlying transaction.
Routing all three to IT wastes time and obscures authority.
Retain a stable internal invoice reference alongside external identifiers and response records.
Staff should be able to locate an invoice from either the ERP or the integration log without guessing which timestamp matches.
Define how an uncertain outcome is investigated before a retry.
A timeout means the caller lacks confirmation; it does not automatically establish that the remote system received nothing.
Follow the applicable technical recovery process.
Keep corrections linked to the original business event.
The treatment of a rejected technical document can differ from correction of an already issued commercial invoice.
Finance should decide the appropriate route using the applicable requirements.
Worked hypothetical: a green batch is incomplete
Its internal transport job reports success, but reconciliation finds 232 resolved invoices, five data exceptions and three with uncertain outcomes.
These are invented counts.
The unresolved total is eight invoices, calculated as five plus three.
The batch is 96.7 percent resolved when 232 is divided by 240 and rounded to one decimal place.
That percentage must not conceal the value or age of the eight exceptions.
The five data cases go to the responsible finance-data owners.
The three uncertain cases remain in an investigation queue until their status is established.
Neither group is silently labelled paid or discarded from the daily report.
The controller signs off a reconciliation that explains all 240 records.
A high success percentage may be encouraging, but the important control is that every invoice has a supported state and an accountable next action.
Require evidence for the release decision
Demonstrate the evidence on representative permitted examples.
Avoid treating an unchecked promise in a proposal as equivalent to an observed result.
Select cases from normal business variation: different customers, relevant document types and corrections.
A large sample of identical invoices provides less useful coverage than a smaller set exercising the paths that can fail differently.
| Case | Expected evidence | Owner |
|---|---|---|
| Normal invoice | Internal reference linked to recorded external outcome | Finance systems |
| Data rejection | Readable reason and approved correction path | Master-data or tax owner |
| Uncertain response | Status investigation before authorised retry | Integration operations |
| Commercial correction | Original event and relevant correction linked | Financial controller |
| Daily reconciliation | Prepared population fully explained by outcomes | Finance operations |
Operate the integration as a finance service
Keep sensitive authentication material out of ordinary support tickets.
A replacement staff member should be able to follow the process without inherited personal knowledge.
Monitor unresolved age and repeat causes alongside technical availability.
An integration can be available while one customer record repeatedly fails.
Fixing that record may matter more than marginally improving average response time.
Automation can classify known errors and assemble evidence.
It should not silently change tax treatment or invent missing buyer information to obtain acceptance.
A technically accepted but incorrect invoice creates a different problem.
Your next step is a rehearsal of one rejected case and one uncertain outcome, followed by reconciliation.
Complete that rehearsal with finance present.
It will reveal whether the remaining work concerns data, software or decision ownership.
What this page cannot conclude
- 01The July 2026 Wave 25 announcement is specific to its stated cohort; earlier notifications and other applicable obligations remain relevant.
- 02The detailed guideline accessed is version 2 from May 2023; current technical specifications and taxpayer instructions must be checked before implementation.
- 03No production Fatoora integration or invoice was tested.
- 04This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Sources
- 01Wave 25 criteria for the integration phase of e-invoicing, 24 July 2026Saudi Zakat, Tax and Customs Authority · accessed Sep 15, 2026
- 02Detailed Guidelines for E-Invoicing, version 2, May 2023Saudi Zakat, Tax and Customs Authority · accessed Sep 15, 2026
- 03E-InvoicingSaudi Zakat, Tax and Customs Authority · accessed Sep 15, 2026
This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 15, 2026). Design Fatoora Recovery Before Your First Rejection. dotSuper. https://dotsuper.net/feeds/applied-systems/saudi-arabia-fatoora-invoice-recovery