On this page
What is e-invoicing software?
It is software that issues the invoice in a structured electronic format and sends it to the tax authority in your country, then tracks its status until it is accepted or rejected. It differs from a PDF sent by email, because the authority receives a data document its systems read and check.
People search for it as “e-invoice software”, “e-invoicing system”, “tax invoice software” or “e-invoice integration”. They mean one thing: software that turns your ordinary invoice into a document the tax authority accepts, without retyping it. In Anzma this is a set of separate modules per country that run on top of sales and invoicing software and connect to accounting and stock.
This line does not replace a full ERP; it is the tax layer on top of one. If you are looking for a system that runs the whole company, see a complete ERP system or the guide to choosing an ERP.
How does e-invoicing work in Egypt?
Egypt’s Tax Authority runs two systems: the e-invoice system for sales to companies and business customers, and the e-receipt system for counter sales to consumers. Each has different documents, signing and statuses.
For invoices, you issue the invoice from sales, Anzma validates its data, it is signed with your company’s certificate, sent and tracked until it is valid. For receipts, the receipt is built from the POS sale in a chain per device, signed, sent and printed with a QR code. Details of the first are in ETA e-invoice integration, the second in Egypt e-receipt software, and the general entry point is e-invoicing software in Egypt.
One important point in Anzma: when the e-receipt module is on, a POS sale goes as a receipt and not as an invoice, so it is never sent twice.
How does e-invoicing work in Saudi Arabia?
Saudi Arabia has one platform, Fatoora, run by ZATCA. Phase 1 means issuing the invoice electronically with a QR code, and phase 2 means connecting your invoicing system to the platform to send invoices.
In phase 2 each invoicing unit (a POS device or a branch) is registered and gets a CSID certificate, every invoice is signed and chained to the previous one, then sent: standard tax invoices for clearance and simplified invoices for reporting. The detail is in ZATCA e-invoicing software. Unlike Egypt, there is no USB token step: Anzma generates each unit’s signing key and stores it encrypted.
In practice each POS device or branch has its own numbering chain and hash, so a fault on one unit does not stop another from sending. Anzma also reminds you to renew the certificate before it expires, so invoicing does not stop by surprise, and tracks each invoice until it is accepted.
What is the difference between the Egyptian and Saudi systems?
The core difference is that each country has its own authority, documents and signing, so one setup cannot serve both. Below is a quick comparison of what Anzma does in each system; it is not a ruling on what is mandatory for you, which the authority decides.
| Aspect | ETA invoice | ETA receipt | ZATCA |
|---|---|---|---|
| Authority | Egyptian Tax Authority | Egyptian Tax Authority | Zakat, Tax and Customs Authority |
| Document | Invoice, credit and debit note | Receipt and return receipt | Standard and simplified invoice, notes |
| Buyer | A company or business customer | A consumer at the counter | Business and consumer |
| Signing | Company certificate (USB token and agent) | Company certificate (agent) | A CSID certificate per unit |
| Flow | Send, then valid or invalid | Chain per device, then accepted | Clearance or reporting |
| Anzma module | eta_invoicing | eta_receipts | zatca |
Which modules are in the e-invoicing line?
Three modules, each serving one system. All of them depend on sales, and read the POS where needed.
ETA e-invoice integration: sending invoices and credit notes to the Egyptian system, signing, status tracking, cancellation within the window, and receiving supplier documents. The e-receipt is built on top of it.
Egypt e-receipt software: a receipt from every POS sale in a chain per device, a printed QR code and return receipts. It needs the POS and the Egyptian e-invoice module.
ZATCA e-invoicing software: invoicing unit registration and CSID certificates, clearance of standard invoices and reporting of simplified ones, and a TLV QR code.
The split is by system rather than by feature, because each system has its own documents, signing and statuses, and merging them into one screen would hide differences you need to see. Inside each module you find the screens and permissions it needs: the sent-documents list, integration settings, device or unit details, and received documents in Egypt.
How do you start the connection in Anzma?
The steps are the same in spirit in both countries and differ in detail. It is best to always begin on the test environment.
- 1
Prepare business data
Tax number, company and branch addresses, each business customer’s details, item codes and their tax classification.
- 2
Register with the authority
In Egypt: register the business, your system and branches on the portal. In Saudi Arabia: register the business and generate an OTP for each invoicing unit.
- 3
Prepare signing
In Egypt, the company certificate (usually on a USB token) with a signing agent. In Saudi Arabia, Anzma generates each unit’s key and obtains its certificate.
- 4
Configure the connection
Enter the settings and credentials, choose the test environment and run the connection test.
- 5
Test with sample invoices
Issue invoices of each type, review the errors shown per field and fix the missing data.
- 6
Go to production
Switch the environment, enable automatic sending once you trust the data, and watch statuses daily.
What do you need to sign e-invoices in Egypt?
The Egyptian system requires an electronic signature made with your company’s certificate, and that certificate normally lives on a USB token that cannot be plugged into a cloud server. So Anzma works with a small signing agent you run on a PC in your premises that holds the token: it asks Anzma over the internet for waiting documents, signs them and returns only the signature, with no inbound port opened at your end and without Anzma ever receiving your private key. If your certificate is a file, it can be uploaded instead of using the agent.
This means you need a PC that stays on during business hours. If it is off, documents wait for signing and are not lost. We supply neither the token nor the certificate; they come from the issuer. In Saudi Arabia it is different: Anzma generates each invoicing unit’s key and stores it encrypted.
What happens to one invoice from issue to acceptance?
To see the value of the connection, follow one invoice. A salesperson issues it for a customer, and the system deducts the items from stock and posts revenue and receivable to the books with a double entry. This is where the tax module starts: it turns the invoice into the document your country’s authority wants, checks that its data is complete, then signs it and queues it for sending.
The invoice is then sent in order and tracking begins. In Egypt Anzma polls the document’s result until it is valid or invalid; in Saudi Arabia a standard invoice comes back cleared and a simplified one is reported. Either way the response is stored on the invoice itself, so the accountant sees in the invoice list what was accepted, rejected or waiting, without entering a government portal.
If a correction is needed, a sent invoice is not edited; a credit note linked to it is issued and sent in turn. Books, stock and the tax authority then keep one version of the event, which is what separates e-invoicing built into an integrated system from a standalone sending tool.
What are the most common reasons e-invoices are rejected?
A rejection is rarely a technical fault. Most are missing data that shows up when you send, and once fixed it disappears from everything that follows. Similar causes recur in both systems: a business customer with no tax number or an incomplete address, an item without a code or tax classification, a branch whose address is not written as registered, and a credit note for an invoice not yet accepted.
Anzma checks these before sending and shows the error by field, so days are not lost corresponding with the authority over an empty field. It also stores the rejection reasons returned by the authority and alerts the responsible users. The practical advice is to clean customer and item data before moving to production, and to have the accountant review the failed-documents list at the end of each business day.
One program or manual entry on the portal?
In theory you can key invoices into the authority’s portal by hand, but that means double entry, errors and delay as invoice volume grows. A comparison of the options:
| Aspect | Manual entry on the portal | A separate accounting tool | Anzma |
|---|---|---|---|
| Entering the invoice | Once on the portal, once in your books | Once, with a separate link | Once, from sales |
| Check before sending | No | Varies | Yes, by field |
| Status tracking | Manual | Varies | Automatic with alerts |
| Stock and accounting | Separate | Partial | Connected |
| Receipt from the POS | Not available | Varies | A dedicated module |
How does e-invoicing connect to accounting and purchases?
E-invoicing is not an island. Every document sent has a source in accounting: a double entry for revenue, VAT and receivable, so what the authority sees matches your trial balance. If an invoice is corrected with a credit note, the books and stock adjust together.
In Egypt the line also reaches purchases: the invoices your suppliers issued in your company’s name are pulled in, and you match them to a purchase bill or create one from them instead of keying it, which saves the accountant time and reduces transcription errors. The detail is on the ETA e-invoice integration page.
Who in your company runs and monitors the connection?
The connection works when responsibilities are clear. The owner or manager handles registration with the authority and the credentials, the system admin sets up the configuration, environment and signing, the accountant follows document statuses and handles rejections, and the cashier supervisor reviews failed receipts at the end of the day.
In Anzma each module has separate permissions that match these roles: view documents, export, send and resend, cancel in Egypt, manage onboarding and certificates in Saudi Arabia, and edit settings. You give each employee only what the role needs, and keep cancellation and settings with someone you trust.
What about the UAE and the rest of the Gulf?
Today Anzma supports the Egyptian and Saudi systems in this line. Companies in the UAE, Kuwait, Qatar and the other Gulf countries run on their country pack: currency, VAT and tax number, without a government e-invoicing module, because the system does not impose a connection that does not exist. When a country announces a new system we assess supporting it and say so; we do not promise what has not been built.
If your group has companies in different countries, give each company its own settings. See a complete ERP system for how multiple companies are managed, and pricing for branch and plan limits.
Which businesses need e-invoicing?
That depends on each country’s tax authority, not on the type of business alone, so check with the authority for your status. In Anzma the connection is available to many businesses because it is built on sales. Shops selling at a counter, such as retail store management software and supermarket management software, benefit from the receipt in Egypt and the simplified invoice in Saudi Arabia.
Companies selling to business customers, such as wholesale and distribution software and supply company software, benefit from the company invoice. Restaurants, pharmacies and clinics have a POS connected to the systems; see restaurant management software and pharmacy management software.
What do four different sales look like in the two systems?
The clearest way to see the differences is to follow one sale in each case. The numbers are illustrative only, and the tax rates are the two country rates configured in Anzma: 14% in Egypt and 15% in Saudi Arabia.
Example: a company in Cairo sells goods worth 1,000 pounds to another company. The invoice is issued from Sales, Anzma adds the tax and checks the buyer’s tax number and the item code, then signs it and sends it as an e-invoice. Another example: a shop in Alexandria sells to a walk-in customer for 200 pounds at the till, so an e-receipt is built in the till’s receipt chain and a QR code is printed on it.
A Saudi example: a company in Riyadh sells to another company for 1,000 riyals. This is a standard tax invoice, so it goes to the Fatoora platform for clearance before you hand it to your customer. At the till, a shop in Jeddah sells to a consumer for 200 riyals: a simplified invoice is handed over immediately and then reported to the authority. In both Saudi examples the document carries a TLV QR code.
| Case | Country | Document | Module | What happens after the sale |
|---|---|---|---|---|
| Sale to a company, invoice | Egypt | E-invoice | eta_invoicing | Sign, submit, then valid or invalid status |
| Till sale to a consumer | Egypt | E-receipt | eta_receipts | Device chain, sign and submit, then accepted |
| Sale to a company, invoice | Saudi Arabia | Standard tax invoice | zatca | Clearance by the authority before delivery |
| Till sale to a consumer | Saudi Arabia | Simplified invoice | zatca | Immediate delivery, then reporting |
What does Anzma do, and what stays with you and the authority?
A connection fails when each side assumes the other will handle a step. So we put the responsibilities in one table, and anything that belongs to the tax authority is decided by that authority alone.
| Task | Anzma | You | Tax authority |
|---|---|---|---|
| Building the document from the invoice and checking its fields | Yes | Prepare customer and item data | No |
| Signing | Signing agent in Egypt, unit key in Saudi Arabia | Run the agent and keep the token safe | Defines the signing method |
| Registration and certificates | Guided screens and generated requests | Enter credentials or the OTP | Issues credentials and accepts registration |
| Submission and retries | Yes, with a queue and growing intervals | Review rejected items daily | Receives and answers with a status |
| Deciding who is obliged and when | No | Check the authority and your accountant | Yes, alone |
| Official approval of providers and its conditions | We do not claim it | Verify with the authority | Yes |
How do you test before production in Egypt and Saudi Arabia?
Each system has test environments before production, and the idea is the same: try realistic documents without touching your tax records. In Egypt the module starts on the pre-production environment and moves to production only when you change it in the settings. In Saudi Arabia there are three environments: developer portal, simulation and production.
Do not settle for one successful invoice. Issue a sample that represents your business: a business customer and a consumer, a taxable item and an exempt one, a credit note, a discounted sale and a branch other than the main one. Every pattern you leave untested may show up for the first time in production as a rejection.
- In Egypt: test invoices for each type of buyer, test receipts from every till, and a review of the field-level errors.
- In Saudi Arabia: a test billing unit, then standard and simplified invoices and notes, then a review of the saved warnings.
- Before switching: the accountant reviews tax rates and exemption reasons, and the system admin confirms signing and the environment.
- After switching: someone reviews rejected items daily, especially in the first week.
What is the checklist before choosing e-invoicing software?
Choosing the software is a decision you live with for years, and most regret comes from something nobody asked about. Ask the vendor these questions and ask for a live demonstration, not a description.
- Does it really support your country and its system, or does it support another country and promise the rest?
- Is the invoice issued from the same program you sell from, or do you re-enter it?
- Does it validate fields before sending and show the error per field?
- What is the signing method and what does it need from you: an always-on PC or a certificate file?
- Is there a test mode before production, and do you decide when to switch?
- What happens to a document when the connection drops or sending fails?
- How is an accepted document corrected, and is editing after submission blocked?
- Does it connect to stock and accounts, or does it stop at sending?
- Does it claim official approval? Verify with the authority yourself before you trust any claim.
How do you run companies in Egypt and Saudi Arabia together?
In Anzma the rule is one company per country. The Egyptian company carries its tax number, a default 14% tax, its currency and the invoice and receipt modules, and the Saudi company carries its tax number, a default 15% tax and the ZATCA module. A company’s invoice is never sent to another country’s system.
This separation helps at review time. Each authority sees only the company registered with it, and each country’s accountant sees that country’s books. If you need a group view, read the financial reports of each company separately and combine them in the way your group prefers.
A common mistake is for an Egyptian business to open a Saudi branch and assume the e-invoicing settings move with it. In reality Saudi Arabia needs a new registration with the authority, billing units and its own certificates, so give it separate time in your plan.
What is a suggested plan for the first month?
This is not a period any authority commits to. It is the order we find practical for someone starting from zero, and it changes with the size of your business and how fast the certificate arrives.
- Week one: list items, customers and branches, correct tax numbers and addresses, and register the business with the authority.
- Week two: obtain the signing certificate or the OTP, and set up Anzma on the test environment.
- Week three: issue sample documents of every type, review errors, and train the accountant and the cashier supervisor.
- Week four: go to production with one unit or branch, then widen gradually while watching statuses daily.
What mistakes do companies commonly make when switching on e-invoicing?
The same mistakes recur at most businesses, and most are avoided by an early decision rather than complex technology.
- Leaving the signing certificate to the last minute in Egypt, when it depends on the issuing body.
- Testing with one easy invoice and then going live.
- Leaving items without a code or tax classification, and free-text lines.
- Mixing up the invoice and the receipt in Egypt, so a sale is sent twice or not at all.
- Editing an invoice that was already sent instead of issuing a credit note.
- Leaving the signing-agent PC switched off on working days.
- Nobody owning the daily review of rejected documents.
- Relying on a claim of approval without checking the official authority.
How do you correct an invoice that was sent by mistake?
An invoice is not edited after it is sent or accepted, because the tax authority already holds a copy. A correction is a new document that points to the original: a credit note reduces the value and a debit note increases it, and each is sent as its own document.
Example: you issued an invoice for ten units and the customer received only eight. You issue a credit note for two units, so revenue and tax go down, the two units return to stock, and the document reaches the authority linked to the original invoice. At the Egyptian till, the return receipt does the same job.
Only in Egypt can a document sent by mistake be cancelled within the window the system allows, and cancellation is not meant for a wrong price or quantity. Use a note for corrections and keep cancellation for a document that should never have been issued.
What happens to e-invoices when the internet drops?
Selling does not stop in either case, but what happens to the tax document differs. For sales invoices the document is built and enters the sending queue, the background job retries at growing intervals until it arrives, and you are notified if it fails. It is not sent twice because the system blocks a duplicate document.
On the Egyptian till, selling continues locally and syncs when the connection returns, and the e-receipts are created then, in chain order. A receipt printed during the outage carries no official QR code and no system number, because neither exists before submission. The rest of the back office needs the internet.
The practical advice is to know in advance what you tell a customer who asks for an official receipt during an outage, and to have the cashier supervisor confirm at the end of the day that every synced sale arrived and was accepted.
Which module fits your business: Egypt and Saudi Arabia?
The table summarises which module usually handles each type of sale in each country. It describes what Anzma does, not what an authority obliges you to do, which is for ETA or ZATCA to decide.
| Type of sale | In Egypt | In Saudi Arabia |
|---|---|---|
| Wholesale and supply to companies | E-invoice (eta_invoicing) | Standard tax invoice for clearance (zatca) |
| Shop or supermarket with a till | E-receipt (eta_receipts) | Simplified invoice for reporting (zatca) |
| Restaurant or café | Receipt when the order is paid | Simplified invoice when paid |
| Pharmacy or clinic with a till | Receipt from the till | Simplified invoice |
| Business selling to individuals and companies | Receipt and invoice together | Simplified and standard together |
Is free e-invoicing software enough?
Many people search for free e-invoicing software or a download, which is understandable. But the more important question is not the price, it is what falls on you after issuing. The official portal usually allows manual issuing, which suits someone issuing very few invoices. As invoices grow, double entry becomes a burden, with errors and late submission.
Software downloaded from unverified sources carries another risk: nobody guarantees it is updated when the authority changes its specification, and there is nowhere to ask for support when a document is rejected. An e-invoice is tied to your business certificate and tax number, so do not hand them to a tool whose source you do not know.
So our advice is to compare the total cost: the accountant’s time on repeated entry, transfer errors and late submission, against a subscription to a system that issues from the invoice itself. We do not promise a free product; our modules are part of paid plans, and you can book a free meeting so we can work out with you what suits your business.
What do the terms that keep appearing in e-invoicing mean?
There are many abbreviations in this subject, and understanding them makes it easier to talk to your accountant and to support. Do not worry if they blur at first; Anzma’s screens show the required step in plain language, and this list is a quick reference when someone mentions a name you do not know during registration, testing or a review of rejections with the authority.
| Term | Meaning | Where it appears |
|---|---|---|
| ETA | Egyptian Tax Authority | Egypt |
| ZATCA | Zakat, Tax and Customs Authority | Saudi Arabia |
| CSID | A digital certificate for each billing unit | Saudi Arabia |
| EGS | Billing unit: a till or a branch | Saudi Arabia |
| TLV | The encoding format of QR code data | Saudi Arabia |
| Clearance and reporting | The authority checks a standard invoice before delivery, a simplified one is reported after | Saudi Arabia |
| Signing agent | A small program that signs with the USB token at your site | Egypt |
What does it cost and how do we start?
None of the three modules is tied to a plan feature; the general plan limits on users, branches and monthly invoices apply, and the details are on pricing. The actual cost of the connection depends on the number of invoicing units or POS devices and the setup required.
The best first step is a short meeting where we settle your country, your customer type (business or consumer) and the number of devices and branches. Book an online meeting for free and we will show the screens on your own business data and start on the test environment. Remember that your obligation date and its details come from the authority, so check there.
Do not wait until the deadline nears to begin. Preparing item and customer data, getting the signing certificate and registering units are the longest parts, and all of them can be done at leisure on the test environment without touching live business. Starting early also lets your team learn to read and fix errors before sending becomes part of the day.
Frequently asked questions
What is the difference between an e-invoice and an e-receipt in Egypt?
An invoice is for sales to companies and business customers, a receipt for counter sales to consumers. Each has its own system and correction document: a credit note for the invoice and a return receipt for the receipt. In Anzma a counter sale is never sent twice; it goes as a receipt when the module is on.
What is phase 2 of e-invoicing in Saudi Arabia?
It is the integration phase: your invoicing system connects to the Fatoora platform to send invoices, with a CSID certificate per invoicing unit, signing and an extended QR code. It follows the generation phase, which only required issuing the invoice electronically. The authority sets when it applies to each business.
Am I required to use e-invoicing?
The Egyptian Tax Authority and ZATCA decide who is obliged and from when, and publish it on their sites. We quote no dates or thresholds here so they cannot go stale. Check eta.gov.eg or zatca.gov.sa, or your accountant, then book a meeting and we will set up the connection.
Does the system support both countries for the same group?
Yes, with one company per country. The company’s country decides the system: Egypt with the e-invoice and e-receipt modules, Saudi Arabia with the ZATCA module. Each company has its own tax number, VAT, currency and settings, so one country’s invoices never mix with the other’s.
What is needed for the connection: certificate, signing, device?
In Egypt, a signing certificate in the company’s name, usually on a USB token, with a signing agent on a PC in your premises, or a certificate file instead. In Saudi Arabia, Anzma generates each invoicing unit’s key and obtains its certificate using an OTP from the authority’s portal. The certificate itself comes from its issuer.
Can I try it on a test environment first?
Yes, each system has a test environment. The Egyptian module starts on pre-production by default, and the Saudi module supports the developer portal and simulation before production. We recommend starting with sample invoices to find missing item and customer data before the first real send.
What happens if an invoice is rejected?
Anzma stores the errors returned by the authority and shows them by field, and alerts the responsible users. You fix the data and resend from the same screen. An accepted invoice is never edited but corrected with a credit note, and in Egypt a document sent by mistake can be cancelled within the window the system allows.
Is there free e-invoicing software?
We do not offer free e-invoicing software. Our modules are part of a platform sold in plans, whose details are on the pricing page. You can book a free online meeting where we show the screens on your own business data and settle the right plan. The authorities also have official portals that allow manual issuing, which you can check.
Is Anzma approved by the authorities?
To be precise, Anzma’s modules integrate with the Egyptian Tax Authority’s and ZATCA’s systems following their published specifications. We do not claim approval or listing by any authority. Check the authority for any conditions on solution providers, and ask us about test-environment status in the meeting.
Does e-invoicing work with the POS, stock and accounting?
Yes, it runs on top of sales and the POS. The invoice deducts stock and posts to accounting with a double entry, then is sent, so your internal numbers match what reached the authority. In Egypt receipts are built from POS sales, and in Saudi Arabia simplified POS invoices are reported.
How do I choose the right e-invoicing software?
Ask: does it support your country and its system? Does it validate data before sending? How is signing done and what does it need from you? Does it track status and handle rejections? Is it connected to your stock and accounting? Ask for a test environment before committing, and check the official authority for any conditions on providers.
Does the connection work with multiple branches and tills?
Yes. In Egypt the receipt chain is per till and each branch has its registered address; in Saudi Arabia a billing unit is registered per till or branch with its own chain and certificate. A fault on one device does not stop the others from sending, and you review each document’s status from the documents screen.
Official sources
Rate this page
Did you find this useful? Your rating helps others.
No ratings yet.


