ZATCA Phase 2: What Changes and Who Must Comply

ZATCA Phase 2 moves Saudi Arabia's e-invoicing requirements beyond electronic invoice generation. Businesses brought into scope must connect their invoicing systems with ZATCA, use the required invoice format, and support the technical controls needed for integration.

What Is ZATCA Phase 2?

ZATCA Phase 2 is the Integration Phase of Saudi Arabia's electronic invoicing program. It requires businesses within the applicable scope to integrate their electronic invoicing solutions with ZATCA's systems and meet additional technical and business requirements.

The main difference from Phase 1 is the system connection. Phase 1 established electronic invoice generation and storage. Phase 2 adds integration, structured invoice data, and technical requirements that affect the software used to create and process invoices.

For businesses entering a new Phase 2 wave, compliance is therefore a technology and integration task, not simply an accounting procedure.

How Is Phase 2 Different From Phase 1?

Phase 1 focuses on generating and storing electronic invoices through a compliant electronic solution. Phase 2 builds on that foundation by requiring the electronic invoicing solution to integrate with ZATCA.

The distinction matters when a company already has an invoicing system. A system that works for basic electronic invoice generation may still require changes before it can support Phase 2 integration.

Businesses can review GO-Globe's ZATCA e-invoicing services in Saudi Arabia to understand how electronic invoicing connects with business software and ERP systems.

Who Needs to Prepare for Phase 2?

Businesses that fall within a ZATCA Phase 2 implementation wave need to prepare for the applicable integration requirements. The implementation is carried out progressively, so companies should confirm their notification, integration date, and applicable technical requirements with ZATCA.

For businesses newly brought into scope, including the specified Wave 24 and Wave 25 groups, the key question is whether the current ERP, POS, or invoicing platform can support the required integration.

What Changes Under ZATCA Phase 2?

ZATCA Phase 2 introduces changes to the relationship between a company's invoicing system and ZATCA. The system must support the required electronic invoice format and the technical integration process.

The practical impact depends on how the business currently creates invoices and where transaction data is stored.

Why Does Real-Time Integration Matter?

Phase 2 requires the business's electronic invoicing solution to communicate with ZATCA through the applicable integration process. This means the invoicing system becomes part of the compliance workflow.

A finance team can no longer treat the government connection as a separate manual step. The ERP or POS needs to handle the transaction data and produce the required electronic invoice information as part of the system workflow.

What Role Do XML and Invoice Data Play?

Electronic invoices require structured data. XML is used to represent invoice information in a machine-readable format rather than treating the invoice only as a visual document.

The ERP or POS must therefore collect accurate information from the underlying transaction and generate the required electronic representation.

This creates a direct relationship between sales data, VAT information, customer details, invoice fields, and the electronic submission process. Errors in the source transaction can affect the resulting invoice data.

What Is the Cryptographic Stamp?

The cryptographic stamp is part of the technical controls associated with the ZATCA e-invoicing process. It helps establish the integrity and authenticity of the electronic invoice within the applicable technical framework.

Because the cryptographic process is connected to the invoice generation workflow, it should be handled by the invoicing system rather than added manually after an invoice has been created.

How Does ZATCA Phase 2 Affect ERP and POS Systems?

ZATCA Phase 2 directly affects the software that creates electronic invoices. ERP and POS systems must support the required invoice structure, integration process, and technical controls.

This makes system readiness a central part of Phase 2 preparation.

What Must an ERP Handle?

An ERP used for Phase 2 should be able to connect transaction processing with electronic invoice generation and ZATCA integration.

Depending on the business setup, the system may need to handle:

• Electronic invoice generation
• Required XML invoice data
• Applicable invoice fields
• QR code generation
• API-based integration
• Cryptographic controls
• ZATCA submission or reporting processes
• Invoice and transaction records
• Connections between sales and accounting data

The exact technical implementation depends on the company's software architecture and the applicable ZATCA requirements.

GO-Globe's ERP software solutions provide a relevant starting point for businesses evaluating how ERP functions can support connected finance and operational processes.

What If the Business Uses a POS System?

A POS system can be directly involved in e-invoicing when it generates invoices for customer transactions. If the POS creates the invoice, the Phase 2 integration requirements need to be addressed within that transaction flow.

Businesses should therefore assess the POS independently rather than assuming that an ERP integration automatically solves every invoicing requirement.

The assessment should identify where the invoice originates, which system owns the transaction data, and how that system will communicate with ZATCA.

How Should Businesses Prepare for ZATCA Phase 2?

Businesses should start with a technical review of their current invoicing environment. The purpose is to identify gaps between the existing system and the requirements that apply to the company's Phase 2 wave.

What Should the Readiness Review Cover?

A practical review should examine:

