checklist_rtl Saudi e-invoicing

How to choose ZATCA e-invoicing software in 2026: native, connector or ERP add-on

Every vendor says ZATCA-compliant. The useful question is how: whether the invoice, the stamp, the connection and the VAT return live in one system, or are handed between several. This guide sets out the three architectures on the market, the twelve questions that separate them, and what each answer costs you later.

Architectures 3
Checklist 12 questions
ZATCA pre-certifies products? No — each unit passes its own checks

ZATCA does not keep a list of approved products. Compliance is proven unit by unit: each solution unit is onboarded, issued a certificate, and must pass the authority's compliance checks with sample documents before it can send a real one. That means two products can both be called compliant on the day they are sold and behave very differently on the day an invoice is rejected, a certificate expires, or the rules change.

The three architectures

Native Connector / middleware ERP add-on
What it is The accounting system builds, stamps and sends the XML itself A separate service receives invoices from your system and talks to ZATCA A module bought for a large ERP, often configured by a partner
Where the invoice lives One place Two places, kept in sync One place, plus the module's logs
Set-up Minutes: an OTP and the company details Field mapping, testing both systems A project, often weeks
A rejection Shown on the invoice, fixed on the record Shown in the connector, fixed in the source system Depends on the partner's configuration
Cost shape One subscription Two subscriptions, sometimes per document Licence plus implementation
Best for Small and mid-sized businesses choosing their books Businesses keeping a system that cannot integrate Large groups already running that ERP
None of the three is non-compliant by nature. They differ in how many systems must agree for an invoice to be right.
Analytics dashboards on a large monitor
The test of a solution is not the demo invoice. It is the rejected one, the expired certificate and the busy month-end.

Twelve questions to ask every vendor

# Ask A good answer
1 Do you issue phase 1 and phase 2 documents from the same system? Yes — the switch on the wave date is a setting, not a migration
2 Who generates and holds the private key? Generated inside the solution unit, never displayed or exported
3 How is onboarding done? One OTP from FATOORA; compliance checks run automatically
4 Is a standard invoice held until it is cleared? Yes — the customer copy is ZATCA's stamped version
5 What happens if reporting fails at 11 pm? Automatic retries and a visible queue before the 24 hours run out
6 Can a timeout ever file an invoice twice? No — an already-filed response is treated as success
7 How are rejections shown? The rule, the field and the record to fix, in Arabic and English
8 Can I check a document before sending it? Yes, without consuming a position in the chain
9 How are credit and debit notes linked? To the original invoice, with a reason, on the same route
10 How is the certificate renewed? From settings with a new OTP; the chain continues unchanged
11 Is the VAT return built from the cleared documents? Yes — every box drills down to the invoices behind it
12 What do you charge per document? Nothing beyond the plan, with clear monthly allowances
Ask for a live demonstration of questions 5, 7 and 10. They are the ones a slide cannot answer.

Red flags

  • The product offers to show or export the stamping key. ZATCA's prohibited functions name this explicitly.
  • An issued invoice can still be edited or deleted, even by an administrator.
  • Phase 2 is “coming soon” or depends on a partner not yet chosen.
  • Rejections arrive as a code with no explanation, or only in English.
  • The VAT return is exported to a spreadsheet to be finished by hand.

Compliance is the entry ticket. What you are really choosing is how much of your month the rules will take up.

Questions people actually ask

Does ZATCA approve e-invoicing software?

Not in advance. Each solution unit proves compliance when it is onboarded and passes ZATCA's compliance checks, and keeps proving it with every document ZATCA accepts.

Is a connector a bad choice?

Not if you must keep a system that cannot integrate on its own. It is a second system to maintain, so it makes most sense when replacing the first is not an option.

Can I switch software after integrating?

Yes. The new solution unit is onboarded with its own certificate and starts its own chain. Keep the old system's documents for the retention period.

Where these facts come from

Checked against the following on 26 October 2026. Rules and dates change — if you are reading this long after that date, verify before you act on it.

WisoBooks is a bookkeeping and business-management tool, not an accounting, tax or legal advisor. Nothing on this page is tax advice, and tax rules change. Confirm your own obligations with the relevant authority or a qualified advisor.

auto_stories Keep reading

Next in this series

All guides

Test it against the checklist

Open a free trial and run all twelve questions yourself against ZATCA's simulation environment.

Free 30-day trial • No credit card • Cancel anytime