Updated: Sep 28, 2026
ZATCA e-invoicing requires Saudi businesses to replace manual invoice processes with electronic systems that support the required invoice format, QR code, XML data, VAT information, and Phase 2 integration with Fatoora.
Contents
ZATCA e-invoicing is Saudi Arabia's electronic invoicing system for businesses subject to the applicable requirements. It replaces paper or manually managed invoices with electronic invoices generated through compliant systems.
For finance teams, the key issue is not simply creating an invoice on a screen. The invoicing system must produce the required electronic data, handle invoice information correctly, and support the applicable ZATCA integration requirements.
Businesses therefore need to treat e-invoicing as part of their accounting and operational systems rather than as a separate spreadsheet task.
The e-invoicing process involves structured invoice data, electronic invoice generation, QR codes where applicable, and system capabilities that support ZATCA requirements.
The invoice must contain the required information in the applicable format. For businesses using an ERP, this means sales transactions, customer information, tax information, and accounting records need to connect correctly to the invoicing process.
A useful starting point is GO-Globe's guide to ZATCA e-invoicing in Saudi Arabia, which focuses specifically on the relationship between e-invoicing requirements and business systems.
Spreadsheets can store invoice information, but they do not by themselves provide the system integration and automated invoice generation required for an integrated e-invoicing process.
A finance team may still use spreadsheets for supporting calculations or internal analysis. The actual invoice workflow, however, needs a system that can generate the required electronic invoice data and maintain consistent information across sales, tax, and accounting records.
ZATCA introduced e-invoicing through two main implementation phases. Phase 1 established electronic invoice generation and storage requirements. Phase 2 adds integration and technical requirements that connect taxpayer systems with ZATCA.
Understanding the difference is essential because a business can generate electronic invoices without having the complete integration capabilities required for Phase 2.
Phase 1, known as the Generation Phase, became enforceable on December 4, 2021. It requires taxpayers within scope to generate and store tax invoices and notes through compliant electronic solutions.
The practical change is significant. Businesses need an electronic solution rather than relying on handwritten or manually generated tax invoices.
The system must support the creation and storage of the required electronic invoice records. This makes the invoicing application part of the company's finance process.
Phase 2, known as the Integration Phase, started on January 1, 2023 and is being implemented in waves. It introduces additional technical and business requirements and requires the taxpayer's electronic solution to integrate with ZATCA systems.
This means Phase 2 is not simply a different invoice design. It changes the relationship between the business's invoicing system and ZATCA.
Businesses selected for a Phase 2 wave receive notification from ZATCA at least six months before their integration date. The exact requirements therefore depend on the applicable ZATCA implementation instructions and the business's assigned wave.
Phase 2 makes system architecture an important part of compliance planning. A tool that can produce an invoice but cannot support the required integration does not address the complete requirement.
Finance teams should therefore evaluate the connection between their ERP, invoicing module, tax data, and ZATCA integration before selecting or modifying software.
A ZATCA e-invoice contains structured information required for the transaction and tax process. The exact requirements depend on the type of invoice and applicable ZATCA specifications.
The system producing the invoice must therefore manage invoice data consistently rather than treating the electronic format as a separate document created after the transaction.
XML is important because e-invoicing requires structured electronic data rather than only a visual document. The invoicing system must produce the required electronic representation of the transaction.
QR codes also form part of the e-invoicing requirements for applicable invoices. The QR code provides encoded invoice information that can be read electronically.
This is why a compliant invoice process needs more than a PDF generator. The underlying application must manage the data that produces the required electronic invoice and associated information.
Fatoora is ZATCA's platform associated with the e-invoicing process and integration requirements.
For Phase 2 businesses, the invoicing system must support the required connection with ZATCA. This makes integration between the business application and Fatoora a central technical consideration.
The system must therefore be designed around the applicable ZATCA technical requirements rather than treating government integration as an optional add-on.
ZATCA e-invoicing is closely connected to VAT because invoice data includes tax information that must remain consistent with the underlying transaction and accounting records.
An invoice system cannot be treated as an isolated document tool when VAT calculations, sales transactions, customer records, and financial entries depend on the same information.
If the sales transaction contains one value while the invoice or accounting record contains another, the business can create inconsistencies in its financial data.
An ERP can reduce this problem by connecting sales and finance information within the same business system. GO-Globe describes its ERP software as a way to connect business functions through a shared system.
For e-invoicing, the important relationship is straightforward: the transaction creates the invoice, the invoice contains the applicable tax information, and the accounting system records the financial effect.
The applicable invoice format depends on the transaction and the relevant ZATCA requirements. Businesses may work with tax invoices and simplified tax invoices, among other applicable documents.
The ERP or invoicing application should therefore support the invoice types required by the business instead of forcing finance teams to create different documents manually.
A business needs an electronic invoicing system or ERP that can generate the required invoice data and support the applicable ZATCA integration. The right system depends on the company's existing ERP, sales channels, accounting processes, and Phase 2 requirements.
Off-the-shelf invoicing software may handle basic invoice generation, but finance teams should verify whether the product supports the complete Phase 2 integration requirements before adopting it.
An ERP is useful when e-invoicing needs to connect with sales, finance, inventory, procurement, or other operational processes.
Instead of entering transaction information into one system and recreating it in another, the ERP can use the underlying transaction data to support invoice generation and accounting.
Businesses reviewing their existing setup can also use GO-Globe's ERP readiness guidance for 2026 to consider whether their current system is prepared for changing operational and technology requirements.
The deployment model is a separate decision from ZATCA compliance. Both cloud and on-premise ERP environments can be evaluated against the business's technical, operational, security, and integration requirements.
The key question is not simply where the ERP runs. The system must support the required invoicing workflow and the applicable ZATCA integration. Businesses comparing deployment options can review cloud ERP versus on-premise ERP as part of that assessment.
ERP preparation should begin with the existing invoice workflow. Finance teams need to identify where transaction data originates, how VAT is calculated, how invoices are generated, and how the system will communicate with ZATCA.
The review should cover both software capabilities and data quality.
Before implementation or integration, businesses should check whether their system can:
These checks help identify whether the business needs configuration, integration, an ERP upgrade, or a new system.
ZATCA compliance depends on the system behind the invoice. If sales data, tax data, customer records, and accounting entries remain disconnected, finance teams may continue to depend on manual reconciliation.
An integrated ERP creates a single operational process from transaction to invoice to financial record. That structure is especially relevant when the business must support electronic reporting and government system integration.
GO-Globe provides ERP development and integration services for Saudi businesses that need their business systems connected with e-invoicing requirements. Its Saudi ERP offering includes ZATCA-related e-invoicing capabilities and can connect finance and other business functions within an ERP environment.
For businesses operating in Riyadh, GO-Globe also provides a dedicated Riyadh ERP system service page covering ERP requirements for businesses in the Saudi market.
The appropriate approach depends on the existing ERP, business workflow, and integration requirements. The goal is to make e-invoicing part of the normal transaction and accounting process rather than a separate manual activity.
ZATCA introduced mandatory e-invoicing requirements through Phase 1 and Phase 2 for taxpayers within the applicable scope. Phase 1 became enforceable on December 4, 2021, while Phase 2 began on January 1, 2023 in waves.
Phase 1 focuses on generating and storing electronic tax invoices and notes through compliant electronic solutions. Phase 2 adds technical and business requirements for integration between the taxpayer's electronic solution and ZATCA systems.
The electronic invoicing process uses structured electronic data. Businesses implementing the applicable requirements need a system capable of producing the required XML representation and other specified invoice information.
QR codes form part of the requirements for applicable e-invoices. The invoicing system must generate the required information in the QR code according to the applicable ZATCA specifications.
Spreadsheets can support internal calculations or data preparation, but they do not provide the complete electronic invoicing and Phase 2 integration capabilities required from a compliant invoicing solution.
Businesses should check invoice generation, XML support, QR code generation, VAT data handling, invoice types, electronic record storage, and the ability to support applicable ZATCA Phase 2 integration requirements.
Yes, an existing ERP can be assessed for integration based on its architecture, invoice workflow, data structure, and applicable ZATCA requirements. The required approach depends on the existing system and business processes.