On this page
What is an e-receipt?
It is a sales receipt issued in a structured electronic format from the point of sale and sent to the Egyptian Tax Authority through a system separate from the e-invoice system. It carries a QR code that lets the buyer look up the receipt, and it is aimed at direct consumer sales at the counter.
People search for it as “e-receipt”, “ETA e-receipt system” or “POS e-receipt integration”. In Anzma it is handled by the e-receipt module (eta_receipts), part of the e-invoicing software line for Egypt and Saudi Arabia, and it sits on top of the POS and the ETA e-invoice integration.
Receipt or invoice: which one do you need?
A receipt is for counter sales to consumers; an invoice is for sales to companies and business customers. One business can need both: a counter for walk-in buyers and invoices for wholesale and corporate customers.
Anzma keeps them apart. With the e-receipt module on, POS sales go out as receipts and not as e-invoices, while ordinary sales invoices and credit notes go to the e-invoice system. So one sale is never sent twice.
| Aspect | E-receipt | E-invoice |
|---|---|---|
| Buyer | A consumer at the counter | A company or business customer |
| Source in Anzma | The POS screen | The sales module |
| Ordering | A chain per POS device | Invoice numbering |
| Correction | A return receipt | A credit note |
| QR code | Printed on the POS receipt | On the document once accepted |
How does a receipt travel from the POS to the system?
After the first setup the whole path is automatic, and the cashier sees nothing extra. This is how it goes.
- 1
A sale at the POS
The cashier completes the sale as usual. A simplified invoice is issued, deducts stock and posts to the books.
- 2
The receipt is built
Anzma builds the receipt with seller, branch, activity, items, taxes and payment method, computes its identifier and links it to the previous receipt on the device.
- 3
Signing
The receipt is signed with your company’s certificate through a signing agent on a PC that has the signing token, or with a certificate file, as chosen in settings.
- 4
Sent in order
Each device’s receipts are sent in chain order, and that device’s queue pauses briefly on a transient fault so the order stays intact.
- 5
Accepted and tracked
Anzma follows the receipt’s status at the authority until it is accepted or rejected, and stores rejection reasons so they show on the receipts screen.
What does it take to run it? (the honest version)
Setup involves two sides: what the authority requires and what you configure in Anzma. One thing to know up front is that signing needs your company’s certificate, which normally lives on a USB token that cannot be plugged into a cloud server. So Anzma uses a small signing agent that you run on a PC in your premises.
- On the authority’s side: register the business and its POS devices and obtain credentials for each device.
- In Anzma: enter each POS device’s serial number and credentials, and test the connection with the dedicated button.
- A signing certificate issued to your company; it does not come from Anzma.
- A PC that runs the signing agent and stays online during business hours, or a certificate file if that suits you.
- Items with correct codes and tax data, plus the tax registration number, activity and branches set in the settings.
What does the e-receipt mean for your business?
The idea is the same wherever you sell at a counter, but the work differs. This is how it looks in Anzma, not a ruling on who must issue e-receipts; that is the authority’s decision.
| Business | How it works in Anzma | Industry page |
|---|---|---|
| Retail and supermarkets | Barcode scanning, fast checkout, a receipt per sale | [[industry:supermarket|supermarket management software]] |
| Restaurants and cafes | A receipt when the order is paid at the POS | [[industry:restaurant|restaurant management software]] |
| Pharmacies | POS with batch tracking and permissions | [[industry:pharmacy|pharmacy management software]] |
| Clinics | A receipt if payment is taken at the clinic cashier | [[industry:clinic|clinic management software]] |
What does the e-receipt Anzma builds contain?
Anzma builds the receipt from the sale’s own data, so nothing is keyed twice. The header carries the identifier, issue time, number and currency, alongside the seller’s tax registration number, branch and activity. Then come the item lines with code, unit, quantity, price and tax, the tax totals and the payment method. Buyer details are optional and added when the customer asks.
Most rejections come from missing item data or business settings rather than a sending fault. So Anzma validates the receipt when it builds it; if something is missing the receipt shows as failed with a list of errors, you fix them and retry. It is best to prepare the basics before you start.
- A correct code and tax data for every item sold at the POS.
- Tax registration number, activity code and branch address in the integration settings.
- A serial number and credentials for every POS device.
- POS payment methods that match the types the system accepts: cash, card, wallet and others.
How do you track receipts and fix rejected ones?
The module has two screens: E-receipts, listing every receipt with its status, device and errors, and E-receipt settings, for business data, each device’s registration status and the automatic sending option. Each has its own permissions: view, export, send and resend, view and edit settings, so only people you choose can change settings.
If a receipt fails or is rejected, Anzma notifies the responsible users and keeps the reason so you can fix it, then you resend from the same screen. A dashboard widget lists failed receipts so they stay in front of you. Under the system’s published rules a receipt may not be resendable after a certain time, so do not leave failures sitting.
How does a receipt connect to stock, accounting and shifts?
The e-receipt does not change how the cashier works. A POS sale stays a simplified sales invoice that deducts items from warehouses, posts to accounting with a double entry, and feeds shift closing and the day’s reports. The e-receipt is an extra layer built on top and sent to the authority.
That is why your internal numbers match what was sent: every receipt has a matching sales invoice and you can go from one to the other. If you need a tax invoice for a business customer instead of a receipt, use sales and send it as an e-invoice.
How do multiple devices and branches work?
The chain belongs to the device, not the company. With two branches and three POS devices you have three independent chains, each device with its own serial number, credentials and linked receipts. A fault on one device therefore does not stop the others; only the affected device’s queue pauses and then resumes.
Devices are registered on the e-receipt settings screen, where each device shows its registration status, receipt count and last identifier sent, and has its own connection test button. A new device sends nothing until its details are entered, so no receipt leaves an unregistered device.
What does this module not cover?
It is fair to state the limits so you do not expect more. The module connects the Anzma POS to the e-receipt system; it does not replace what belongs to your business or the authority.
- It does not give you a signing certificate; that is issued to your company by its issuer.
- It does not decide whether you are obliged; that is the authority’s call.
- It does not send business invoices; those use the e-invoice module.
- It is not for Saudi counter sales; those use the ZATCA module.
- It does not supply hardware; it runs in the browser on your existing devices.
What about returns and internet outages?
A return is its own receipt of the return type, referencing the original receipt, so the system knows what was sold and what came back. The original receipt stays as issued.
During an outage the POS keeps selling locally and syncs when the connection returns, and the e-receipts for those sales are created at sync time in chain order. A receipt printed during the outage carries no official QR code or system number, because those do not exist before sending. The rest of the back office needs internet.
What does one day of sales on a till look like?
An illustrative example with assumed numbers: a pharmacy with one till makes three sales in the morning: one in cash for 120 pounds, one by card for 200 and one in cash for 50. A receipt is built for each, the second links to the first and the third to the second in the device’s chain, and they are sent in the same order.
Then the second customer returns an item worth 50 pounds, so a return receipt is issued that points to the original sale receipt, and the original is not touched. At the end of the day the supervisor closes the shift, the receipt totals match the till totals, and the supervisor reviews the receipts list and finds no failures, or handles those found.
The point is that the cashier does nothing extra. All of this happens behind the sale, and its result shows on the receipts screen for anyone with view permission.
What does the buyer see when scanning the QR code on the receipt?
The code leads to the receipt page on the authority’s portal, where the buyer can view its data. The link is built from the receipt identifier, its issue time, its total and the business’s registration number, so the buyer needs no special app and no account.
The official code appears only after the receipt is sent and accepted, because the identifier comes from the system. That is why a receipt printed during an outage, before sync, does not carry it. If a customer asks to verify, ask them to scan after sync, or check the receipt on the receipts screen.
What should you watch in a restaurant, a pharmacy or a clinic?
The idea is the same, but each type of business has a watch point tied to how it takes payment and what data it holds.
- Restaurant and café: the receipt is issued when the order is paid at the till, so make sure delivery and dine-in orders go through the same till.
- Pharmacy: a medicine item needs a code and correct tax data, and batches and permissions are managed in stock, not in the receipt.
- Clinic: the receipt concerns payment at the clinic till, not services recorded without payment.
- Shop and supermarket: there are more devices, so name each device clearly and follow its chain separately.
- Everyone: the payment methods at the till must match what the system accepts: cash, card, wallet and others.
How do you pilot one device before rolling e-receipts out to your branches?
A fast rollout multiplies any mistake by the number of devices. A gradual pilot is better: one device in one branch for a few days on the pre-production environment, then more devices, then production. Keep a short note of the errors that appeared and how they were handled, so it becomes a reference for the other branches and for any new employee who takes over the till later, and you avoid repeating the same explanation in each new branch you add, while the supervisor is reassured that everyone works the same way.
- Register the device with its serial number and credentials, and press the connection test button.
- Make a sale with each payment method you accept, and a test return.
- Check that the receipt is signed and arrives as accepted, and that the code shows on the printout.
- Train the cashier on what to do if sending is late, and the supervisor on reviewing failures.
- Add one device after another, and do not move to production until failures from the previous device settle.
What are the most common e-receipt mistakes?
Most mistakes come from item data and settings, not from sending itself.
- Items without a code or tax data, especially items added in a hurry at the till.
- A device whose data was not entered, or whose connection was not tested before selling.
- Leaving the signing-agent PC off during working hours.
- Delaying the handling of failed receipts until they exceed the periods the system allows.
- Mixing up the consumer receipt and the business customer’s invoice.
- Not reviewing the tax registration number, activity code and branch address in the settings.
Why is the receipt chain per device?
Each receipt carries a reference to the receipt before it on the same device, forming a connected chain from which no link can be removed without the gap showing. That is why sending order matters, and the third receipt is not sent before the second.
In practice this means two things. First, a temporary fault on one receipt stops only its device’s queue until handled, so order stays sound and receipts do not overtake each other. Second, the end-of-day review is done per device, so you quickly see which device is behind and which receipt holds it up.
You do not need to understand the details of how receipts are linked to benefit. It is enough to know that Anzma builds, orders and sends them in sequence on your behalf, and that the receipts screen shows the device, status and error of each receipt.
How do we start?
Start with the POS, then add e-receipts once your items and branches are in order. The module sits beside the e-invoice module, and both share the environment (test or production) and the business details. It is not tied to a plan feature; user and invoice limits apply as on pricing.
Before the meeting, note how many POS devices you have, whether you hold the signing certificate, and which PC could run the agent. Then book an online meeting for free and we will set it up on a test environment first. For business invoices see e-invoicing software in Egypt.
Frequently asked questions
What is an e-receipt?
It is a sales receipt in a structured electronic format, issued from the point of sale and sent to the Egyptian Tax Authority with a QR code. In Anzma it is issued from the POS screen in a chain per device, signed and sent automatically or by button, and you follow its status from the e-receipts screen.
What is the difference between an e-receipt and an e-invoice?
A receipt is for counter sales to consumers, an invoice for sales to businesses. They go to different systems and use different correction documents: a return receipt for one, a credit note for the other. In Anzma a POS sale is never sent twice; it goes as a receipt when the module is on.
Is my business required to issue e-receipts?
The Egyptian Tax Authority decides which activities are covered and the implementation phases, and publishes them on eta.gov.eg. We list no dates or lists here so they cannot go stale. Check with the authority or your accountant, then book a meeting and we will show how the connection is set up on your POS.
Do I need an approved POS device?
Whether the authority requires a particular device or vendor is for the authority to say, and we do not assert it here. Anzma runs in a browser on your own devices, and each POS device is registered with its serial number and credentials. Check with the authority before buying any hardware.
What is printed on the receipt?
The POS receipt prints a QR code in the required format carrying the receipt identifier, time, total and the company’s registration number, leading to the receipt page on the authority’s portal. The official code is printed once its data exists, so a receipt printed during an internet outage does not carry it.
Does it suit restaurants, pharmacies and clinics?
Yes, wherever sales are made at an Anzma POS. A restaurant issues the receipt when the order is paid, a pharmacy from its counter, a clinic if payment is taken at its cashier. Sales to companies use e-invoicing instead. The authority decides how far the obligation reaches for each activity.
What happens if the internet drops?
The POS keeps selling and stores sales locally, then syncs when the connection returns, and the e-receipts are created at sync time in chain order. A receipt printed during the outage has no official QR code. Other back-office screens need internet, and some POS actions are unavailable offline.
What is needed for signing?
Receipts must be signed with your company’s certificate, usually on a USB token that cannot be attached to a cloud server. So you run a signing agent on a PC that holds the token; it asks Anzma over the internet for what to sign and returns only signatures. A certificate file is the alternative where available. The certificate itself comes from its issuer.
Is Anzma approved by the Egyptian Tax Authority for e-receipts?
To be precise, Anzma’s e-receipt module integrates with the authority’s e-receipt 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.
How do I register a till in the e-receipt system?
You register the device with the authority and get its credentials, then enter its serial number and data on the e-receipt settings screen and press the connection test button. Sending does not start from a device until its data is entered, so no receipt leaves an unregistered device.
Can a receipt be edited after it is sent?
Receipts are not edited after sending. If a customer returns goods, a return receipt pointing to the original is issued and the original stays as issued. The system may set a period for resending a failed receipt, so handle failures the same day.
Does the e-receipt work with several branches and devices?
Yes. Each till has its own chain, serial number and credentials, so two branches with three tills give three chains. A fault on one device does not stop the others; only its own queue pauses and then resumes.
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.


