UAE E-Invoicing Implementation Guide for SMEs: Step-by-Step for the 2027 Mandate

Phase 2 of the UAE e-invoicing mandate lands on 1 July 2027 for businesses below AED 50 million in revenue — and Phase 1 buyers start demanding compliant invoices from 1 January 2027. If your larger customers go live first, they may reject your PDF invoices months before your own deadline.

This guide walks through the actual implementation, step by step — the questions SMEs ask when they sit down to do it, not just what the mandate says.

Step 1 — Confirm which phase you're in

Use your most recent audited financials. If you're close to the threshold, ask your auditor — the FTA counts revenue, not profit.

Watch out: phases apply to you as an issuer. Your customers' phases apply to them. A Phase 1 customer can require compliant invoices from you in January 2027 regardless of your July deadline.

Step 2 — Appoint an ASP on EmaraTax

Every in-scope business must route invoices through a Ministry of Finance accredited service provider. You cannot connect to the FTA directly.

1. Log in to EmaraTax with UAE Pass
2. Open the e-invoicing onboarding section
3. Select your ASP from the accredited list and accept the designation
4. The ASP completes technical activation on its side

Allow 1–2 weeks between designation and activation — ASPs provision your seller record before invoices can flow.

Step 3 — Clean up your invoice data

This is where most SME implementations actually struggle. PINT-AE validation is stricter than what your accounting software probably accepts today:

• Buyer TRN — 15-digit format, mandatory for VAT-registered buyers
• Addresses — emirate must use the official code list (DXB, AUH, SHJ…), not free text
• Party identifiers — trade licence numbers, legal registration names
• Tax categories — every line needs a coded category (S, Z, E, O), not just a percentage
• Line-level math — line net amount must equal qty × price ± charges/allowances exactly

Pull a sample of your last 50 invoices and check them against this list. The fields that fail are nearly always buyer TRNs and free-text addresses.

Step 4 — Connect your software to the ASP

Three integration patterns, roughly in order of effort:

You do not need to change your accounting software. The ASP converts whatever format you send into PINT-AE XML — that's its job. See our integrations for the full list of supported systems.

Step 5 — Test in the sandbox

Never discover problems on your first live invoice. An ASP sandbox mirrors the real flow without submitting to the FTA:

• Send your real invoice shapes — including edge cases like credit notes, zero-rated exports and mixed VAT rates
• Read the exact validation errors the ASP returns
• Fix your data or templates until invoices pass cleanly

TrustBill's sandbox shows the same field-level errors Microvista returns, so what passes in test passes in production.

Step 6 — Go live and monitor

• Issue live invoices and watch the first submissions end to end
• Track rejections — the first week surfaces any data gaps the tests missed
• Confirm buyer-side receipt with your biggest customers

What implementation costs

• ASP fees — typically AED 0.50–2 per invoice, or a fixed tier; see our cost and pricing guide
• Setup — self-service platforms like TrustBill: AED 0; custom integration projects: AED 2,000–10,000
• Training — a day or two for whoever issues invoices
• Penalty for doing nothing — AED 5,000 per month of non-compliance

The realistic timeline

Starting now means you test while it's cheap — in sandbox, with zero penalty risk. Starting in May means every rejected invoice is a fire drill.

Start with a test invoice, not a sales call

The fastest way to understand e-invoicing is to send one. Create a free TrustBill account, upload or create a test invoice, and see exactly which fields the FTA will check — before you commit to anything.

For the full regulatory background, read our UAE E-Invoicing Guide, the ASP selection checklist, and the PINT-AE standard explained.