E-Invoicing (ZATCA): Preparing Your Accounting System Step by Step

E-invoicing is no longer optional. In Saudi Arabia it is mandated by the Zakat, Tax and Customs Authority (ZATCA), and in Egypt by the Egyptian Tax Authority. An organisation that delays preparing does not merely face a technical problem, but a real regulatory risk. Here we explain what you need to know as a business owner — not as a developer — and then how we prepare your system in practice.

First: what is e-invoicing actually?

Simply: instead of a paper invoice or a PDF sent by hand, your accounting system creates a digital invoice in a defined format and sends it in real time to the government platform for verification and approval. The government's goal is clear: tax transparency and fighting evasion. Your goal: compliance without disrupting your daily work.

Saudi Arabia: ZATCA in two phases

Phase one (generation): your system issues compliant electronic invoices carrying a QR code and defined data, stored digitally. This phase is relatively simpler.

Phase two (integration): here is the real challenge. Your system connects directly to the ZATCA platform (Fatoora), sends every invoice for real-time verification, and receives the approved signature before handing it to the customer. This requires digital certificates, precise technical integration, and testing in ZATCA's sandbox before going live. Organisations are onboarded in waves by revenue size, so confirm which wave your organisation falls into and its date.

Egypt: the e-invoice system

The Egyptian system requires registering the organisation on the authority's portal, obtaining an electronic signature, and connecting your accounting system to send invoices in real time. The electronic receipt for points of sale is added later. Unified item coding (GS1 codes or the authority's codes) is a core requirement that is often neglected and causes invoices to be rejected.

Practical preparation steps — as we deliver them

1. Review the organisation's details: tax registration, address and activity — they must match exactly what is registered with the authority, otherwise invoices are rejected.
2. Clean the item catalogue: every item needs a correct code. This step alone exposes disorder accumulated over years.
3. Configure taxes in the system: VAT rates, exempt items, how discounts are handled — all of it appears on the invoice.
4. Digital certificates and integration: issuing the certificates and connecting the system to the authority's platform in the sandbox first.
5. Real testing: we issue test invoices and confirm they are accepted before any actual go-live.
6. Go-live and monitoring: we watch the first days of operation closely, because any rejected invoice means a blocked sale.

Why practical experience matters here

The difference between a vendor who read the documentation and a vendor who has actually delivered shows up at the first rejected invoice. Error messages from the authorities' platforms are sometimes vague, and the cause may be a single wrong field in the tax configuration or a missing item code. Our integration experience is practical on both systems — Odoo and ERPNext — not theoretical.

Common mistakes we see

• Leaving preparation to the last moment: integration and testing take time; rushing means errors at go-live.
• Ignoring data cleaning: items without correct codes = rejected invoices.
• Not testing in the sandbox: going straight live without testing is a gamble.
• Forgetting points of sale: in retail and restaurants, the electronic receipt is a separate requirement. Read: point of sale connected to accounting.

What if my current system does not support integration?

Many organisations discover, when e-invoicing is imposed, that their old accounting system — or their Excel files — cannot integrate at all. Here you have two paths: patching in a separate external solution that bridges between your system and the government platform, or moving to a system that supports integration natively. Patching looks cheaper but adds a fragile layer needing constant maintenance, and separates your invoices from your accounting. Moving to an integrated system solves invoicing, accounting and stock together. Which suits you? It depends on your size and your plans — and that is what the diagnostic session reveals. We will not sell you a new system if patching genuinely suffices.

The operational impact: what changes in your day

After correct preparation, e-invoicing becomes transparent to your team — they issue the invoice as usual, and the system handles sending and verification behind the scenes. But in the first days, expect cases needing attention: a customer with incomplete tax details, an item with a non-matching code, or a temporary outage in the government platform's connection. A good system handles these gracefully — it holds the invoice and retries rather than stopping the sale. Part of our work is tuning that handling before you meet it.

Common questions

Does e-invoicing slow the cashier down? With a well-configured integration, no. Verification happens in seconds behind the scenes. Slowness only occurs with poor setup or a weak connection.

Do I need special hardware? Usually not — this is software configuration and certificates, not new devices in most cases.

What about old invoices? E-invoicing applies from activation onwards; there is no need to reissue what came before.

In summary

E-invoicing is mandatory, and correct preparation protects you from a regulatory risk and from your sales stalling. The key: start early, clean your data, and test before going live. If your current system does not support integration, that is usually a signal that the time for a system that does has arrived — we help you diagnose without selling you what you do not need.