E-invoicing readiness checklist
Tick a box only when the answer is "a system holds this, and I could show you where". A tick for "someone knows it" does not count. The gaps you find here are the work, and they are the same gaps an accredited provider will find in 2027, one rejected invoice at a time.
Part 1: the dates that apply to you
- I know which phase I am in.Revenue at or above AED 50 million: appoint an accredited provider by 30 October 2026, live 1 January 2027. Below AED 50 million: appoint by 31 March 2027, live 1 July 2027.
- I know that B2B and B2G invoices are in scope.Consumer sales are not covered by the current mandate. Anything you invoice to another business or a government entity is.
- I have looked at the Ministry of Finance accredited provider list at least once.If you invoice from an accounting package, check whether the vendor is on it. Zoho Software Trading LLC is, as of September 2026.
Part 2: where each field on the invoice comes from
For the invoice in front of you, where did each of these come from: a record in a system, a chat, a notebook, or memory?
- Customer legal nameThe registered name, spelled one way, everywhere.
- Customer TRN15 characters, held as a field, not typed from a photo in a WhatsApp thread.
- Customer addressStructured: building, street, emirate, not one free-text line.
- Line item descriptionsFrom an item list, not retyped from memory each time.
- Unit price per lineFrom a price list or the quote record, not from what someone remembers agreeing.
- Tax category per lineStandard, zero-rated, exempt or out of scope, set on each line. One rate at the bottom of the page is not this.
- Totals and tax breakdownComputed by the system from the lines, never typed in.
- Your own seller detailsName, TRN, address, consistent across branches and trade names.
Part 3: how the invoice moves
- Every invoice comes out of the same system.Including the rush jobs, the on-site jobs and the customer who pays cash. "Most of them" is the gap.
- Credit notes come out of the same system.They are e-documents too, and the same fields apply.
- Nobody retypes an invoice into a second place.Anything typed twice is somewhere two versions can disagree, and disagreement is what gets an invoice rejected.
- I could tell you today how many invoices from last month have no buyer TRN on them.If it takes a person a morning to answer, the data is not structured yet.
- I know who will see a rejected invoice, and how fast.Rejections come back from the provider. Someone has to own them or they sit.
Part 4: the customer cleanup, the part that takes longest
- One record per customer, no duplicates under different spellings.
- TRN on file for every VAT-registered business customer.The ones missing get chased now, not in June 2027.
- A place ready to hold each customer's electronic address.New under the UAE model: the identifier the network routes invoices with. Your provider will need one per customer.
- One item list with a tax category on every entry.
How to read it.
Every box ticked: appoint your provider and you are close to done. Talk to your accountant about anything in Part 1 you are unsure of.
Three to six unticked, mostly in Part 2: your software may be fine and your data is not. The cleanup in Part 4 is the job, and it takes weeks of small effort, so it starts now.
More than six unticked, or "a person remembers it" for the fields in Part 2: invoicing is running on memory and WhatsApp. That is the system build, and the deadline puts a date on it.
This checklist covers data and process. Your accountant stays the authority on how a specific supply is treated, and an accredited provider does the transmitting; we build the part before it.
Want us to run this against your real invoices?
Free 30-minute call. We trace one of your invoices back to where each field came from and tell you what has to change before a provider can accept it, and whether that needs a system or a settings change.
One measurable outcome, agreed in writing before we start. How the guarantee works →