If you sell in Egypt or Saudi Arabia, you have probably heard that invoices must now be "electronic". For many business owners this sounds like printing a PDF instead of using a paper book. It is more than that. In both countries, an electronic invoice is structured data in a format the tax authority defines, signed so it cannot be altered, and shared with the authority through its platform.
This article explains, in plain terms, what that means for the system your business issues invoices from. It is not tax advice: which rules apply to you, and from when, is something to confirm with your accountant.
Egypt: the ETA e-invoice and e-receipt
The Egyptian Tax Authority runs two related systems:
- The e-invoice system for invoices between businesses.
- The e-receipt system for sales to consumers, such as shops, restaurants and clinics.
Businesses have been brought into both in stages. In practice, a system that issues invoices in Egypt needs to:
- Hold the data the authority asks for: seller and buyer details, tax registration numbers, item codes, quantities, prices, discounts and taxes.
- Map your products and services to the item codes the authority accepts.
- Sign each document with the company's approved signature before sending it.
- Submit it through the authority's API and store the identifier and status it returns.
- Handle credit and debit notes, cancellations and rejections.
Saudi Arabia: ZATCA's Fatoora
The Zakat, Tax and Customs Authority (ZATCA) introduced e-invoicing, known as Fatoora, in two phases:
- Phase one, generation. Invoices must be generated and kept electronically by a compliant system, with a QR code on simplified (consumer) invoices.
- Phase two, integration. The system connects to ZATCA's platform. Businesses are called into this phase in waves, by size, and given notice.
In phase two, a system typically has to:
- Produce invoices in the required structured format, in Arabic, with the mandatory fields.
- Give each invoice a unique identifier and link it to the previous one, so the sequence cannot be altered unnoticed.
- Stamp each invoice cryptographically, using credentials the system obtains when it is registered with ZATCA.
- Send standard (business) invoices for clearance before they reach the buyer, and report simplified (consumer) invoices shortly after they are issued.
- Keep every invoice and the authority's response.
What this means for your system
Whether your invoices come from a CRM, an ERP, a booking system or an online shop, the same list applies:
- Clean master data. Customers with correct tax numbers and addresses, products with the right codes and tax rates. Most rejections start here.
- Signing and credentials, handled safely. Keys and certificates are stored securely, renewed on time, and never sit in a spreadsheet.
- A queue, not a button. Invoices are sent in the background, retried if the authority's platform is slow, and never sent twice.
- Rejections a person can fix. The reason in plain words, a way to correct it, a record of each attempt.
- Arabic that reads properly. Invoice PDFs and screens in correct right-to-left Arabic, with English alongside where your clients need it.
- Records you can find. Every invoice, credit note and response, searchable for audits.
Build it in, or bolt it on?
If you are planning a new internal system or CRM, design e-invoicing in from the start: it shapes how customers, products and invoices are stored. If you already have a system, e-invoicing can often be added as a separate service that reads invoices, sends them and writes back the result, with the repeated steps handed to automation.
Either way, ask any vendor to show you how their system handles a rejection. It tells you more than any feature list.
Your accountant decides what the rules require. Your system decides whether following them takes a minute or a morning.
Questions to ask before you start
- Which of our documents must be sent: invoices, receipts, credit notes, or all of them?
- Which system is the source of truth for customers and products today?
- Who on our side owns the signing credentials and their renewal?
- What should happen at the till or in the field if the connection is down?
- Who sees rejections, and how quickly must they be fixed?
Answering these with your accountant before the first meeting with a developer saves weeks.
Next step
Tell us where your invoices come from today, how many you issue, and whether you sell in Egypt, Saudi Arabia or both. A person from NOVA reads every brief and answers.
