UAE e-invoicing readiness takes eight steps, and this PINT AE checklist puts them in order.

Plan backwards from your implementation date.

With revenue of AED 50 million or more, you appoint an Accredited Service Provider by 30 October 2026, and implement by 1 January 2027. Below that, you appoint by 31 March 2027, and go live on 1 July 2027. Ministerial Decision No. 244 of 2025 sets them, as amended by No. 66 of 2026, and the timeline gives every date with its source.

The Ministry of Finance publishes its own readiness checklist, seventeen yes-or-no questions, as Appendix 2 of its guidelines. It tells you what must be true on the day. This guide adds the order of the work and what usually sits behind each question inside an ERP.

Step 1. Assume you are in scope, then settle which entity participates.

Under Ministerial Decision No. 243 of 2025, e-invoicing applies to any person doing business in the UAE, for every business transaction, whether or not it is registered for VAT, unless the person or the transaction is specifically excluded. Sales to consumers are out until the Minister decides otherwise, and the timeline lists the other exclusions. The format matters too, since the Ministry of Finance says a PDF, a Word document, an image, a scanned copy or an email is not an e-invoice.

One provider handles both your sending and your receiving. Each member of a tax group onboards on its own, and how to choose an ASP covers what that means. Trade between members of the same VAT group has 24 months' grace from 1 January 2027, and everything else they do runs on the normal timetable.

Hold as evidence a list of your legal entities, the revenue of each for its most recent accounting period, and the phase each one falls in.

Step 2. Your identity on the network is your TIN.

The Tax Identification Number (TIN) is the first 10 digits of your 15-digit TRN. A business in scope that is not registered for any tax must register with the Federal Tax Authority to obtain one. In a tax group, use the first 10 digits of your own TRN, not the representative member's.

On the invoice, the seller's electronic address is that TIN, and the electronic identifier is the fixed value 0235 for businesses registered in the UAE. Three predefined buyer endpoints cover buyers who have no participant identifier of their own:

• 0235:9900000098 when the buyer has not yet implemented e-invoicing. That buyer still receives a regular tax invoice as well, such as a PDF.
• 0235:9900000099 for an export where the buyer has no Peppol identifier.
• 0235:9900000097 for a deemed supply, whoever the supplier is.

Before onboarding, the Ministry asks you to confirm that your company details in EmaraTax, such as trade licence, address and contacts, are current.

Step 3. Measure the gap on a month of real invoices.

The Ministry of Finance's Mandatory Fields document, version 1.0 of 23 February 2026, lists 51 mandatory fields for an electronic tax invoice and 49 for a commercial invoice, meaning any invoice that is not a tax invoice. The counts are ours, taken from the numbered rows in its sections 4.1 and 4.2.

Scope from the Ministry's list and test against the rules, since the specification's cardinality column alone understates the work. In the PINT AE 1.0.4 invoice semantic model, 40 elements are mandatory at every level of their branch, 37 business terms and 3 scheme-identifier attributes. We counted every element whose own minimum occurrence, and every parent group's minimum, is one. The Ministry's list is longer because the UAE-specific validation rules make optional elements mandatory in practice: IBR-127-AE requires a payment due date whenever an amount is due, IBR-150-AE requires the seller's legal registration identifier, and IBR-143-AE and IBR-144-AE require the city and emirate on both addresses.

To measure it, export one full month of invoices and credit notes, the awkward ones included. For each mandatory field, record where it comes from in your system, whether it is filled on every document, and whether its format matches the code list. Twenty of the 51 fields describe the seller and the buyer, and they come from your company, customer and address records rather than the invoice itself, which is why the next step takes longest.

Step 4. Master data decides how many invoices are rejected.

No provider does this work for you. Check, record by record:

