A practical guide to ZATCA e-invoicing (FATOORA) requirements in Saudi Arabia and the role an ERP system plays in preparing for the integration phase.
E-invoicing in Saudi Arabia is no longer something a business can put off. Since the Zakat, Tax and Customs Authority (ZATCA) launched FATOORA, issuing, storing and exchanging invoices has become part of the everyday tax obligations of every VAT-registered business. In Phase 2 in particular, it is no longer enough for your software to print a well-formatted invoice with a QR code: your invoicing solution or ERP system must now connect directly to ZATCA's platform. This article explains, in practical terms, what has changed and what your system needs to offer so your business is ready when the integration notice arrives.
What is e-invoicing in Saudi Arabia?
E-invoicing means issuing invoices, credit notes and debit notes in a structured electronic format that can be processed automatically, instead of paper invoices or scanned files. A PDF sent by email, or an invoice typed in a word processor, is not an electronic invoice in the regulatory sense. The requirements have been applied in two phases:
- Generation phase: started on 4 December 2021. Businesses must issue and store invoices through a compliant electronic solution, handwritten invoices are no longer allowed, and simplified invoices must carry the mandatory fields and a QR code.
- Integration phase: rolled out in waves starting 1 January 2023, with ZATCA notifying the taxpayers in each wave in advance. In this phase the invoicing solution is connected to FATOORA so invoices can be exchanged and validated.
Because the criteria and dates of each wave are updated from time to time, the reliable reference is always the ZATCA website and the official notice your business receives, not what circulates in the market.
What does Phase 2 require technically?
In the integration phase your system treats an invoice as structured data rather than a printable document. In general terms this includes the following; refer to the technical specifications published by ZATCA for the exact details:
- Generating the invoice in XML according to the approved specifications, alongside a human-readable copy for the customer.
- Onboarding the solution unit or device with FATOORA and obtaining its own cryptographic certificate.
- Adding a cryptographic stamp and a unique identifier to each invoice, and chaining each invoice to the previous one so it cannot be altered or deleted without a trace.
- Sending standard (business-to-business) tax invoices to the platform for clearance before sharing them with the buyer, and reporting simplified (consumer) invoices within the period ZATCA sets.
- Receiving the platform's responses, whether acceptance, rejection or warnings, handling them and keeping a complete log.
None of this is usually added to an old accounting program with a single button, and this is where a system designed for integration differs from one that only prints invoices.
How does an ERP system help with FATOORA compliance?
When invoices come out of a single ERP system that combines sales, inventory and accounting, the data an invoice needs is already where it should be: the customer's VAT number and address, the items and their tax treatment (15%, exempt or zero-rated), the payment method and the supply date. If invoices are written in a separate program and then moved into the accounts by hand, every extra transfer step opens the door to mismatched figures or a rejected invoice.
An integrated system also links credit notes and returns to the original invoice automatically, and produces VAT reports from the same data that was sent to ZATCA, which reduces the chance of differences between your VAT return and what is recorded on the platform. Systems such as Odoo, SAP and Oracle offer packages or add-ons for Saudi requirements, but activation and coverage differ by version and edition, so you need to check your own installation specifically.
Practical steps before the integration notice arrives
Do not wait for the notice to start. Calm preparation well ahead of the deadline turns go-live day into an ordinary day. We suggest this order:
- List every invoice source: branches, points of sale, the online store and any other software that issues invoices in the company's name.
- Clean the master data: verify the VAT numbers and addresses of business customers, and standardise item definitions and tax categories.
- Review your current solution: does it support Phase 2? Does it need an upgrade or an add-on, or is moving to another system the better option?
- Test in the simulation environment ZATCA provides before going live, including difficult cases such as returns, discounts and invoices in a foreign currency.
- Train your team to read rejection messages and correct an invoice the proper way, through credit or debit notes.
At Haaltech we usually begin with a consulting session to review invoice sources and the data path from sales order to journal entry, before any talk of changing systems or buying new add-ons.
Common mistakes to avoid
- Relying on a vendor who promises compliance without showing you a successful test in ZATCA's environment.
- Connecting the main system while forgetting the points of sale or branches that issue simplified invoices.
- Entering customer data without validation, which leads to tax invoices being rejected when submitted.
- Treating e-invoicing as a purely technical project without involving your accountant or tax adviser.
If you run several systems, such as a CRM for sales and another for accounting, also read our article on integrating Salesforce with ERP, because the invoice journey often starts before it reaches the accounts.
Conclusion: e-invoicing readiness starts with data
Phase 2 of e-invoicing is not just a programming challenge; it tests how well organised your data is and how well your systems work together. A business that issues invoices from one system with clean data is better placed to comply, and to use that same data for reporting and decisions. If you want to review your current system's readiness or plan an ERP implementation that meets FATOORA requirements, contact us and we will work out the right starting point together.