Saudi Arabia E-Invoicing Compliance: Why Phase 2 Is Now a Business Continuity Issue

Most businesses treat e-invoicing compliance as an IT project.

In Saudi Arabia, it is increasingly becoming a business continuity issue.

The Kingdom's Zakat, Tax and Customs Authority (ZATCA) has continued expanding the rollout of Phase 2 e-invoicing integration through successive waves. The latest development makes the direction particularly clear: the compliance scope is extending beyond larger enterprises and increasingly reaching businesses with significantly lower VAT-subject revenues.

On July 24, 2026, ZATCA announced the criteria for its 25th wave of Phase 2 e-invoicing integration. The wave covers taxpayers whose revenues subject to VAT exceeded SAR 187,500 in any of the years 2022, 2023, 2024 or 2025. Businesses falling within this group are required to integrate their e-invoicing solutions with ZATCA's Fatoora platform by February 1, 2027.

That represents a significant expansion compared with earlier waves.

For finance leaders, the message is straightforward: e-invoicing can no longer be treated as a future technology upgrade or a compliance exercise that can be handled shortly before a deadline. It needs to be considered as part of the organisation's financial systems, governance, operational resilience and business continuity planning.

From Generation to Integration: Understanding Saudi Arabia's E-Invoicing Framework

Saudi Arabia's e-invoicing framework was introduced in two phases.

Phase 1, known as the Generation Phase, became effective on December 4, 2021. It requires taxpayers within the scope of the e-invoicing regulations to generate and store invoices and notes through compliant electronic solutions.

Phase 2, known as the Integration Phase, began on January 1, 2023, and is being implemented progressively through waves.

Under Phase 2, businesses must go beyond simply generating electronic invoices. Their compliant e-invoicing solutions must be integrated with ZATCA's systems, including the Fatoora platform. E-invoices must also meet specified technical and formatting requirements and contain additional information required under the framework.

This distinction is important.

A business may already have an electronic invoicing system and still not be fully prepared for Phase 2.

The question is no longer simply:

"Can we generate an electronic invoice?"

It is:

"Can our invoicing environment reliably generate compliant invoices and integrate with ZATCA's requirements as part of our day-to-day operations?"

That is a much broader business question.

Wave 25 Brings Smaller Businesses Into Focus

The latest wave demonstrates how significantly the scope has expanded.

Wave 25 covers taxpayers whose VAT-subject revenues exceeded SAR 187,500 during 2022, 2023, 2024 or 2025. Targeted taxpayers are required to complete integration with the Fatoora platform no later than February 1, 2027.

This represents a notable change from earlier waves.

Wave 23, for example, covered VAT-registered taxpayers with taxable turnover exceeding SAR 750,000 during the relevant years. Those businesses were required to comply with Phase 2 requirements between January and March 2026.

The change in thresholds illustrates the broader direction of the rollout.

What was once largely viewed as a major-enterprise transformation is increasingly relevant to smaller and mid-sized VAT-registered businesses as well.

For companies that assumed their size would keep them outside the immediate scope of Phase 2, that assumption deserves to be revisited.

Why E-Invoicing Is More Than an IT Project

It is easy to assign e-invoicing to the IT department.

After all, the implementation involves software, ERP systems, APIs, integrations, data structures, invoice formats and technical connectivity.

But the consequences of getting those elements wrong extend well beyond technology.

Invoices sit at the centre of several business processes:

  • Sales and order management

  • Accounts receivable

  • VAT reporting

  • Customer onboarding

  • Finance and accounting

  • ERP workflows

  • Credit notes and adjustments

  • Cash collection

  • Reconciliation

  • Tax documentation and record keeping

If the invoicing system is not ready, the problem can quickly become an operational problem.

A poorly planned integration can create delays in invoice issuance, reconciliation issues, manual workarounds, customer disputes or disruptions to established finance processes.

That is why finance leadership should treat Phase 2 readiness as a cross-functional business initiative, rather than a technology implementation delegated entirely to IT.

1. Map Your Invoicing and ERP Environment Now

The first step is understanding what actually happens when your business creates an invoice.

For many companies, the process is more complicated than it appears on paper.

A typical organisation may have:

  • An ERP system for accounting

  • Separate sales or CRM software

  • Point-of-sale systems

  • E-commerce platforms

  • Billing applications

  • Third-party invoicing solutions

  • Manual spreadsheets

  • Multiple business entities

  • Different invoicing workflows across departments

Before selecting or changing technology, businesses should map the complete invoicing lifecycle.

Identify where invoice data originates, how it moves between systems, where tax information is calculated, who approves invoices, how credit notes are handled and how records are stored.

This exercise can expose integration gaps before they become deadline problems.

ZATCA provides targeted taxpayers with advance notice of their Phase 2 integration requirements. However, that notice period can disappear quickly when ERP changes, vendor coordination, testing and internal approvals are involved.

2. Make Finance and IT Joint Owners

E-invoicing touches both technology and tax compliance.

IT understands systems architecture, integrations, security and software dependencies.

Finance understands tax treatment, invoice workflows, accounting controls, customer requirements and reporting.

Neither function should operate in isolation.

A practical governance structure should therefore involve finance, IT and, where appropriate, tax, legal, procurement, sales and external technology providers.

