Skip to content
Guide 14 min read Updated

Egypt’s ETA e-invoice and e-receipt: how to connect your POS, accounting and ERP

By Manager & CEO, SmartTech Studio

If you sell in Egypt, your sales system answers to the Egyptian Tax Authority (ETA). Sales to other businesses and to government go through the e-invoice system. Sales to consumers, at a till or online, go through the e-receipt system. They are separate systems with separate rules, and a business can be bound by one of them or by both.

Neither is a PDF. Each invoice or receipt is created as structured data, signed or authenticated, and submitted to the ETA from the system that made the sale: your POS, your accounting package, your ERP or your online store. If that system cannot do it, it is not ready for Egypt.

This guide explains how the two systems work, how to check whether you are obligated, what the integration involves and how to prepare, in order. It is written for owners and finance teams, not as tax advice. Rules and taxpayer lists change by ETA decision, so confirm your own position with your tax adviser and on the ETA website. The facts below were checked on 4 November 2026.

Two systems: the e-invoice and the e-receipt

The e-invoice system covers business-to-business (B2B) and business-to-government (B2G) sales. Its legal basis is Ministerial Decision No. 188 of 2020. It began with large taxpayers in November 2020 and was extended in phases until, by the end of 2022, the ETA required taxpayers across Egypt to issue electronic tax invoices.

The e-receipt system covers sales to the final consumer (B2C): a shop till, a restaurant, a clinic reception, an online store selling to individuals. It is rolled out by separate ETA decisions, each with an attached list of named taxpayers and a start date.

One does not replace the other. A distributor that sells to shops and also runs a retail branch may need both: e-invoices for the trade sales and e-receipts at the branch counter. Treat them as two integration projects, even if one system issues both.

Both sit alongside VAT, which is 14% in Egypt. The tax lines on every e-invoice and e-receipt must match the VAT you charge and declare.

Are you obligated? How to check

For the e-receipt there is no single nationwide start date. The ETA issues its decisions in main phases and sub-phases, and each decision binds the taxpayers named in its list from a stated date. The latest one we could confirm on the ETA website, Decision No. 361 of 2025, the first sub-phase of the ninth main phase, binds the taxpayers on its list from 15 November 2025. The one before it, Decision No. 281 of 2025, started on 15 September 2025.

So the question is not "how big is my business?" but "is my registration number on a list?" The ETA website has an inquiry page for exactly this. Check it, and check again whenever a new decision is announced; decisions appear on the ETA site and in the Egyptian press.

Taxpayers bound by the recent e-receipt decisions must also register on the portal of the ETA’s consumer incentive programme, «فاتورتك.. حمايتك وجايزتك», which rewards buyers for asking for an electronic receipt.

Two warnings. First, figures quoted online as an e-receipt "threshold" are often something else, such as the receipt value above which the buyer’s national ID must be recorded. Second, if you are not on a list yet, a new POS or ERP should still be built ready for it. Rebuilding a till system against a deadline costs more than building it right the first time.

What e-invoice integration involves

Item codes. Every line on an e-invoice carries a code: a GS1 barcode number, which you register on the ETA portal, or an internal EGS code, which the ETA must approve before you can use it. Approval takes time, so code your catalogue first. A missing or unapproved code is one of the most common reasons an invoice is rejected.

The electronic signature. Each e-invoice is signed before submission, either with a USB token issued to a named signatory or with an e-seal for automated signing, both from a licensed certification provider. A token is fine for a few invoices a day; a system that issues many should sign automatically.

Submission. Your system sends the signed document to the ETA as JSON or XML in the ETA’s format. The ETA validates it and returns a unique identifier (UUID) for each accepted document. Your system should store that UUID with the invoice and show every rejection to someone who can fix it.

Corrections. An accepted invoice is not edited. You correct it with a credit or debit note that references the original, or cancel it through the ETA within the window and rules the ETA sets. Your accounting has to follow the same logic, or your books and the ETA’s records will disagree.

Master data. Your customers’ tax registration numbers and addresses, and the tax type of every item, must be right, because validation is automatic. Mistakes a clerk used to fix by hand now come back as rejected invoices.

What e-receipt integration involves

Every point of sale is registered. Each POS device is registered under your tax registration number on the ETA’s taxpayer profile portal before it issues a single receipt, and that registration gives the device its own client ID and secret. The POS then authenticates with them, together with its serial number and operating system version, and receives an access token that the ETA’s SDK says is valid for one hour. Only a taxpayer the ETA has tagged for consumer (B2C) sales can submit receipts.

