ZATCA e-invoicing: Fatoora phases, waves and what breaks
Saudi e-invoicing is not a filing requirement. It is a systems requirement, and that is why it defeats businesses that treat it as a deadline to meet rather than a project to run.
Under Phase 2, your billing system talks to ZATCA before your customer sees the invoice. Get that wrong and you cannot invoice — which is a commercial failure, not just a compliance one.
The two phases
| Phase 1 — Generation | Phase 2 — Integration | |
|---|---|---|
| Who | All VAT-registered businesses | In waves, by revenue threshold |
| Format | Structured electronic invoice, not paper or PDF | Compliant XML with cryptographic stamp and UUID |
| Standard B2B and B2G | Generated and stored | Cleared by ZATCA before being shared with the buyer |
| Simplified B2C | Generated with a QR code | Reported to ZATCA within 24 hours |
| System | Compliant software | Integrated with ZATCA, with certificate management |
Getting onboarded
Why it changes more than invoicing
Once ZATCA holds structured invoice data in near real time, the VAT return stops being a self-contained declaration. It becomes a figure that either agrees with data the authority already has, or does not. That shifts the compliance risk from the annual audit to the monthly reconciliation — and it rewards clean master data far more than it rewards careful form-filling.
Chartered Advisory assesses your billing system against the Phase 2 requirements, runs the data clean-up that prevents clearance failures, and reconciles reported invoices to your VAT return.
Avail our Saudi VAT servicesThe mistakes that cost the most
- Treating the wave notice as a deadline rather than a project start.
- Assuming existing software is compliant without testing clearance.
- Skipping the data clean-up, then failing clearance on missing customer details.
- Missing the 24-hour window on simplified invoices.
- Not monitoring certificate expiry, and discovering it when invoicing stops.
- Never reconciling reported invoices to declared output VAT.
Where clearance actually fails
| Failure | Root cause | Fix |
|---|---|---|
| Invoice rejected on validation | Missing or malformed mandatory field — customer VAT number, national address, unit code | Master data clean-up before go-live |
| Wrong invoice type | Standard versus simplified applied incorrectly | Rule based on customer type, set in the system rather than chosen by the user |
| Tax category mismatch | Zero-rated or exempt items coded as standard, or the reverse | Tax category set on the product master, not per invoice |
| Simplified invoice late | Reported outside the 24-hour window | Automate reporting; do not rely on an end-of-day manual run |
| Everything stops overnight | Certificate expired | Diarise expiry with an owner and a reminder, not a note in a folder |
What good looks like after go-live
- Daily — clearance success rate monitored; failures investigated the same day rather than batched.
- Weekly — simplified invoice reporting confirmed inside the 24-hour window for every batch.
- Monthly — invoices reported to ZATCA reconciled against output VAT in the return. A gap here is the single most visible discrepancy in the system.
- Quarterly — master data reviewed for new customers and products added without complete tax attributes.
- Annually — certificate renewal, and a check of whether a later wave has changed anything for you.
An evidence-led way to apply this guidance
The useful question in ZATCA e-invoicing: Fatoora phases, waves and what breaks is not simply whether a rule exists. For ZATCA e-invoicing: Fatoora phases, waves and what breaks, the file must prove the facts that make the rule apply. Start the ZATCA e-invoicing: Fatoora phases, waves and what breaks working by writing down ownership, residence, source, registration, filing period and evidence in the statutory form. Then tie each ZATCA e-invoicing: Fatoora phases, waves and what breaks conclusion to licence, commercial registration, contracts, invoices, ledgers and authority acknowledgements. That article-specific exercise separates a defensible ZATCA e-invoicing: Fatoora phases, waves and what breaks position from one built around a label, a memory or a copied rate.
The legal starting point for ZATCA e-invoicing: Fatoora phases, waves and what breaks is the Saudi VAT Law issued by Royal Decree and its Implementing Regulations. The operational check for ZATCA e-invoicing: Fatoora phases, waves and what breaks belongs with ZATCA. Read the instrument, current guidance and actual transaction together for ZATCA e-invoicing: Fatoora phases, waves and what breaks: guidance explains administration, but it does not rewrite the law or repair missing evidence.
Rate discipline. The 15% used below is an explicit case assumption for ZATCA e-invoicing: Fatoora phases, waves and what breaks, not a substitute for checking the rate that applies to the actual period, supply, entity or election. For ZATCA e-invoicing: Fatoora phases, waves and what breaks, replace that assumption with the confirmed current rate before the working is used in a return or invoice.
| Checkpoint | Evidence to place on file | Reviewer question |
|---|---|---|
| Legal trigger | the Saudi VAT Law issued by Royal Decree and its Implementing Regulations | Which fact activates the ZATCA e-invoicing: Fatoora phases, waves and what breaks rule, and where is that fact evidenced? |
| Period and cut-off | Dated contract, invoice, return period and acknowledgement | Does the ZATCA e-invoicing: Fatoora phases, waves and what breaks amount belong in this period rather than the one before or after it? |
| Classification | licence, commercial registration, contracts, invoices, ledgers and authority acknowledgements | Would an independent reviewer reach the same ZATCA e-invoicing: Fatoora phases, waves and what breaks classification from the documents alone? |
| Rate or treatment | Current authority publication saved with the working | Was the ZATCA e-invoicing: Fatoora phases, waves and what breaks source effective on the transaction date? |
| Submission trail | Final computation, payment proof and portal receipt | Can the ZATCA e-invoicing: Fatoora phases, waves and what breaks filed figure be rebuilt without asking the preparer? |
Two worked case files
Worked example 1 — bridge the ledger to the tax or Zakat base. For a file concerning ZATCA e-invoicing: Fatoora phases, waves and what breaks, assume the records show SAR 550,000 as the gross ledger amount tested, SAR 120,000 as the documented item outside the selected base, and SAR 30,000 as the period or classification adjustment. The amount carried to the authority computation for ZATCA e-invoicing: Fatoora phases, waves and what breaks is therefore SAR 400,000:
| Line | Amount | File reference |
|---|---|---|
| gross ledger amount tested | SAR 550,000 | Primary control schedule |
| Less: documented item outside the selected base | (SAR 120,000) | Supporting document index |
| Less: period or classification adjustment | (SAR 30,000) | Reviewer-approved adjustment |
| amount carried to the authority computation | SAR 400,000 | Signed computation |
WORKING 1 SAR 400,000 x 15% = SAR 60,000; SAR 400,000 + SAR 60,000 = SAR 460,000
The arithmetic is the easy part of ZATCA e-invoicing: Fatoora phases, waves and what breaks. The ZATCA e-invoicing: Fatoora phases, waves and what breaks judgement sits in taxable-person status, ownership, source, period, elections and the authority evidence for each adjustment, including why SAR 120,000 and SAR 30,000 were removed. If any ZATCA e-invoicing: Fatoora phases, waves and what breaks answer is weak, keep the amount in the exception list rather than forcing it into a filing, resolution or account.
Worked example 2 — reconcile the authority account before filing. For ZATCA e-invoicing: Fatoora phases, waves and what breaks, assume SAR 1,200,000 as the authority-account control total, SAR 130,000 as the payments and credits already acknowledged, and SAR 65,000 as the supported timing or assessment differences. The open balance before submission for ZATCA e-invoicing: Fatoora phases, waves and what breaks is SAR 1,005,000.
WORKING 2 SAR 1,200,000 - SAR 130,000 - SAR 65,000 = SAR 1,005,000
For ZATCA e-invoicing: Fatoora phases, waves and what breaks, place the SAR 1,200,000 authority-account control total, the SAR 130,000 support for the payments and credits already acknowledged, and the SAR 65,000 schedule for the supported timing or assessment differences beside the final SAR 1,005,000 balance. A ZATCA e-invoicing: Fatoora phases, waves and what breaks reviewer should be able to move from source evidence to control total, from control total to decision, and from decision to the submitted figure without a hidden spreadsheet or oral explanation.
The final quality-control questions
- Has the file for ZATCA e-invoicing: Fatoora phases, waves and what breaks identified the controlling law and the version effective for the relevant date?
- Are the ZATCA e-invoicing: Fatoora phases, waves and what breaks assumptions visibly labelled and separated from enacted rates, thresholds and deadlines?
- Do the SAR 400,000 and SAR 1,005,000 results reconcile to source evidence and the general ledger?
- Is every ZATCA e-invoicing: Fatoora phases, waves and what breaks exception assigned to a person and date rather than buried in a note?
- Has the client or responsible officer approved the ZATCA e-invoicing: Fatoora phases, waves and what breaks facts before submission?
This is the standard that makes ZATCA e-invoicing: Fatoora phases, waves and what breaks useful in practice: the conclusion is stated, the law is named, the numbers can be recomputed, and the evidence survives after the person who prepared the file has moved on.
Sources
This guide is written against the official and clearly labelled professional references below. Rates, thresholds and portal procedures change between reviews, so open the primary source before relying on a figure.
Questions people also ask
What is the difference between Phase 1 and Phase 2?
Phase 1, generation, requires every VAT-registered business to issue and store invoices electronically in a structured form rather than as paper or PDF. Phase 2, integration, connects your billing system directly to ZATCA: standard B2B and B2G invoices must be cleared before they are shared with the buyer, and simplified B2C invoices must be reported within 24 hours.
When does Phase 2 apply to my business?
In waves, announced by ZATCA and set by revenue threshold, with the largest taxpayers integrated first and successive waves reaching progressively smaller businesses. Businesses above SAR 7 million of revenue were already in scope at earlier waves. Check the current wave list against your own revenue rather than assuming you are too small.
Can I keep using my existing accounting software?
Only if it can generate compliant XML, embed the cryptographic stamp and UUID, produce the QR code and integrate with ZATCA for clearance or reporting. Many general packages cannot do this without a certified solution or middleware. This is a systems project with a lead time, not a form to complete before the deadline.
What actually goes wrong in Phase 2?
Almost always integration rather than intent. Clearance failures on malformed XML, missing mandatory fields, certificates that expired without anyone monitoring them, and simplified invoices reported outside the 24-hour window. Each is a technical fault with a compliance consequence, which is why the onboarding needs testing time before the wave date, not on it.
Does e-invoicing change what I file?
Not the VAT return itself, but it changes the evidence behind it. ZATCA holds structured invoice data in near real time, so the return is checked against records the authority already has. A mismatch between reported invoices and declared output VAT is now visible automatically rather than only on audit.
Send the tax year and the transaction or filing involved, and we will tell you what is actually required.
Talk to Chartered Advisory Open the tax calculators