The objective should be to establish clear ownership for:

  • Regulatory interpretation

  • Technical architecture

  • ERP readiness

  • Data mapping

  • Integration testing

  • Invoice validation

  • Exception handling

  • Record retention

  • Ongoing monitoring

This also helps avoid one of the most common implementation risks: discovering late in the project that a supposedly simple invoice process depends on multiple systems or manual interventions.

3. Do Not Confuse "Electronic" With "Compliant"

One of the biggest misconceptions surrounding e-invoicing is that a business becomes compliant simply because it has moved from paper invoices to electronic invoices.

Phase 2 is more demanding.

Businesses must assess not just whether invoices are digital, but whether their complete invoicing environment meets the applicable technical and regulatory requirements.

This assessment should cover the entire process rather than a single invoice template.

Questions finance and IT teams should ask include:

  • Is the current invoicing solution compatible with Phase 2 requirements?

  • Can it connect with the required ZATCA platform?

  • Are all required invoice fields being captured correctly?

  • How are credit and debit notes handled?

  • Are invoice data flows automated or dependent on manual intervention?

  • How are errors identified and corrected?

  • Are different branches or entities using different systems?

  • Can the organisation maintain appropriate records and audit trails?

  • Has the integration been tested under realistic business scenarios?

These questions are particularly important for businesses operating with legacy systems or multiple disconnected applications.

4. Start With a Readiness Assessment

For businesses approaching a potential ZATCA wave, a structured readiness assessment can provide a much clearer picture of what needs to happen.

The assessment should generally cover four areas.

Regulatory Readiness

Determine whether the business falls within the applicable Phase 2 requirements and identify the relevant ZATCA wave and integration deadline.

Process Readiness

Review how invoices, credit notes, cancellations and adjustments are created, approved and recorded.

Technology Readiness

Assess ERP systems, billing platforms, integrations, data fields, APIs and other technical dependencies.

People and Governance Readiness

Establish who owns implementation, testing, exception management and ongoing compliance.

The output should be more than a generic statement that the company is "working on e-invoicing."

Management should know what systems are affected, what gaps exist, who is responsible for closing them and how much time is required for implementation and testing.

5. Build Testing and Contingency Into the Timeline

  • Integration projects rarely fail because a company has never heard of the requirement.

  • They often struggle because implementation begins too close to the deadline.

  • Testing deserves particular attention.

  • A business should not assume that a successful connection between systems automatically means the invoicing process is ready for production.

  • Testing should consider normal invoices as well as exceptions and less frequent scenarios, including adjustments, credit notes, customer data issues and different transaction types.

  • The objective is to make sure the system works under real operating conditions.

  • Contingency planning also matters.

  • If an integration fails or an invoice cannot be processed as expected, finance teams need a defined process for identifying, escalating and resolving the issue without unnecessarily disrupting billing and collections.

  • This is where e-invoicing becomes a business continuity issue.

The Strategic Implication for Businesses in Saudi Arabia

  • The evolution of Saudi Arabia's e-invoicing rollout sends a clear message about the direction of compliance.

  • Phase 2 is not a single implementation event affecting only the largest organisations. It is a progressive rollout covering different taxpayer groups over time.

  • The 25th wave is particularly significant because of its SAR 187,500 VAT-subject revenue threshold.

  • For businesses that have not yet assessed their position, waiting for a notification before beginning preparation may create unnecessary operational pressure.

  • The better approach is to understand the company's exposure, systems and readiness in advance.

What Finance Leaders Should Do Now

  • Businesses operating in Saudi Arabia can use the current period to establish a practical e-invoicing readiness roadmap.

  • First, confirm your scope. Review your VAT-subject revenues for the relevant years and monitor ZATCA announcements concerning future waves.

  • Second, map your systems. Identify every system and process involved in creating, modifying, approving and storing invoices.

  • Third, assess the gaps. Determine whether your ERP, billing software and integrations can support the applicable Phase 2 requirements.

  • Fourth, establish governance. Make finance and IT joint owners, with appropriate involvement from tax and other affected functions.

  • Fifth, test early. Allow sufficient time for technical integration, data validation, user testing and remediation.

  • Finally, prepare for ongoing compliance. E-invoicing should not be treated as a project that ends on the integration date. Systems, processes and regulatory requirements need continuing oversight.

    Conclusion

Saudi Arabia's e-invoicing journey has moved well beyond the question of whether businesses should digitise their invoices.

The focus is now on whether businesses can operate their invoicing processes in accordance with an increasingly integrated regulatory environment.

The latest Wave 25 announcement reinforces that point. With the applicable threshold falling to taxpayers whose VAT-subject revenues exceeded SAR 187,500 in one of the relevant years, businesses that previously considered Phase 2 a large-enterprise issue need to reassess their position. The February 1, 2027 deadline also demonstrates why preparation should begin well before the final integration date.

For finance leaders, the practical takeaway is simple:

Map the systems. Understand the requirements. Establish ownership. Test early.

E-invoicing compliance in the Kingdom is no longer simply a question of if a business will need to adapt.

For businesses within the applicable scope, it is a question of how prepared they will be when their ZATCA integration wave arrives.