• Customers and suppliers. A TRN where they are VAT-registered, which the rules require to be 15 digits, starting with 1 and ending with 03 (IBR-132-AE), or a 10-digit TIN where they are not. The legal name as registered. A legal registration identifier with its type: TL for a trade licence, EID for an Emirates ID, PAS for a passport or CD for a Cabinet Decision. For a trade licence, the name of the issuing authority too (IBR-172-AE, IBR-101-AE).
• Addresses. The first address line, the city, the country code, and the emirate as the country subdivision, which for a UAE address must be one of seven codes: AUH, DXB, SHJ, UAQ, FUJ, AJM or RAK (IBR-128-AE).
• Items. A name and a description, a unit of measure held as a code rather than free text, and a tax category on every item. Goods also need an HS classification code and services a service accounting code (IBR-184-AE to IBR-186-AE).
• Tax categories. Every item and line mapped to one of the six categories in the guidelines, which are standard rate, exempt, outside the scope of VAT, reverse charge, zero-rated and margin scheme. Domestic reverse charge applies only to the goods the Cabinet has listed, such as electronic devices, precious metals and stones, crude oil, natural gas and metal scrap.
• Free zone customers. Where the person who ultimately uses or owns what you supply is not the customer, the e-invoice has to name that beneficiary too, and a free zone invoice must carry a beneficiary ID (IBR-007-AE).

The evidence is a count of records failing each check, before and after the clean-up, and a named owner who keeps new records clean.

Step 5. Map every scenario you invoice to its flags.

Every invoice carries a transaction type code made of eight flags: free zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, supply through e-commerce, and exports. More than one can apply to the same invoice, and each brings its own requirements. Map your real scenarios, starting with these.

• Credit notes. The decision requires an electronic credit note when a transaction is cancelled, when the agreed price is reduced, when consideration is returned, and when an administrative or numerical error is corrected. A credit note can cover part of an invoice, and one credit note can reference several earlier invoices. Each one needs a reason code from the specification's list and, in most cases, a reference to the invoice it corrects (IBR-158-AE, IBR-055-AE).
• Advance payments. The advance triggers its own tax invoice when it is received, so the final invoice bills only what remains.
• Retention and milestones. The retention calculation goes on a separate commercial document, not on the e-invoice, and the retained amount is invoiced with VAT when it falls due.
• Foreign currency. Each line of a tax invoice carries its VAT amount and its amount payable in AED, and the invoice must show the gross amount payable in AED.
• Rounding. Applied to the invoice total, to two decimal places, and not at tax category level.
• Self-billing. Only between two VAT registrants, and only once the buyer is on the e-invoicing system itself.

Keep as evidence a scenario list drawn from last year's invoices, each scenario with one real document mapped field by field.

Step 6. Appoint one provider, and put three answers in writing.

Choose from the Ministry of Finance register, finish the contract and commercial terms, then start onboarding yourself: your EmaraTax account administrator opens the e-invoicing tile, selects the provider and is passed to its portal. The provider then issues your Peppol participant identifier. How to choose an ASP covers what to test before you sign.

The Ministry's own checklist asks about each of them: how invoice data reaches the provider, how success and failure messages come back to you, and where data is hosted and how it is secured.

Step 7. Test the whole loop, rejections included.

The guidelines list what testing has to cover: sending invoice data to the provider, the provider issuing the invoice to the buyer, the success or failure message coming back, receiving a supplier's e-invoice, the provider reporting tax data to the Federal Tax Authority, and the confirmation of that reporting.

Use your own documents from Step 5 and add the cases that go wrong in production: a rejected invoice, its correction and resubmission, a credit note against an invoice issued before go-live, and a supplier's e-invoice arriving in your payables process. A perfect sample file proves only that the connection works.

Step 8. Give errors an owner before the clocks start.

Before go-live, agree a governance model for resolving errors with your provider. From go-live, these time limits run:

• Send each e-invoice or credit note on time: 14 days from the transaction, or the VAT law's timeline if you are registered for VAT.
• Tell the Federal Tax Authority about a system failure inside 2 business days.
• Pass any change to your registered data on to your provider inside 5 business days of the Authority confirming it.
• Keep every e-invoice, credit note and its data for as long as the Tax Procedures Law requires. Where the decision says 'within the State', the guidelines read that as a test of access, not of server location: the Authority must be able to have them produced, complete and readable, on request. A provider can store them for you under contract, while the legal duty remains yours.
• Keep sending a regular tax invoice, alongside the e-invoice, to any buyer not yet on the system.

The whole checklist, with the evidence for each step.

SolaryxDev does the data and testing steps.

Steps 3, 4, 5 and 7 are ours, and they happen inside the system you already run: measuring the gap on a month of your invoices, cleaning the master data, mapping every scenario to PINT AE, and testing the whole loop with your provider, rejected invoices too.

Where your data needs more than a clean-up, data readiness and migration covers it. Start at UAE e-invoicing readiness, or book a call.