Businesses that struggled with e-invoicing in other markets rarely failed at the technology. They failed at data: customer records with no tax number, item lines with no unit code, three spellings of the same legal name, and a habit of editing invoices after they had been sent. All of that is fixable, and all of it takes longer than connecting the software.
Weeks 1–2 · Decide and appoint
- Confirm which phase you are in. The test is annual revenue against the AED 50 million threshold — if you are close to it, plan against the earlier dates.
- Choose your accounting system and your accredited provider, and get both costs in writing.
- Appoint the provider in EmaraTax and confirm the link shows Active.
- Name one owner. E-invoicing that belongs to "finance and IT" belongs to nobody.
Weeks 3–6 · Clean the data
This is the phase that decides whether the rest is quiet. Work through it as a data project with a definition of done, not as a background task.
-
Customers and suppliers
Legal name exactly as registered, address, country, and TRN for every registered counterparty. Deduplicate: two records for one customer become two endpoints and one argument.
-
Items and units
Every item needs a code and a unit of measure that maps to a standard unit code. "Each", "pcs" and "unit" as three different free-text values is the classic cause of a rejected line.
-
Tax categories
Go through your tax codes and classify each one: standard, zero-rated, exempt with a reason code, out of scope, reverse charge. A rate of 0% with no category behind it is ambiguous to the validator even when it is obvious to you.
Do this before testing, not during. Half of sandbox rejections trace back to it.
-
Document numbering
One sequence per document type, no gaps, no reuse. A transmitted number is consumed permanently — you cannot re-issue under it, even after a rejection.
Weeks 7–10 · Rehearse
Test in the sandbox with documents that look like your real month, not with three clean invoices.
- A standard-rated domestic invoice with several lines and a discount.
- A zero-rated export, and an exempt supply with its reason code.
- A reverse-charge purchase, if you buy services from abroad.
- A foreign-currency invoice with the tax stated in AED.
- A credit note against an invoice already accepted.
- A deliberately invalid invoice — a bad TRN — so you see what a rejection looks like before it matters.
Then rehearse the human parts: who fixes a rejection, how a correction is issued, and how a sales team member finds out that the invoice they raised did not arrive.
Weeks 11–13 · Go live early
Switch to live transmission before your phase date. A business using the system voluntarily, ahead of its own phase, is outside the penalty regime while it does so — which means your first live month costs nothing to get wrong. Going live on the deadline itself throws away that protection for no benefit.
Ready looks like
- Provider appointed and Active in EmaraTax
- Every counterparty record carries a validated TRN
- Tax categories classified, not just rated
- Inbound supplier invoices land somewhere owned
- Corrections issued as credit notes by habit
- Live and transmitting before the deadline
Not ready looks like
- "Our software vendor is handling it"
- Master data cleanup scheduled for the final month
- Testing limited to one clean invoice
- No plan for receiving
- Invoices still edited after issue
- Go-live planned for the deadline itself
What to do if your deadline is closer than 90 days
Compress in this order, and do not reorder it: appoint the provider first, because it has an external dependency; clean customer TRNs next, because they block the most documents; classify tax categories third; and test with your five most common document types. Everything else — supplier data, inbound handling, edge cases — can be improved while you are live. Being live and imperfect is a better position than being perfect and unappointed.
Questions people actually ask
How long does this really take?
For a business with clean data and one system, a few weeks. For a business with three spreadsheets, several thousand customer records and no TRNs, the data work alone fills the ninety days.
Do we need an IT project?
If your accounting system produces PINT AE and connects to your provider, no. If you are building a mapping layer between systems, yes — and that layer becomes something you own permanently.
What if we are not in the first phase?
You have longer, and the same list. Businesses under AED 50 million appoint by 31 March 2027 and go live on 1 July 2027; the pilot is open to you before that.
Can we start in the pilot without committing?
That is what the pilot is for. Voluntary use ahead of your phase carries no penalty exposure, and it is the only way to find your edge cases at a time of your choosing.
Where these facts come from
Checked against the following on 24 August 2026. Rules and dates change — if you are reading this long after that date, verify before you act on it.
- Ministry of Finance — eInvoicing programme
- Ministerial Decision No. 244 of 2025 on implementation
- Peppol PINT specifications
WisoBooks is a bookkeeping and business-management tool, not an accounting, tax or legal advisor. Nothing on this page is tax advice, and tax rules change. Confirm your own obligations with the relevant authority or a qualified advisor.
