ZATCA e-invoicing software requirements: a buyer's checklist

ZATCA e-invoicing software in Saudi Arabia has to do more than print a tidy invoice. It must generate invoices electronically, block edits and deletions after issue, add the required QR code and, once your business is called into Phase 2, connect to ZATCA's FATOORA platform to clear or report every invoice. This checklist explains those requirements in plain terms and what to ask before you buy or build.

What does ZATCA require from e-invoicing software?

In short, the software must create structured electronic invoices, protect them from tampering and, in Phase 2, exchange them with ZATCA in real time or near real time. The rules arrived in two phases, and your software has to meet both.

Phase 1, often called the generation phase, took effect on 4 December 2021. It requires VAT-registered businesses to issue invoices from a compliant electronic solution rather than handwritten books or editable spreadsheets. Phase 2, the integration phase, started on 1 January 2023 and has been rolled out in waves, with businesses selected by VAT turnover and notified by ZATCA ahead of their date. Because the schedule and technical rules are updated from time to time, confirm your own wave and obligations with your tax adviser or directly with ZATCA.

This guide is not tax advice. It is a buyer's view of what the software side has to handle, so you can ask the right questions of a vendor or a development team.

Which Phase 1 rules still apply to your system?

All of them. Phase 2 adds integration on top of Phase 1, it does not replace it. If your current system fails the Phase 1 basics, fix that before you plan integration.

• Invoices are generated electronically and stored in a way you can retrieve later
• Issued invoices cannot be edited or deleted; corrections go through credit notes and debit notes
• Simplified tax invoices, usually for consumer sales, carry a QR code with the seller name, VAT number, timestamp, invoice total and VAT amount
• Standard tax invoices, usually for business customers, show the buyer's VAT number where the buyer is registered
• No anonymous access, no shared default passwords, and proper user sessions
• No resetting the invoice counter and no running two invoice sequences in parallel
• Accurate timestamps and logs that cannot be changed

Many older POS and accounting systems allowed a cashier to void and reissue invoices quietly. That habit has to go. A compliant system makes every correction visible as a separate document.

What changes when your business is called into Phase 2?

Phase 2 means your system talks to ZATCA directly. Invoices are produced in the XML format defined in ZATCA's technical specifications, signed, and sent through the FATOORA platform.

Two flows matter. Standard tax invoices for business customers go through clearance: your system sends the invoice to ZATCA, receives it back validated with ZATCA's cryptographic stamp, and only then shares it with the buyer. Simplified tax invoices for consumers go through reporting: you can hand the invoice to the customer straight away, but your system must report it to ZATCA within 24 hours.

Before any of this works, each invoicing unit, such as a POS terminal, a branch server or an ERP instance, has to be onboarded through the FATOORA portal. Onboarding gives the unit the credentials it uses to sign invoices. If you have many branches or tills, plan who will onboard each device, how certificates are renewed, and what happens when a terminal is replaced.

What should a buyer check before choosing a solution?

Ask the vendor or developer to show the flows working, not to describe them. A short live demo against ZATCA's sandbox environment tells you more than a brochure.

• Clearance for standard invoices and reporting for simplified invoices, including credit and debit notes
• A queue that holds simplified invoices when the connection drops and sends them automatically when it returns, with alerts if anything is close to the 24-hour limit
• Clear handling of rejected invoices: who is notified, what the error says, and how the corrected document is issued
• Onboarding and certificate management for every device and branch, with an admin screen rather than manual scripts
• Bilingual invoice layouts in Arabic and English, amounts in SAR and VAT at 15% shown correctly at line and total level
• Exports of the signed XML and the PDF for each invoice, so your accountant can retrieve any document quickly
• Role-based access and an audit log that records who did what and when
• A plan for updates when ZATCA changes its specifications, and who pays for that work

If your business sells through tills, the POS is usually where the hardest cases appear: split payments, returns at a different branch, and offline periods. Our page on POS software for Saudi Arabia covers those retail details.

Should you buy a ready-made tool or build the integration?

Buy when your invoicing is simple and your existing systems already support Phase 2. Build or extend when invoices come from a custom ERP, an industry system or several systems that a packaged tool cannot reach.

A packaged e-invoicing tool works well for a single company issuing straightforward invoices from one accounting system. The trade-off appears when invoices start life somewhere else: a rent-a-car contract, a hospital bill, a logistics job card or a school fee schedule. In those cases you either push data into the packaged tool through an interface, or you add the ZATCA integration to the system that already holds the invoice data.

Adding integration to your own system keeps one source of truth and avoids double entry, but it means you own the maintenance. A middle path is a small integration service that sits between your systems and FATOORA, receives invoices from each source and handles signing, clearance, reporting and retries in one place. We build this kind of custom software integration when a business has more than one invoicing source.

For example, a distribution company might issue B2B invoices from its ERP, consumer receipts from van sales handhelds, and service invoices from a separate maintenance system. Rather than buying three separate connectors, it could route all three into one integration service, so clearance rules, error handling and archives are managed in a single place and the finance team has one screen to watch.

What drives the cost of becoming Phase 2 ready?

The number of invoicing sources and the state of your current data drive cost far more than the ZATCA connection itself. A clean system with one invoice type is a small job; several legacy systems with inconsistent customer records are not.

• How many systems issue invoices, and whether you can change their code
• How many devices and branches must be onboarded
• Quality of master data: VAT numbers, addresses, product tax categories
• Offline requirements for POS and field sales
• Arabic layouts, credit note workflows and approvals
• Testing time in the sandbox and with your accountant before go-live

Ask for an estimate that lists these items separately. If a quote is a single number with no breakdown, you cannot tell what has been left out.

How is an e-invoicing project usually run?

The work follows a short, structured path: understand every invoice you issue, write the scope down, build in phases, test against the sandbox, and hand over with documentation.

We start with discovery workshops over video call, where finance, IT and operations walk through every invoice type, credit note case and branch. From that we write a scope that lists each flow and each system. A named lead engineer owns delivery, and the work runs in two-week sprints with a demo at the end of each one, so your finance team sees real invoices clearing in the sandbox early instead of at the end.

Releases are phased: usually one invoice source or one branch first, then the rest. Testing covers happy paths, rejections, offline queues and credit notes. At handover, the source code and the cloud accounts are registered to your company, along with the documentation your team needs to onboard new devices. You can read more about how we work with businesses across Saudi Arabia.

Frequently asked questions

Does every business in Saudi Arabia need Phase 2 integration now?

Phase 2 has been applied in waves based on VAT turnover, and ZATCA notifies businesses before their integration date. Check your status on the FATOORA portal or with your tax adviser rather than assuming.

Can we keep issuing invoices if the connection to ZATCA fails?

For simplified invoices, a well-built system issues the invoice and queues the report until the connection returns, within the 24-hour window. Standard invoices need clearance before they are shared, so plan a process for outages and confirm the exact rules with your adviser.

Does the invoice have to be in Arabic?

Tax invoices in Saudi Arabia are expected to be issued in Arabic, and another language such as English can appear alongside it. Confirm the exact field requirements with your tax adviser, and make sure the layout supports both languages.

Who maintains the integration when ZATCA updates its rules?

Agree this before you sign. Whether you buy or build, someone has to track specification changes, test them and release updates, and the contract should say who.

If you are planning Phase 2 integration or replacing a system that cannot meet it, talk to us about your invoice flows and we will help you map the work before any code is written.