- Market
- Saudi Arabia
- Written for
- CIO, COO
- Languages
- EN · AR
The problem
The regulator defined the invoice; your systems predate the definition
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
Saudi Arabia’s e-invoicing regime — FATOORA — is defined and operated by ZATCA, the Zakat, Tax and Customs Authority. ZATCA publishes the requirements: what an electronic invoice must contain, how it must be structured and secured, and how it is reported to or cleared with the authority. For the obligation itself — which rules apply to your organisation and from when — ZATCA’s published requirements and your tax advisers are the authority, and nothing on this page substitutes for either.
What the requirements leave to you is the harder, quieter half: making an estate of systems that predate them comply, invoice by invoice, without stopping the billing that runs the business. An ERP configured a decade ago abroad, a billing platform, a point-of-sale fleet, a subscription system — each issues something it calls an invoice, and typically none of them captures every required field, emits the required structure, or has ever spoken to a tax authority’s systems. Closing that gap is not a setting; it is integration engineering against a moving estate, and treating it as a checkbox is how organisations end up compliant on paper and failing in the field mapping.
The architecture
Every invoice source, one compliance boundary, one story for the auditor
The alternative — each system integrated separately with the authority’s platform — multiplies every future requirement change by the number of systems. A single boundary pays for itself the first time the requirements evolve.
A surface diagram: ERP, billing platform, point of sale and other invoice issuers feed one e-invoicing boundary that validates, enriches, secures and submits invoices, producing compliant invoices, authority reporting, an archive and audit trail, and reconciliation back to the ledger.
ERP invoices
Sales and credit notes from the system of record.
Billing platform
Recurring and usage-based charges.
Point of sale
High-volume simplified invoices from stores and branches.
Other issuers
Subscription, marketplace or bespoke systems that also invoice.
What we do
The e-invoicing boundary
Validates and enriches each invoice to the required structure, applies the required security and sequencing, submits to the authority’s platform, and records the outcome — one implementation of the requirements, however many systems feed it.
Compliant invoices issued
In the structure and form the regime specifies.
Reporting to the authority
Submissions and their acknowledgements, logged per invoice.
Archive and audit trail
What was issued, when, and what the authority answered.
Reconciliation to the ledger
Reported invoices matched back to the ERP, so the two never drift apart silently.
When the published requirements change, one boundary changes with them — not five systems on five vendor timelines.
Where it goes wrong
The four ways e-invoicing projects come back to haunt finance
These are the patterns we are usually called in after. Each is cheaper to prevent than to unwind.
- 01
The data was never there
A compliant invoice requires fields the source system never captured — a buyer identifier here, a classification there. Defaulting or guessing them satisfies the format and corrupts the record; the honest fix reaches upstream into master data, which is why the gap analysis runs field by field before any integration is built.
- 02
Five systems, five integrations
Each issuing system wired separately to the authority’s platform works on day one and becomes five maintenance burdens by the first requirements update — each on its own vendor’s schedule, each failing in its own way, none telling finance a single story.
- 03
Compliance as a finished project
The regime evolves — requirements are published, phases extend to new groups of taxpayers, technical specifications are updated. An integration built as a one-off, with no owner and no watch on ZATCA’s publications, is compliant until the first change it never heard about.
- 04
Reported and recorded drift apart
A submission fails quietly, a credit note is issued in the ERP but never reported, a retry duplicates. Without routine reconciliation between what the authority acknowledged and what the ledger holds, the discrepancy is found by an auditor — the most expensive person to find it.
Our role
The engineering we do between your systems and the FATOORA platform
- 01
The estate, mapped honestly
We inventory every system that issues an invoice and run the field-level gap analysis against the published requirements, so the plan starts from what your data actually holds rather than what the vendor brochure assumed.
- 02
The boundary, built and proven
We build the single boundary that generates, secures and submits invoices from every source, tested against the authority’s integration environment before a production invoice touches it, with failure handling that never loses an invoice silently.
- 03
The regime, kept up with
We watch ZATCA’s published updates and carry them into the boundary as scheduled engineering work, with reconciliation to the ledger run as a routine control — so compliance is an operated capability, not a certificate on a wall.
Which obligations apply to your organisation, and from when, is a question for ZATCA’s published requirements and your tax advisers; we build and run the engineering that lets your systems meet what they determine.
The Zakat, Tax and Customs Authority (ZATCA) defines and operates Saudi Arabia’s e-invoicing regime and publishes its requirements. Source
Common questions
What buyers ask
Our ERP vendor says it already supports Saudi e-invoicing. What is left to do?+
Usually the parts the vendor cannot see from outside your estate. "Supports e-invoicing" typically means the ERP can emit an invoice in the required structure when given complete, correct data — and the work left is exactly that condition: fields the implementation never captured, master data that fails validation, the other systems in your estate that also issue invoices and are not the ERP, and the reconciliation between what was reported and what your books hold. The vendor capability is a genuine head start; the estate-level engineering around it is what this engagement supplies.
Invoices leave our company from four different systems. Must each one be integrated with FATOORA separately?+
It is possible and we advise against it. Four separate integrations mean four implementations of the same requirements, four places to update when the published specifications change, four failure modes, and no single record finance can trust. The structure that ages well is one boundary: every issuing system feeds it in its own native shape, and the boundary owns validation, security, submission and the audit trail once. The per-system work then shrinks to a mapping into the boundary — much smaller, and testable system by system without touching the compliance logic.
The e-invoicing requirements keep evolving. How does the integration avoid going stale?+
By being designed for change and owned after go-live. Structurally, the single-boundary architecture confines requirement changes to one place, and the mappings from source systems rarely need to move when the authority’s specifications do. Operationally, someone has to watch ZATCA’s publications, translate each update into scheduled engineering work, and re-verify against the authority’s integration environment before the deadline — we run that as part of the engagement or hand it to your team with the runbook. For what any given update obliges you to do and by when, ZATCA’s published requirements and your tax advisers remain the reference; our job is that your systems can do it.
In this cluster
Map your invoicing estate
A mapping session that lists every system in your estate that issues an invoice, the data each is missing, and the sequence for bringing them through one compliant boundary.
Start the conversation