1. Invoice generation: Identify which system creates tax and simplified invoices.
2. Transaction data: Check where customer, sales, VAT, and product information originates.
3. XML capability: Confirm that the system can produce the required structured invoice data.
4. Integration: Determine how the ERP or POS will connect with ZATCA.
5. Technical controls: Review the requirements for authentication, cryptographic controls, and other applicable mechanisms.
6. Data consistency: Confirm that sales, invoicing, and accounting records use consistent information.
7. Testing: Establish how the integration will be tested before the applicable enforcement date.

A broader ERP readiness assessment for 2026 can also help businesses identify whether their existing ERP architecture needs changes before new requirements become operational.

Should Businesses Replace Their ERP?

Not necessarily. An existing ERP may be suitable if it can be configured or integrated to meet the applicable Phase 2 requirements.

The decision should follow a technical assessment rather than assuming that replacement is required. A business may need an integration layer, ERP modification, POS changes, or a new invoicing component depending on its existing architecture.

The important question is whether the current system can reliably perform the required functions and maintain the necessary connection with ZATCA.

What Happens If an ERP and ZATCA Are Not Properly Connected?

A disconnected system creates manual work between the transaction, invoice, and compliance processes. It can also make it harder for finance teams to maintain consistent invoice data across different systems.

Phase 2 therefore makes integration architecture part of the compliance process.

Why Does Data Flow Matter?

Consider a transaction that begins at a POS system, passes through an ERP, and produces an electronic invoice. Each system must preserve the information required for the next step.

If customer information, VAT values, invoice numbers, or transaction amounts are changed or entered manually between systems, the business creates additional opportunities for inconsistency.

A connected architecture keeps the data flow within defined system processes.

Can Automation Support Phase 2 Work?

Automation can reduce repetitive manual steps when it is built into the actual transaction and invoicing workflow. For example, an automated process can transfer transaction data into invoice generation rather than requiring finance staff to re-enter information.

For businesses reviewing automation in a Riyadh-based operation, GO-Globe also provides Riyadh AI automation services. Automation should remain connected to the actual compliance workflow rather than being added as an unrelated technology layer.

How Does AI Relate to ZATCA Phase 2 ERP Systems?

AI is not a substitute for ZATCA Phase 2 integration. The core requirement remains a compliant electronic invoicing system that can perform the required technical processes.

AI can be considered separately for ERP tasks such as data analysis, forecasting, or workflow automation where those functions have a genuine business purpose. GO-Globe discusses the role of AI and machine learning in ERP systems as a broader ERP technology topic.

For Phase 2 compliance, however, businesses should first establish the required invoice and integration capabilities. Additional automation should support the system rather than distract from those core requirements.

Integrating Your ERP or POS With ZATCA Phase 2

ZATCA Phase 2 integration requires technical work across the invoice lifecycle. GO-Globe's Saudi ERP services address ERP development and integration for businesses that need their operational systems connected with ZATCA requirements.

The integration work can involve API connectivity, XML invoice processing, cryptographic controls, and the connection between ERP or POS transaction data and electronic invoice generation.

Businesses can review GO-Globe's Saudi Arabia ERP system services when assessing an existing system or planning an ERP integration for Phase 2.

For companies operating in Riyadh, GO-Globe also provides a Riyadh ERP system focused on ERP requirements for the Saudi market.

Talk to Us About ZATCA Phase 2 Integration

If your business has entered a ZATCA Phase 2 wave, the next step is to assess the ERP, POS, or invoicing system against the applicable integration requirements. GO-Globe can help with the technical integration work required to connect business systems with ZATCA processes.

Talk to GO-Globe about ZATCA Phase 2 integration.

Frequently Asked Questions

What is ZATCA Phase 2?

ZATCA Phase 2 is the Integration Phase of Saudi Arabia's electronic invoicing program. It adds technical and business requirements and requires applicable electronic invoicing solutions to integrate with ZATCA systems.

Who must comply with ZATCA Phase 2?

Taxpayers selected for a ZATCA Phase 2 implementation wave must comply with the requirements applicable to their integration date. Businesses should check their ZATCA notification and applicable wave requirements.

Does ZATCA Phase 2 require ERP integration?

Phase 2 requires the applicable electronic invoicing solution to integrate with ZATCA. If the ERP generates or controls the relevant invoices, the ERP may need to be configured or integrated to support those requirements.

Does a POS system need ZATCA Phase 2 integration?

If the POS system is responsible for generating applicable electronic invoices, its role in the Phase 2 architecture must be assessed. The required approach depends on the POS configuration and how it connects with other business systems.

What is XML used for in ZATCA Phase 2?

XML provides a structured electronic representation of invoice data. A Phase 2 solution needs to generate invoice information in the format required by the applicable ZATCA specifications.

Can an existing ERP be upgraded for Phase 2?

Yes. An existing ERP can be assessed to determine whether configuration, development, or integration changes can bring it into line with the applicable Phase 2 requirements. ERP replacement is not automatically required.

What should a business do after receiving a Phase 2 notification?

The business should review the applicable integration date and requirements, assess its ERP or POS architecture, identify technical gaps, and plan development and testing before the required integration date.