ZATCA e-invoicing: connect your system, don't replace it

What Phase 2 requires, in plain words

Since Phase 2 began rolling out, being “e-invoicing compliant” in Saudi Arabia stopped meaning “my invoice has a QR code.” Your invoicing system must talk to ZATCA's Fatoora platform directly: standard B2B invoices go for clearance before they reach your customer, simplified B2C invoices are reported after issue, and every invoice carries the required XML structure, cryptographic stamp, and UUID. ZATCA brings businesses in by revenue waves, notifying each wave ahead of its deadline — so if you are VAT-registered and have not been called yet, you will be.

The choice nobody explains: integrate or replace

Most vendors answer the compliance question with “buy our system.” Sometimes that is right. But if your POS and accounting setup works — your staff know it, your data lives in it — replacing it for compliance alone is the expensive path. The alternative is a compliance layer:

• Your existing system keeps issuing invoices exactly as today
• A middleware layer reads each invoice, generates the compliant XML, applies the stamp and UUID
• Standard invoices are cleared with ZATCA in real time; simplified invoices are reported on schedule
• Every submission is archived with its response — the log you show an auditor

When integration wins — and when it doesn't

Integration wins when the current system is solid but not compliance-aware: a POS the branch staff have used for years, an ERP customized around your operation, or a custom system whose original developer moved on. It loses when the system is closed to any data access, or so old that connecting it costs more than moving off it. An audit answers this in one session: we look at where your invoice data lives, and tell you honestly which path is cheaper over two years — including when the answer is “buy an off-the-shelf compliant system, you don't need us.”

Common questions