E-invoicing phase two: what changes when you integrate
The first lesson in this track explained that Saudi e-invoicing rolled out in two phases: the generation and storage phase that began in December 2021, and the integration phase that began in January 2023 and applies to groups of businesses based on their revenue. Most businesses passed the first phase quietly, since it only changed what an invoice looks like. The second is heavier: it turns your system from an archive you keep into a connection you use daily.
The core difference between the two phases
In phase one the invoice is generated and stored on your side, and the Authority sees it on request. In phase two your invoicing system connects directly to the Fatoora platform of the Zakat, Tax and Customs Authority, and the invoice becomes part of an electronic path that no longer completes inside your business alone.
| Aspect | Generation phase | Integration phase |
|---|---|---|
| Where the invoice completes | Inside your system | Your system plus the platform |
| Internet connection | Not required to issue | Required to keep the path moving |
| Format | Structured electronic | Specified format with a stamp and technical fields |
| When a mistake surfaces | At review time | At the moment of issuing |
Two different paths depending on invoice type
Tax invoice: cleared before it is handed over
An invoice between businesses, or to a government entity, is sent to the platform before you share it with the buyer, and it is not a valid invoice until it is cleared. In practice this means a wrong VAT number on the buyer stops the invoice before it reaches them, instead of surfacing months later.
Simplified tax invoice: reported after issuing
An invoice to a final consumer is issued and handed over immediately at the point of sale, then reported to the platform within the window the Authority sets, which is twenty four hours from issuance according to what is published on its site. The customer does not wait, but your system is still obliged to send what it issued, on time.
What your system is actually required to do
- Onboard with the platform and obtain the cryptographic stamp certificate for each issuing device.
- Stamp every invoice and chain it to the previous one, so no invoice can be removed from the sequence without a trace.
- Give every invoice a unique identifier and an unbroken sequential counter.
- Produce a QR code generated from the stamped invoice data, not a fixed image.
- Send to the platform and handle its answer: accepted, accepted with warnings, or rejected.
- Block edits after issuing, and correct through a credit or debit note rather than a silent change.
A concrete example
A food distribution business sells through two channels: wholesale to restaurants with tax invoices, and a direct outlet with simplified invoices. In the first week after its integration date, four situations appeared:
| What happened | Effect | The right response |
|---|---|---|
| Wrong VAT number for a restaurant customer | Invoice not cleared, not delivered | Fix the customer record once, not on every invoice |
| Two hour internet outage at the warehouse | Wholesale invoices pending | Hold delivery until clearance, do not improvise a manual invoice |
| A cashier running an old software version | Simplified invoices never reported | Standardise versions and tie each device to its certificate |
| A sale cancelled by deleting the invoice | Broken sequence | Issue a credit note linked to the original invoice |
Notice that three of the four are not technical problems. They are process problems: unclean customer data, improvisation during an outage, and a device outside the system.
A checklist before your integration date
- Know your wave and its date from the official source, not from what circulates informally.
- Ask your vendor one specific question: is this system qualified for the integration phase and onboarded with the platform? Ask for evidence, not a promise.
- Clean up customer records: legal name, VAT number, address.
- Inventory every issuing point: branches, cashiers, field reps, online store.
- Write a documented procedure for a rejection and for a connection outage, and train whoever stands at the point of sale on it.
- Run a full cycle before the date: issue, clear, credit note, report.
The groups covered by the integration phase are announced in waves, and each business is notified before its own obligation date. Always check zatca.gov.sa for your group, the applicable dates, and the current technical requirements.
This lesson is introductory and does not replace the official texts or advice from a tax specialist for your own case.