National E-Invoicing: Getting Your System Through the Gateway

Since 1 April 2025, an invoice in Jordan is no longer a piece of paper you issue.

It is a document you issue with a third party's approval.

The sentence looks small, and it is the largest change to your operations in years — because

everything built in your shop or office on the assumption that an invoice leaves when you decide it

leaves is now built on an assumption that no longer holds.

The sentence this book rests on

Compliance is a question of systems, not of intent.

And nobody violates this in bad faith. Every violation I have seen is the same kind: entirely sound

intent, and a process that was never redesigned. An employee issues an invoice on the portal and records

it in the books — so you now have two truths. Or a return is handled by editing the original invoice — **and

it cannot be edited**. Or a sale stops because the connection dropped, so the goods go out with a note on the

side, "we'll fix it tomorrow".

All of them are the acts of a well-meaning person inside a system that was not designed for this.

What actually changed — and what did not

Unchanged: what you sell, your price, the tax due, and your relationship with your accountant.

Three things changed, and all of them are in the process rather than in the paper:

1. The invoice is cleared before it exists. You send it, it is checked, and a code comes back that

makes it an invoice. Before that you do not have an invoice — you have an attempt.

2. The invoice cannot be edited after issue. Every correction is a new document referencing the

original.

3. The invoice now leaves a trace outside your books. Whatever passed the gateway exists at the

Department whether or not you recorded it. **So the match between what you issued and what you booked became

checkable from outside.**

Why an error costs more than it appears

The fine is the cheapest item on the list, and it is up to JOD 500 per violation as published.

More expensive than that: an invoice issued outside the system is not valid as a tax document. So

your registered buyer loses the input tax deduction on it, and their expense may not be recognised. Which

means you did not violate this alone — you cost your customer money, and they will know, and they will

ask you for it, or buy from someone else next time.

And the difference is fundamental: a fine is paid once, **and a business customer who cannot deduct their

inputs from you does not come back**.

When not to buy a new system

I sell systems, and I will say when not to buy one:

• When your existing system can connect. Most accounting and point-of-sale systems in use today have

added the connection or can add it. Ask your current supplier before you ask a new one.

• When your volume is small and your invoices are simple. The platform itself allows direct issuing. **And

disciplined manual issuing beats a system you cannot operate.**

• When your problem is the process rather than the tool. If your returns are chaos on paper today, **they

will stay chaos inside any system** — faster.

• When the motive is fear. Whoever buys while afraid of a fine buys what is offered to them, **not what

suits them**, and learns the difference after the migration.

And the most honest of the four is the third, the only one money does not solve.

A rule that governs this whole book

Do not make this book your technical reference.

And I will say plainly why: I reviewed several suppliers' guides and they **contradict each other on the

specification itself — on the file format, and on whether a digital signature is required at all. And all

of them sell integrations.**

The specification changes, and the operational layer does not. So this book is about the second: what

breaks in your process, how to test it, who owns it, and what to do when the gateway is unreachable.

**As for fields, formats and codes, they have one source: the Income and Sales Tax Department and its

platform.** What your supplier says is verified there, not in a book.

What this book is — and is not

It is not a tax book, and issues no ruling on a rate, an exemption or a goods classification. **Consult

your accountant and the Department.**

Nor is it about choosing an ERP — that is "Selecting and Implementing an ERP System"; **nor about

point-of-sale — that is "The Point-of-Sale System"; nor about clinics** — that is "The Clinic System". This

book assumes them and does not repeat them.

And when we reach cleaning and migrating customer data, that is "Cleaning and Migrating Your Data", **and

I will point at it rather than repeat it**.

Action steps

1. Write the sentence and post it at the point of sale: compliance is a question of systems, not of intent.
2. Confirm the mandate date and your own position with your accountant, not from an article.
3. Ask your current system's supplier about connecting before you ask any new vendor.
4. Go honestly through "when not to buy a system" — and if an item applies, stop here.
5. Ask: is my problem the tool or the process?
6. Name today who owns this file in your business, by name.
7. Open the Department's site and its platform, and make them your reference for fields and formats.
8. Do not start buying before chapter three — the inventory comes first.