A central system does not remove that step. The ETA’s e-receipt FAQ lets an ERP be registered as a single virtual POS only when the business has one branch or one outlet. If several outlets issue receipts through a central ERP, every POS in every outlet must be registered, and each receipt still carries the serial number of the POS it came from and the branch code registered with the tax office.

Receipts are chained. Each receipt’s UUID is a SHA-256 hash of its own content, and that content includes the UUID of the previous receipt from the same POS, left empty only for the very first one. A return receipt carries the UUID of the sale it reverses, and the SDK allows a return up to 540 days after the sale. That is why receipts cannot be deleted or renumbered after the fact: the chain would break. To cancel a whole sale, the POS issues a return receipt for its full value.

A rejected receipt has its own fix. You correct it and send it again with a new UUID, the same previous UUID it had before, and the old UUID in a “reference old UUID” field. The ETA’s FAQ allows this within 96 hours of issue; after that, the correction goes through a late submission request.

The printed receipt carries a QR code. Its content is a link to that receipt on the ETA’s invoicing portal, followed by the receipt total and the seller’s registration number, on one line in a format the SDK specifies. Build it into your receipt template and test it on the printer you actually use, thermal paper included.

Offline sales. A shop does not stop selling when the internet drops, and the ETA does not require a connection at the moment of sale. Receipts can be issued offline, stored on the POS and sent later, as long as the gap between issue and submission stays within the period the ETA sets, which its FAQ gives as 24 hours at present. Past that, the taxpayer files a late submission request on the portal. The FAQ says a request currently opens a 48-hour window to send receipts up to 30 days old, and the SDK adds a yearly cap on the number of requests. The FAQ also says the taxpayer bears any consequences the ETA sets for receipts not sent in real time, so the POS should alert someone well before the 24 hours run out.

Batch limits. One submission can carry up to 500 receipts (1.5 MB), and one receipt up to 300 lines. A POS that queued a long offline day has to send it in several batches, not one.

Buyer details. Most consumer receipts need none. When the buyer is a person, their name and national ID become mandatory once the receipt total reaches 150,000 Egyptian pounds; that is the value for receipt version 1.2 and later, and it was 50,000 for versions 1.0 and 1.1. A sale to a company, whatever its value, belongs on an e-invoice, not a receipt, according to the ETA’s FAQ. The POS should ask for personal details only when the rule applies, and handle them under the Personal Data Protection Law (Law 151 of 2020).

These details come from the ETA’s e-receipt SDK and its e-receipt FAQ, which we read on 19 November 2026. The ETA describes several of them as current settings that it can change, so check them again before you build on a number.

Choosing or upgrading a POS for the e-receipt: what to test

A demo on the vendor’s laptop proves very little. Before you buy a POS or pay to upgrade the one you have, test it on a real till in a real branch, connected to the ETA’s pre-production environment.

Approved hardware, and a team behind it. The ETA publishes a list of approved POS suppliers, and its e-receipt FAQ points businesses to it. Its POS technical specification also asks for software that can be modified and a development team able to build the integration. Ask which of the vendor’s models is on the list, and who will maintain the ETA connection when the SDK changes.

One registration per device. Add a second till to a test branch and time it from registration on the portal to its first accepted receipt. Ask where the client ID and secret are stored, and what happens when the ETA warns that a device’s credentials or active dates are about to expire. The SDK defines those notices, and a good system shows them to a manager before anything fails.

The offline queue. Unplug the router for an hour, keep selling, then reconnect. Every receipt should arrive in order, with the chain intact. Then ask what the screen shows when receipts are still unsent as the 24-hour limit nears, and who gets that warning.

Returns and voids. Return one item from yesterday’s receipt and void a whole sale. Both should produce return receipts that point to the original UUID, and stock and cash reports should then match the ETA portal.

The QR code on paper. Print a receipt on the branch’s own thermal printer, scan it with a phone and check it opens the right receipt on the ETA portal. A code that reads on screen can still fail on a narrow roll or a faint print.

Item codes at the till. Every item sold needs its GS1 or EGS code. Check that a new product cannot be sold before it has one, and that a cashier cannot type a free-text item the ETA will reject later.

Buyer details only when needed. Ring up a sale of 150,000 pounds or more to an individual and check that the POS asks for the name and national ID, and not on ordinary sales. Then ask where those IDs are stored, who can see them and for how long: questions that fall under Egypt’s Personal Data Protection Law.

