ZATCA E-Invoicing Automation: What Phase 2 Integration Actually Requires
ZATCA Phase 2 requires your invoicing system to integrate with Fatoora. What changes, how waves are assigned, and which parts can be automated.
Saudi organizations subject to VAT must issue electronic invoices through a solution that integrates with ZATCA's Fatoora platform. This guide explains what the integration phase requires, how waves are assigned, and which parts of the work automation genuinely removes.
Quick answer
ZATCA e-invoicing automation is the practice of generating, stamping, clearing and archiving tax invoices through a system that connects directly to ZATCA's Fatoora platform, so compliance happens as part of invoicing rather than as a manual step afterwards. Phase 2 — the Integration Phase — began on 1 January 2023 and is being rolled out in waves, with each targeted taxpayer notified at least six months in advance.
Executive summary
Phase 2 changes e-invoicing from a formatting requirement into a systems-integration requirement. The compliance work is real but bounded; the larger and more commonly underestimated task is cleaning the master data your invoices depend on. Organizations that treat the wave notification as a six-month project plan, rather than a deadline to react to, absorb it without disrupting billing.
Key takeaways
- Phase 1 (Generation) began on 4 December 2021 and requires invoices to be produced and stored electronically in a compliant solution.
- Phase 2 (Integration) began on 1 January 2023 and additionally requires the solution to connect to ZATCA's Fatoora platform, use a specified format, and carry additional invoice fields.
- ZATCA assigns Phase 2 in waves by VAT-subject revenue and notifies each targeted taxpayer at least six months before its deadline.
- Phase 2 does not require replacing your ERP. It requires a compliant invoicing layer that integrates with it.
- The most common cause of delay is not the integration itself but incomplete or inconsistent master data — VAT numbers, item codes and customer records.
What is ZATCA e-invoicing automation?
ZATCA e-invoicing automation is the use of connected systems to produce compliant electronic invoices and submit them to the Zakat, Tax and Customs Authority without manual re-entry. It covers invoice generation in the required format, the cryptographic and identifying elements ZATCA specifies, transmission to the Fatoora platform, handling of rejections, and retention of the resulting records.
- E-invoicing (Fatoora) — ZATCA's programme requiring VAT-registered taxpayers in Saudi Arabia to issue and store tax invoices electronically through a compliant solution.
- Generation Phase (Phase 1) — the first stage, effective 4 December 2021, requiring compliant electronic generation and storage of invoices.
- Integration Phase (Phase 2) — the second stage, effective 1 January 2023, requiring the taxpayer's solution to integrate with ZATCA's platform and meet additional technical and business requirements.
How the two phases differ
Phase 1 asked a question about output: are your invoices produced and stored by a compliant electronic solution? Phase 2 asks a question about connection: does that solution talk to ZATCA directly, in the format the authority specifies, with the additional fields it requires?
That difference matters because Phase 1 could often be satisfied by upgrading or configuring existing software. Phase 2 involves an interface to a government platform, which brings certificate management, error handling and monitoring — engineering concerns rather than accounting ones.
| Consideration | Phase 1 — Generation | Phase 2 — Integration |
|---|---|---|
| Effective from | 4 December 2021 | 1 January 2023, in waves |
| Core requirement | Generate and store invoices electronically | Integrate the solution with ZATCA's platform |
| Invoice format | Compliant electronic invoice | Specified format with additional required fields |
| Connection to ZATCA | None required | Direct integration with Fatoora |
| Who is affected and when | All in scope from the same date | Assigned by wave, with at least six months' notice |
How waves are assigned
ZATCA groups taxpayers into waves and notifies them directly. The selection criterion is VAT-subject revenue in a defined reference period, and the threshold has fallen steadily as the programme has extended down the size scale. Wave 24, for instance, covers taxpayers whose VAT-subject revenues exceeded SAR 375,000 during 2022, 2023 or 2024, with integration required by 30 June 2026.
Two practical consequences follow. First, you do not need to guess: ZATCA notifies the taxpayers it targets. Second, the notification is the start of the project, not a reminder of one — the stated notice period of at least six months is the window in which scoping, building and testing have to fit.
What the work actually involves
- Confirm scope — identify every system in the organization that issues a tax invoice, including point-of-sale terminals and departmental billing tools that finance may not have visibility of.
- Choose where compliance lives — inside the ERP, in a middleware layer alongside it, or with a certified solution provider. Each is valid; the choice depends on how many issuing systems you have.
- Close the data gaps — compare the fields your systems currently hold against those the Phase 2 format requires. This is usually where the real effort sits.
- Build and test the interface — validate generation, stamping and clearance against ZATCA's testing environment before any live invoice depends on it.
- Handle rejections deliberately — decide in advance what happens when a submission fails, who is notified, and how the invoice is corrected and resubmitted.
- Monitor continuously — treat failed submissions as an operational metric with a named owner, not an occasional inbox item.
Steps 3 and 5 are the ones organizations underestimate. A missing VAT registration number on a customer record is trivial in isolation and blocking at scale. Connecting invoicing to the ERP integration that already holds your master data removes the re-entry that creates those gaps in the first place, and keeps the system of record unambiguous.
Where automation earns its place
Compliance itself is not optional, so automation is not what makes you compliant — it is what makes compliance cheap and repeatable. The measurable gains are in the surrounding work: preparing invoice data, resolving rejections, reconciling what was submitted against what was accepted, and producing evidence on request.
Organizations that already run procure-to-pay automation on the payable side have most of the ingredients for the receivable side — validated master data, a clean audit trail, and exception routing that puts a human on the cases that need judgement. For finance teams weighing the effort, the automation ROI calculator gives a structured way to estimate the hours currently spent on invoice preparation and correction.
Best practices
- Treat the wave notification as the project start date and work backwards from the integration deadline.
- Fix master data before building the interface, because integration surfaces every inconsistency at once.
- Test in ZATCA's sandbox with real invoice shapes, including credit notes and edge cases, not just a clean sample.
- Give failed submissions a named owner and a daily review, in the same way you would treat a failed payment run.
- Keep the ERP as the system of record and let the compliance layer read from it, rather than maintaining a second copy of customer and item data.
Common mistakes
- Discovering additional invoice-issuing systems after the integration has been scoped for the ERP alone.
- Leaving master-data cleanup until integration testing, when it becomes the critical path.
- Building the happy path only, with no defined process for rejected or failed submissions.
- Treating the deadline as an IT milestone without preparing the finance team for how invoicing changes day to day.
Expert tip
Run a dry inventory before anything else: ask each business unit to name every tool that produces a document a customer treats as an invoice. The list is almost always longer than the finance system suggests, and finding an unlisted billing tool during testing is far more expensive than finding it during scoping.
People also ask
Which ZATCA e-invoicing wave does my company fall into?
ZATCA assigns waves by VAT-subject revenue in a defined reference year and notifies each targeted taxpayer directly. Wave 24, for example, covers taxpayers whose VAT-subject revenues exceeded SAR 375,000 during 2022, 2023 or 2024.
Does ZATCA Phase 2 require us to replace our accounting system?
No. Phase 2 requires a compliant e-invoicing solution that integrates with Fatoora, not a new ERP. Most organizations keep their existing system of record and connect a compliant invoicing layer to it.
How much notice does ZATCA give before an integration wave starts?
ZATCA states that it notifies taxpayers of their Phase 2 wave at least six months in advance.
References
- E-Invoicing roll-out phases — Zakat, Tax and Customs Authority (ZATCA)
- Criteria for taxpayers targeted in Wave 24 of the Integration Phase — Zakat, Tax and Customs Authority (ZATCA)
- E-Invoicing Detailed Guidelines — Zakat, Tax and Customs Authority (ZATCA)
Further reading
- Procure-to-Pay Automation — automating the payable side of the invoice lifecycle
- ERP Integration — connecting compliance systems to the ERP that holds your master data
- Automation for Finance — where automation is applied across Saudi finance functions
Frequently asked questions
Industries we automate
Related reading
Invoice Automation in Saudi Arabia: A Practical Guide for Finance Teams
How invoice automation works end to end for Saudi finance teams — OCR capture, AI validation, three-way match, ZATCA-ready posting, and how to start.
ERP Integration Best Practices
Practical ERP integration best practices — keep the ERP as the system of record, validate data at the boundary, and connect systems cleanly instead of replacing them.
Customs and Shipping Document Automation in Saudi Arabia
Saudi clearance now targets two hours and two supporting documents. Where importers still lose time on paperwork, and which document work automates.
Discuss your process with our Riyadh team
Book a free consultation. We will assess your highest-impact processes and give you a prioritized roadmap with clear ROI, no obligation.