On this page
How do you connect Anzma to Egypt’s e-invoicing system?
In six steps, some on the authority’s portal and some in Anzma. This page is the “how” guide; the wider “what is e-invoicing and who must use it” question is on e-invoicing software in Egypt, and the comparison with Saudi Arabia is on e-invoicing software.
| Step | Where | Who | Notes |
|---|---|---|---|
| 1. Register on the portal | Authority portal | Business owner | Register the business, branches and your system |
| 2. Integration credentials | Authority portal | Business owner | A client ID and secret for the ERP |
| 3. Signing certificate | Certificate issuer | The business | Usually on a USB token |
| 4. Integration settings | Anzma | System admin | Tax number, activity, branches |
| 5. Test on pre-production | Anzma | Accountant | Sample invoices, review errors |
| 6. Go to production | Anzma | System admin | Switch environment, enable auto-send |
What do you need from the authority before connecting?
Before opening any Anzma screen you need your business registered on the e-invoicing portal, your branches registered, and your system registered to obtain an integration client ID and secret. You also need an electronic signing certificate in your company’s name from a certificate issuer. These steps you do with the relevant bodies; they cannot be done from inside Anzma.
Implementation dates and registration details vary by what the authority announces, and we do not quote dates here so they cannot go stale. Once you have these details you move to Anzma to enter them.
We suggest collecting everything in one file before the first meeting: tax registration number, activity code, branch addresses as registered, the integration ID and secret, and who holds the token and where. Setup then becomes one organised session instead of days of chasing between bodies.
What do you set in the integration settings in Anzma?
Open the Integration settings screen and enter the business details. The environment stays on pre-production by default until you change it yourself, so nothing reaches production by accident.
- Environment: pre-production (preprod) or production (prod).
- Tax registration number (RIN) and activity code.
- Your branch addresses at the authority, each with its full registered address.
- The integration client ID and secret; credentials are stored encrypted.
- Signing method: signing agent or certificate file.
- Automatic sending on issue, which is off by default.
- A connection test button that confirms your credentials work.
How does electronic signing work?
The system requires every document to carry an electronic signature made with your company’s certificate, and that certificate normally lives on a USB token that cannot be plugged into Anzma’s cloud servers. So Anzma uses a small signing agent that you run on a PC in your premises that has the token. It works like this: the agent asks Anzma over the internet for waiting documents, receives the text to sign, signs it with the token and returns only the signature. No port is opened at your end, and Anzma never receives or sees the private key.
From the integration settings you generate an agent secret that is shown once and goes into the agent; generating a new one revokes the old one immediately. The alternative that needs no agent is uploading a password-protected certificate file (.p12 or .pfx), if your certificate comes in that form; the file and its password are stored encrypted.
Which documents are sent and how are they checked?
Sales invoices, credit notes and debit notes are sent, along with sales returns that did not come from the POS. POS sales go as receipts through Egypt e-receipt software when it is on, so one sale is never sent twice.
Before sending, Anzma builds the document from the invoice and validates it; if something is missing it sends nothing and shows the reason by field. Common errors include:
- The tax registration number or activity code is not set in settings.
- The issuing branch’s address is incomplete.
- A business customer with no tax registration number or a missing address.
- A free-text line, or an item without a GS1 or EGS code.
- A credit note for an invoice that was not sent yet or is not valid yet.
- An invoice issued longer ago than the system accepts.
- Document charges or rounding that the system cannot express.
What does daily work look like after connecting?
After moving to production it becomes a simple daily habit. A salesperson issues the invoice from sales as before. If automatic sending is on, the document is built, validated and queued for signing at once; otherwise a supervisor presses Send on one invoice or a selected group from the submitted documents screen, which has filters for status, date, customer and errors.
At the end of the day the accountant opens that screen and filters on invalid and failed statuses to fix what shows up, and a dashboard widget lists failed documents so they are not hidden. On the printed invoice, the authority’s identifier, the document status and a QR code appear once it is valid, so your customer can verify it.
It also helps to decide who holds which permissions: view documents, send and resend, cancel a document at the authority, and edit integration settings. Cancel, for instance, should not go to everyone who issues invoices, while sending suits whoever follows issuing daily.
How do you track an invoice’s status and cancel it?
Each invoice moves through clear statuses: queued, signing, submitted, valid, invalid, rejected, cancelled or failed. After sending, Anzma polls the result at growing intervals until it is valid or invalid, stores the errors returned for each field, and keeps the long identifier and share link used for the QR code.
A sent or accepted invoice is never edited; it is corrected with a credit note. An invoice sent by mistake can be cancelled from its screen with a reason, as long as you are within the window the system allows, and Anzma shows the hours left. After the window only a credit note remains. If a document fails you are notified with the reason.
Note that cancellation is recorded at the authority itself, not just in Anzma, so do not use it for a price or quantity error that a credit note and a new invoice can fix; keep it for a document that should never have been issued.
How do you see supplier invoices you received?
From the Received documents screen you sync the invoices your suppliers issued in your company’s name. Anzma pulls recent documents and tries to match the supplier to a contact of yours; then for each document you choose to match it to an existing purchase bill, create a purchase bill from it in purchases, or reject it with a written reason.
That turns the official document into an entry in your books without re-keying, and ties the received invoice to the purchase bill in accounting. Syncing and managing have separate permissions.
How are branches, permissions and security handled?
If your company has several branches, each has its own address registered at the authority, entered in the integration settings and used as the issuer details on every document from that branch. A missing branch address shows up as a clear error at send time instead of being found after a rejection.
Credentials, the certificate file and its password are stored encrypted, and the agent secret is shown only once when generated, with Anzma keeping only its hash. Send attempts and responses are logged per document so you can review the whole history. All of it sits under separate permissions for viewing, exporting, sending, cancelling, received documents and settings, so you can assign them by role.
How does the connection handle buyer types: company, individual and foreign?
The system distinguishes three types of buyer: a business, a natural person and a foreign party. Anzma validates the data of each type before sending: a business needs a tax registration number, a natural person needs the national ID when the invoice exceeds the threshold set by the authority, and a foreign party has different data.
The threshold value and the definition of each type are set and updated by the authority, which is why they are kept in a configuration file that can be changed without changing code, and the authority’s documents remain the reference. The practical advice is to enter each customer’s type and number in contacts from the start, so you do not discover a gap while sending.
How does an invoice and a credit note move through the connection?
An illustrative example with assumed numbers: a company sells goods worth 1,000 pounds to another company and issues an invoice with 14% tax of 140 pounds, so the total is 1,140. Anzma checks the buyer’s tax number, the item code and the branch address, then builds the document, asks the agent to sign it and sends it, and polls for the result until it becomes valid.
A week later the buyer returns a third of the goods. The invoice is not edited; a credit note linked to it is issued, signed and sent as its own document, stock goes back and the entry is adjusted. The note is not issued before the original invoice becomes valid.
What are the commonest error messages and how do you fix them?
The screen shows errors per field, and this table links a common state to its fix. The meaning of error codes issued by the authority is in its own documents.
| What you see | Likely cause | Fix |
|---|---|---|
| Waiting for signature | The signing agent is down or the token is locked | Switch on the agent PC and unlock the token |
| Failed with a customer error | A missing tax number or address | Complete the customer file and resend |
| Failed with an item error | An item without a code or its type | Add a GS1 or EGS code to the item |
| Invalid | The authority returned it with saved errors | Read the errors and fix the data |
| Credit note rejected | The original invoice is not yet valid | Wait for the original to be accepted, then send the note |
How does the accountant review the connection at month end?
Before closing the month set aside a short time to review documents; it is quicker than hunting for a gap after the close locks your books. It makes the monthly review a fixed habit instead of a reaction to the first query from the authority or your external reviewer, and it reveals the repeated patterns that need fixing at their source in the customer, item or branch, so they do not reappear next month, your team stops fixing the same problem every time, and you reach the close with clean books.
- Filter the sent documents screen on invalid, failed and stuck states, and handle everything that appears.
- Check that every sales invoice in the books has a valid document and that credit notes are linked to their originals.
- Sync received documents and match them to purchase bills or create what is missing, and reject what is not yours with a written reason.
- Export the documents list for your records if you have export permission.
- Review who holds send, cancel and settings permissions, and remove what is not needed.
How do we start?
The module runs on top of sales and switches on for companies created in Egypt when the business template includes sales. It is not tied to a plan feature; the general plan limits on users and monthly invoices apply as on pricing. If you also operate in Saudi Arabia, that side has its own ZATCA module with separate invoicing units and certificates. Book an online meeting for free and we will go through the checklist on your own business data, starting on the test environment before any real send.
Frequently asked questions
What are the steps to connect e-invoicing?
Six steps: register on the authority’s portal, obtain integration credentials, get a signing certificate, set up the integration in Anzma, test on pre-production, then move to production and enable auto-send. The first three are with the relevant bodies, the rest are in Anzma.
What do I need from the Tax Authority before connecting?
Register your business and its branches on the e-invoicing portal, register your system to obtain a client ID and secret, and hold an electronic signing certificate in your company’s name from its issuer. The authority sets details and implementation dates and publishes them on its site, so check there first.
How does electronic signing work?
Your certificate stays on a USB token at your premises. A small signing agent on that PC asks Anzma for waiting documents, signs the text with the token and returns only the signature, with no inbound port opened. The alternative is uploading a password-protected certificate file if yours comes in that form.
Can I test on a pre-production environment?
Yes. The module starts on pre-production by default and only moves to production when you change it in settings. Test with sample invoices and review the errors, then switch environment and enable automatic sending once you trust your item and customer data.
Why is an invoice rejected and how do I fix it?
Most often because of missing data: an item code or its type, a branch address, a business customer’s tax number, or a credit note for an invoice not yet accepted. Anzma checks these before sending and shows the error by field, and it stores the authority’s rejection reasons too. Fix the data and resend from the screen.
Can I cancel an invoice I already sent?
Yes, from the document screen with a reason, as long as you are within the cancellation window the system allows; Anzma shows the hours left. After that, correct it with a credit note. A sent or accepted invoice is never edited, and Anzma does not offer to edit it.
How do I see invoices received from suppliers?
On the Received documents screen you sync recent invoices issued in your company’s name. Anzma matches the supplier to your contacts, then you match the document to an existing purchase bill, create a purchase bill from it, or reject it with a reason. Viewing and managing have separate permissions.
Is Anzma approved by the Egyptian Tax Authority?
To be precise, Anzma’s e-invoice module integrates with the authority’s e-invoicing system following its published specifications. We do not claim approval or listing by the authority. Check the authority for any conditions on solution providers, and ask us in the meeting about test-environment status.
What is the difference between a valid and an invalid invoice?
After sending, Anzma polls for the document’s result. Valid means the authority accepted it; invalid means it was returned with saved errors shown per field so you can fix them and resend. A valid invoice is not edited, it is corrected with a credit note.
How does the connection handle an individual or foreign buyer?
The system distinguishes a business, a natural person and a foreign party, and Anzma validates each type’s data before sending. The national ID threshold for individuals is set by the authority, so enter the customer type and number in contacts from the start and check the authority for the current value.
Part of the product line
e-invoicing software
Issue the invoice from your sales system and send it to Egypt’s Tax Authority or Saudi Arabia’s ZATCA depending on the company’s country, with the status of every document tracked.
Official sources
Rate this page
Did you find this useful? Your rating helps others.
No ratings yet.