Branch reporting. With two branches connected, compare each POS’s daily total with what the ETA portal shows for it. If head office needs spreadsheet exports to see that, the reporting is not finished. If the POS also feeds stock and accounts, our guide to ERP systems in Egypt covers that half.

Packaged software, a connector, or a custom build

If you run a packaged accounting or ERP system with an Egyptian version, the vendor usually provides e-invoice support, and sometimes e-receipt support too. Ask in writing which documents it supports, how it signs, and whether it handles a POS that goes offline. Then test it on your own data.

If your sales run through a custom or older system, an online store, or several systems at once, someone has to build the connection: map items to codes, sign, submit, store the UUIDs and handle rejections. It is the same kind of work we describe in our guide to POS and ERP integration and our UAE e-invoicing guide: the rules differ by country, but the plumbing is similar.

And sometimes the honest answer is to replace the system. If the POS cannot work offline, cannot be registered per branch or has no supported way to sign, patching it will cost more than a POS and ERP built for the rules. Our comparison of custom and off-the-shelf software helps with that decision.

The preparation, in order

1. Check your status. Search your registration number on the ETA’s e-receipt inquiry page, and confirm your e-invoice obligations with your tax adviser.

2. List every system that issues an invoice or a receipt: the POS in each branch, the online store, the ERP, the accounting package, and the spreadsheet someone still uses for corporate customers. The spreadsheet is the one that usually gets missed.

3. Code the catalogue. Give every item and service a GS1 or EGS code, and apply for EGS approvals early.

4. Put the signing in place: a token for a named signatory, or an e-seal for automated signing, from a licensed provider.

5. Register each POS and branch with the ETA, and register on the incentive portal if your decision requires it.

6. Connect and test on the ETA’s pre-production environment before going live: a normal sale, a return, a credit note, a sale to a company, a sale to a consumer, an offline hour, a rejected document.

7. Train the counter and finance staff: no edits after issue, how corrections work, and what to do when a submission fails.

Mistakes we see

Treating the e-invoice and the e-receipt as one project. They share codes and master data, but the POS work for receipts is a job of its own.

Leaving item coding to the last week. EGS approvals are not instant, and every uncoded item blocks an invoice.

A POS that only works online. One bad connection day becomes a compliance problem as well as lost sales.

Nobody watching rejections. A rejected document that no one sees is an invoice the ETA never accepted.

Building only for today’s list. If you plan to grow, open a branch or sell to consumers, build for the obligation you will have, not just the one you have now.

How we help businesses in Egypt

SmartTech is a software house in Abu Dhabi that serves Egyptian clients remotely; we have no office in Egypt. We build and connect POS, accounting, ERP and online-store systems so that they issue ETA e-invoices and e-receipts, in Arabic and English. More on how we work with Egyptian companies is on our Egypt page.

We don’t publish prices for Egypt. Every project is quoted in writing after a short call, line by line: systems, branches, integrations and support. Send us a WhatsApp message with what you run today and what you need it to do.

Sources

FAQ

Is a PDF invoice sent by email enough in Egypt?

No. For a business in scope, the tax invoice is the signed electronic document the ETA has accepted, with its UUID. You can still send the customer a PDF copy, but the PDF is not the invoice.

If I already issue e-invoices, do I also need the e-receipt?

Only if you sell to final consumers and your registration number is on an e-receipt decision list. The two systems are separate: e-invoices for business and government sales, e-receipts for consumer sales. Many businesses need both.

How do I know if my business must issue e-receipts?

Search your tax registration number on the ETA’s e-receipt inquiry page, and watch for new decisions. Each decision names its taxpayers and a start date; the latest we confirmed, Decision No. 361 of 2025, started on 15 November 2025.

Can my POS keep selling if the internet goes down?

It should. A well-built POS issues receipts offline, queues them and submits them when the connection returns, within the time the ETA allows (currently 24 hours). If your current POS stops selling or loses receipts when it goes offline, fix that first.

What is the difference between a GS1 code and an EGS code?

GS1 codes are the international barcode numbers carried by many products; you register them on the ETA portal. EGS codes are internal codes you create for items and services that have no GS1 code, and the ETA must approve each one before you use it.

What are the penalties for not complying?

Fines for failing to issue or report invoices and receipts are set under the Unified Tax Procedures Law (Law 206 of 2020). The figures quoted online differ and are not all from the ETA, so check the amounts that apply to you with your tax adviser rather than relying on a blog, this one included.

العربية