- 01
Market
Saudi Arabia
- 02
Written for
CIO, COO
- 03
Decision
Understand why the invoicing system falls short of e-invoicing requirements and how to close the gap
- 04
Languages
EN · AR
The remediation path
Tracing a failed document back to the fix that holds
The path runs upstream, then forward again: from the visible failure to its cause, through remediation in dependency order, into the sandbox, and only then to production. The branch exists because some questions on this path are not engineering questions.
A flow from a surfaced e-invoicing failure, through upstream cause location and fixes in dependency order, to sandbox proof and monitored production cutover, with a branch routing regulatory-scope questions to ZATCA publications and tax advisers.
- 01
The gap surfaces
Documents rejected on submission, notices during an integration phase, or a discrepancy a review turns up. Each failure is recorded with its error detail — the raw material of the diagnosis.
- 02
The cause is located upstream
Each failure is traced to its layer: a field the source system never captured, a structure the generator emits incorrectly, or a connection not readied to the authority’s published specification. One symptom often has causes in more than one layer.
- 03
Fixes land in dependency order
Data before format, format before connection — a compliant structure built on missing fields just fails later and deeper. Live invoicing keeps running throughout; remediation happens beside it, not to it.
- 04
The sandbox proves each fix
The authority provides a test environment, and every remediated document type is exercised against it — normal cases and the awkward ones: credit notes, corrections, the edge cases that failed before.
- 05
Production, then watched
Cutover happens per document type or per issuing system, with acceptance rates monitored so a regression is caught by your dashboards rather than by the authority’s notices.
Not every question is technical
Which obligations apply to your organisation, and from when, are questions for ZATCA’s own publications and your tax advisers. The engineering waits on those answers where it must, rather than guessing them.
The usual causes
Why systems built before the regime fall short of it
Most invoicing estates in the Kingdom were assembled before the e-invoicing regime existed, and the gaps follow from that history in three recognisable layers. The first is data: a compliant document requires fields the source systems were never configured to capture, so they are missing, defaulted or held inconsistently across the ERP, the billing platform and the point of sale. The second is format: what the systems emit as an invoice — a print layout, a PDF, a proprietary export — is not the structured electronic document the requirements describe, and the distance between the two is a generation problem, not a template tweak.
The third layer is integration readiness: reporting to or clearing with the authority’s platform requires an onboarded, secured connection built to its published technical specifications, and a system that has never spoken to a regulator’s platform rarely has one. What makes remediation tractable is that these layers have a natural order — data feeds format, format feeds the connection — and a fixed point of reference: ZATCA publishes the requirements, the specifications and the phases, and the engineering answers to that published text rather than to anyone’s summary of it, this page included.
Sequencing
Closing the gap without stopping the billing that runs the business
The constraint that shapes everything: invoicing cannot pause while it is repaired. So the sequence is built to run beside live billing, with the sandbox absorbing every risk production must not.
Anchor the target in the published requirements
The gap analysis is run against ZATCA’s current published requirements and technical specifications — not against a vendor’s summary or last year’s memory of them — with your tax advisers confirming which obligations are in scope for your organisation. A field-by-field, document-by-document gap list with an authoritative source for every line.
Repair the data at its source
Missing and inconsistent fields are fixed in master data and capture workflows — buyer identifiers, tax registrations, classifications — because defaulting them in the document generator satisfies the format while corrupting the record. Source systems that can populate a compliant document honestly.
Build generation and the connection to specification
Document generation is built or corrected to the required structure, and the connection to the authority’s platform is implemented to its published technical specifications, with the security and sequencing the regime requires. A pipeline that produces and submits the document the requirements describe.
Exercise the sandbox until it is boring
Every document type is tested against the authority’s sandbox — standard flows, credit notes, corrections, and specifically the cases that failed in production before. Cutover is earned by a clean run, not scheduled by a date. Evidence, per document type, that production will accept what the sandbox accepted.
Cut over gradually and keep watching
Production cutover proceeds per issuing system, with acceptance monitored and reconciliation between what was reported and what the ledger holds — and a watch kept on the authority’s publications, because the regime evolves and an unowned integration goes stale. A compliant pipeline with an owner, not a finished project with an expiry date.
Our role
The engineering is ours; the requirements are the authority’s
- 01
Diagnosis across the estate
We trace every rejection and notice to its upstream cause across the systems that issue invoices, and deliver a gap list where each line cites the published requirement it answers to.
- 02
Remediation without interruption
We fix data, generation and integration in dependency order, beside live billing, with every change proven in the authority’s sandbox before production sees it.
- 03
A pipeline your team can keep compliant
We leave monitoring, reconciliation and a documented watch on the authority’s publications with a named owner, because the requirements evolve and the integration must evolve with them.
ZATCA defines what compliance is — the requirements, the phases, the timelines — and your tax advisers confirm what applies to you; our part is making your systems produce, submit and reconcile the documents that published definition describes.
Saudi Arabia’s e-invoicing regime is defined and operated by ZATCA, the Zakat, Tax and Customs Authority; its publications are the authoritative source for all requirements, specifications, phases and timelines. Source
Common questions
What buyers ask
Our documents suddenly started being rejected — what changed?+
Usually one of three things, and the error details tell you which. The checks applied to you may have changed — the regime rolls out in phases and its technical requirements evolve, so validation your documents never faced before can start applying to them. Your own estate may have changed — an ERP update, a new billing module or a data migration can quietly alter what the generator emits. Or nothing changed except coverage: a document type or edge case you rarely issue, a credit note or correction, finally went through the new path and failed as it always would have. The diagnosis starts from the rejection records themselves, read against the authority’s current published requirements rather than against what used to pass.
Our ERP is old and heavily customised — do we have to replace it to comply?+
Rarely. Compliance attaches to the documents your estate produces and submits, not to the age of the systems producing them, and the usual architecture keeps the ERP as the source of record while a compliance layer beside it enriches, structures, secures and submits what the ERP issues. The ERP still needs to capture the required data honestly — that part cannot be outsourced to a layer — so some configuration and master-data work inside it is normal. Replacement enters the picture only when the system cannot be made to hold the required data at all, which is a finding the gap analysis would surface early, not an assumption to start from.
Can we keep invoicing while the compliance gap is being fixed?+
Yes — the remediation is designed around that constraint, because stopping billing is not an option for a running business. The work proceeds beside the live pipeline: data repairs land in the source systems without altering how documents flow today, the new generation and integration path is built in parallel, and everything is exercised against the authority’s sandbox rather than against production. Cutover then happens per document type or issuing system, each one moving only after a clean sandbox run, with the previous path available as a fallback during the transition. What the sequence deliberately avoids is the alternative that feels faster — patching the live pipeline directly and using production as the test environment, with the authority’s platform as the tester.
In this cluster
Diagnose the gap with us
A diagnostic that traces your rejections and notices to their upstream causes and sequences the remediation, sandbox milestones included, without interrupting live invoicing.
Start the conversation
