An e-invoice is no longer just a PDF emailed to a customer. In Saudi Arabia, the Zakat, Tax and Customs Authority (ZATCA) requires VAT-registered businesses to issue invoices from a compliant system and then connect that system to its Fatoora platform. In Egypt, the Egyptian Tax Authority (ETA) requires registered companies to submit their invoices and receipts electronically to its system. If your online store, ERP or point of sale does not integrate with these systems, you are left with tedious manual entry, errors and potential penalties. This guide explains e-invoicing integration in both countries, what your system needs technically, and how to implement the integration properly.
The short answer: e-invoicing integration means your system (store, ERP or POS) automatically sends every invoice to the tax authority's platform in the required format, with an approved digital stamp or signature, then receives and stores the response. In Saudi Arabia this happens with the Fatoora platform: clearance for standard B2B tax invoices and reporting for simplified B2C invoices. In Egypt it happens with the ETA e-invoice and e-receipt system through an API, an approved e-signature and item codes. The safest route is a ready-made compliant system if it fits your business, or a direct integration that is properly built and tested for your custom system.
E-Invoicing in Saudi Arabia: ZATCA and Fatoora
ZATCA rolled out e-invoicing in two phases:
- Phase 1 (generation): started in December 2021. Invoices must be issued and stored from a compliant electronic system, with a QR code on simplified invoices, and handwritten or edited invoices are no longer allowed.
- Phase 2 (integration): started in January 2023 and is being applied in waves based on revenue, with ZATCA notifying targeted businesses in advance. In this phase your system connects directly to Fatoora.
What Your System Needs for Phase 2
- The approved XML format for invoices, following ZATCA's technical specifications.
- Onboarding your e-invoicing solution on the Fatoora portal and obtaining a cryptographic stamp identifier (CSID) for each device or system that issues invoices.
- A cryptographic stamp on every invoice, a UUID, an invoice counter, and a hash that chains each invoice to the previous one to guarantee sequence and prevent tampering.
- Clearance for standard B2B tax invoices: the invoice is sent to the platform and cleared before it is shared with the buyer.
- Reporting for simplified B2C invoices within 24 hours of issue.
- Handling rejections and warnings returned by the platform, and storing every response.
E-Invoicing in Egypt: The ETA System
- E-invoice: for business-to-business transactions, rolled out in phases to registered companies since 2020.
- E-receipt: for sales to consumers in shops and at points of sale, applied in phases that the ETA sets for each category of business.
What Your System Needs to Integrate in Egypt
- Registration on the system and creating ERP integration credentials on the ETA portal.
- An approved e-signature from a licensed provider, used to sign every document before it is submitted.
- Item coding: a code for every product or service under approved coding systems such as GS1 or EGS codes registered on the system.
- Submitting documents through the API in the required format, then tracking the status of each one: accepted or rejected, and why.
- For e-receipts: registering points of sale, printing a QR code on receipts, and submitting receipts to the system.
Quick Comparison: Saudi Arabia vs Egypt
| Item | Saudi Arabia | Egypt |
|---|---|---|
| Authority | Zakat, Tax and Customs Authority (ZATCA) | Egyptian Tax Authority (ETA) |
| Platform | Fatoora | E-invoice and e-receipt system |
| B2B | Clearance before the invoice is sent to the buyer | Signed invoice submitted and validated on the system |
| B2C | Simplified invoice with a QR code, reported afterwards | E-receipt with a QR code |
| Security | Cryptographic stamp with a certificate from the platform | E-signature from an approved provider |
Requirements and regulations are updated from time to time, so always check each authority's official portal or your accountant before implementation.
Is your store or system not yet connected to e-invoicing? We review your current setup, choose the best way to integrate with Fatoora in Saudi Arabia or the ETA system in Egypt, then build and test it. Message us on WhatsApp.
Integration Options: Which One Fits You?
| Option | Best for | Watch out for |
|---|---|---|
| A compliant ready-made accounting system or ERP | Businesses with standard processes | That it supports the phase you are actually required to meet, and connects to your store and POS |
| An integration app for your store platform | Stores on ready-made platforms | Coverage of every invoice type and returns, and who is responsible when invoices are rejected |
| Direct integration from your custom system | Custom systems, custom-built stores and proprietary POS | A precise understanding of the technical specifications and thorough testing in the sandbox |
| An integration provider in the middle | Businesses that want integration without building everything | Service fees, where your data is stored, and the ability to switch later |
How to Implement the Integration Properly
- List every invoice source: the online store, branches and POS, the sales system, and any manual invoices.
- Clean your master data: VAT numbers and addresses for business customers, and item codes and tax rates for every product.
- Choose the integration option that fits, from the table above.
- Build in the sandbox: create invoices, credit notes and debit notes and test them in the developer environment before production.
- Handle errors: automatic retries when the connection drops, and an alert to the responsible person when an invoice is rejected, with the reason.
- Onboard and activate: register devices or the system on the platform and activate certificates or signatures.
- Monitor after go-live: a daily report of invoices sent, accepted and rejected, and regular reconciliation with accounting.
Common E-Invoicing Integration Mistakes
- Connecting the store but forgetting branches, POS or invoices issued from another system.
- Editing an invoice after issuing it instead of issuing a credit or debit note.
- Incomplete customer data, such as a missing VAT number or address, so invoices get rejected.
- No alert when an invoice is rejected, so uncleared invoices pile up unnoticed.
- Treating a PDF or image as a compliant e-invoice.
- Storing stamping or signing keys insecurely.
If you are looking for one system that combines accounting, inventory and sales with e-invoicing, see inventory management software, and for connecting systems in general, read our guide to API integration for businesses.
Frequently Asked Questions
Is a PDF invoice from my store enough?
No. What is required is a structured e-invoice in the approved format with the required stamp or signature, and in the integration phases it must reach the tax authority's platform itself.
When do I need to integrate in Saudi Arabia?
When your business is targeted in one of the Phase 2 waves, and ZATCA notifies targeted businesses in advance. Follow ZATCA's notifications and the Fatoora portal, and don't leave it to the last minute, because testing needs time.
Can a custom-built store be integrated?
Yes, by building an integration module inside the system that generates the invoice in the required format, stamps or signs it, submits it and stores the response, and testing it in the sandbox before go-live.
I sell in both Saudi Arabia and Egypt. Do I need two integrations?
Yes, each country has its own system and specifications, but you can build one invoicing layer in your system that submits to each platform in its own format.
Integrate Your System with DevLabico
At DevLabico we build e-invoicing integration modules for online stores, custom systems and POS for businesses in Saudi Arabia and Egypt, with error handling, alerts and reporting. Message us on WhatsApp or book a free consultation to review your system.
