Egypt: invoices and receipts

Egypt started before its neighbours, which makes its experience the most useful thing to read for anybody who has not started: everything that will happen in Saudi Arabia and the UAE over two years has already happened there.

And the most important lesson is not technical: the threshold moves. Build a solution that suits today’s size and you have built something to revisit when the threshold drops below you.

Two systems, not one

This is the first thing people reading about Egypt get wrong.

	The e-invoice	The e-receipt
For whom	Business to business or government	Business to final consumer
What is sent	A document in an approved format, cleared and given a unique identifier	A sales receipt from the point of sale
Who it covers	Every registered taxpayer	Retail and direct services

A retailer selling to both businesses and individuals is subject to both. Implement one, assume you are finished, and you meet the second as a penalty.

The operational difference is larger than the cosmetic one: the invoice comes out of the accounting system, and the receipt comes out of the point of sale — a different system, usually from a different vendor, needing its own project.

The moving threshold

The mandate in Egypt is tied to VAT registration, and the threshold has fallen.

As tax advisory firms report Resolution No. 281 of 2025: the mandatory registration threshold was cut from EGP 500,000 to EGP 250,000 with effect from 1 January 2026, with newly in-scope taxpayers required to register by 31 March 2026.

The attribution here is deliberate: that figure is reported by advisers rather than read off the authority’s own text, so verify it on the Egyptian Tax Authority’s site before deciding anything on it. It is also a live illustration of this station’s point: the number you built on may have moved since this page was published.

And the lesson transfers straight to the Gulf: a threshold is not a fixed line you stand behind. It is a number that falls, and you watched it fall in Saudi Arabia to SAR 187,500. Basing a decision on “I am below the threshold” is basing it on something in motion.

The e-receipt — why it is a separate project

Because the receipt does not come out of your accounting system. It comes out of the point of sale.

	The invoice	The receipt
Its source	The accounting system or the ERP	The point-of-sale system
Its rhythm	Batches, within a window	Instant, with every sale
Its volume	Hundreds a month	Thousands a day
Who owns it	Finance	Operations or retail

That last row is why most receipt projects stall: the file is opened in finance and executed in a department that does not report to it and does not read its emails.

Three questions to put to the point-of-sale vendor, in writing:

• Is the version I run today supported, or do I need an upgrade? An upgrade is a project with a budget.
• What happens when connectivity drops? Retail selling does not stop, so receipts are either queued and sent later or lost.
• Who reviews rejections daily, and where do they appear?

Anybody with no answer to the second finds out after the first outage that a full day of sales never reached the authority.

What is worth taking from the Egyptian experience

Three things recurred there and will recur in every market.

One: coding is the obstacle, not integration. Connecting a system to the platform is weeks of work. Coding items against an approved classification is months, and needs a decision from procurement and finance rather than from technology. That is station six.

Two: missing data at the other end blocks you. An invoice to a customer without a valid tax registration number is rejected however sound your system is. Cleaning customer data starts six months before the mandate, because it means writing to them.

Three: the receipt gets forgotten. The invoice project runs with a budget and a team, and the point of sale is left because it is “a different system” — and then it is the penalty.

Three differences that transfer straight to the Gulf

Read Egypt against its neighbours rather than on its own, because the three differences are the lesson.

	Egypt	Saudi Arabia	The UAE
Mandate began	The earliest	2021 for generation	Not yet started
How it widened	By cutting the threshold	By adding waves	By revenue band
Intermediary	None — direct integration	None	An accredited one, mandatory

The second row matters most. Egypt widened scope by lowering a number and Saudi Arabia widened it by adding waves — and the result is the same: whoever was outside is now inside.

The conclusion that serves a reader in Riyadh or Dubai today: do not ask “am I in scope?” but “when am I in scope?”. The difference between those two questions is the difference between a planned project and one run against a deadline.

What you actually do in this station

• Decide which system applies to you, or whether both do.
• Verify the current threshold on the authority’s own site, not on this page and not in an article.
• Count your customer data: how many customers have no complete tax registration number in your system? That number is the size of the work ahead.
• If you have a point of sale, ask its vendor today about readiness, and ask for the answer in writing.
• Name who owns item coding in your company.

The three commonest mistakes

One: conflating the two systems. One gets implemented and the file is assumed closed.

Two: relying on an old threshold. Thresholds fall, and whoever was out of scope yesterday is in scope today.

Three: deferring customer data. It is the one thing you cannot fix alone, because it needs the other party to reply.

The acceptance test for this station

1. Separate the invoice system from the receipt system and say who is subject to each.
2. State the current threshold and your source for it, with the date you read it.
3. Explain why coding takes longer than integration.
4. State how many customers in your system have incomplete tax data.
5. State the Egyptian lesson that transfers to the Gulf in one sentence.

What comes next

The three markets are covered. The next station opens the document itself: anatomy of an electronic invoice — the fields, the stamp, the chain, the QR code, and what each of them does.