Guide · UAE e-invoicing
ERP integration for UAE e-invoicing: what your system must do before go-live
On this page12 sections
Short answer: UAE e-invoicing is live for early adopters, and it becomes mandatory from 1 January 2027 for businesses with revenue of AED 50 million or more, who must appoint an Accredited Service Provider (ASP) by 30 October 2026. Everyone else appoints by 31 March 2027 and goes live on 1 July 2027. The ASP carries invoices across the Peppol network and reports to the FTA, but your ERP, billing app or portal still has to produce all 51 mandatory fields, correctly, for every invoice and credit note. That ERP integration is the part most businesses underestimate.
This guide is for the people who look after the system that raises invoices: finance managers, IT leads and owners of businesses running custom, in-house or portal-based billing. It covers the dates, who is in scope, what the ASP does and what stays with you, how to map the 51 fields, and the questions to ask before you sign with an ASP.
Timeline: the dates that apply to you
Your phase depends on revenue, defined in Ministerial Decision No. 244 of 2025 as gross income in the financial statements for your most recent accounting period. The decision says "equal to or exceeds" AED 50 million, so a business at exactly AED 50 million is in the first phase.
| Who | Appoint an ASP by | Mandatory go-live | Notes |
|---|---|---|---|
| Pilot group (MoF Taxpayer Working Group) | By invitation | From 1 July 2026 | Written consent only |
| Any business, voluntarily | When you choose | From 1 July 2026 | Full technical rules apply; e-invoicing penalties don't |
| Revenue AED 50m or more | 30 October 2026 | 1 January 2027 | Moved from 31 July 2026 by Ministerial Decision No. 66 of 2026 |
| Revenue below AED 50m | 31 March 2027 | 1 July 2027 | |
| Government entities | 31 March 2027 | 1 October 2027 | |
| Transactions inside one VAT group | — | 24-month grace from 1 January 2027 | Timing relief only; still in scope |
| Air cargo under an air waybill | — | Excluded for 24 months from go-live |
Only the first-phase appointment date has moved. Ministerial Decision No. 66 of 2026 changed it from 31 July to 30 October 2026, and the Ministry of Finance described the extension as targeted and final. Some pages still show 31 July, including the phase table in the MoF's own guidelines dated 1 June 2026. The decision overrides that table.
Who is in scope
E-invoicing is not only for VAT registrants. Ministerial Decision No. 243 of 2025 covers every business transaction by any person doing business in the UAE, covering B2B, B2G, G2B and G2G.
| Your situation | In scope? | What it means |
|---|---|---|
| VAT-registered, selling to businesses | Yes | Tax invoices and tax credit notes become e-invoices and e-credit notes |
| Not VAT-registered, selling to businesses or government | Yes | You issue commercial e-invoices; register with the FTA for a TIN if you have no tax registration |
| Selling only to consumers (B2C) | No | Out of scope until the Minister decides otherwise |
| Selling to both businesses and consumers | Yes, for business sales | Consumer sales stay outside e-invoicing |
| Non-resident that must issue UAE tax invoices | Yes | Those invoices are issued as e-invoices |
| Holding company with only passive income | No | A recharge, such as a management fee, brings it in |
| Imports under the reverse charge | No e-invoice needed | Domestic reverse-charge supplies still need an e-invoice without VAT |
| Excluded supplies | No | Sovereign activity not in competition with business, air passenger tickets, VAT-exempt or zero-rated financial services |
How the exchange works
The UAE uses a Peppol "five-corner" model. Your system (corner 1) sends invoice data to your ASP (corner 2). The ASP validates it, converts it to PINT-AE XML and delivers it to the buyer's ASP (corner 3), which passes it to the buyer (corner 4). Both ASPs report the tax data to the FTA (corner 5), and confirmations flow back. The e-invoice has no QR code or barcode, and the format supports Arabic and English.
Your address on the network is 0235: plus your 10-digit Tax Identification Number (TIN), the first
10 digits of your 15-digit TRN. You start onboarding yourself, from the e-invoicing tile in the FTA's
EmaraTax portal, after signing with an ASP. Each business uses one ASP for both sending and
receiving, and each member of a VAT group onboards under its own TIN.
What an ASP does and what your own system must do
The MoF's e-invoicing guidelines are clear that the ASP carries the invoice but the compliance obligation stays with the supplier.
| Task | ASP | Your ERP, billing app or portal |
|---|---|---|
| Hold correct customer and product data | No | Yes: buyer TRN/TIN, Peppol ID, address, emirate, unit codes, tax categories |
| Calculate every invoice value, including AED amounts | No | Yes |
| Produce the data for all mandatory fields | Receives it | Yes, in a format the ASP accepts |
| Gather the buyer's Peppol participant ID | No | Yes, from the customer |
| Look up the buyer on Peppol and transmit securely | Yes | No |
| Assign a unique identifier (UUID) to each e-invoice | Yes | Keep your own unique, sequential invoice numbers |
| Validate, convert to PINT-AE XML and report to the FTA | Yes | No |
| Return confirmations and rejections | Yes | Store them, show them to staff, fix and resend |
| Issue within 14 days of the transaction or payment, whichever is earlier | No | Yes |
| Tell the ASP about changes to your FTA-registered data within 5 business days | No | Yes |
| Tell the FTA about a system failure within 2 business days | No | Yes |
| Keep records for the retention period | Agree it in the contract | Yes, retrievable on request |
The 51 mandatory fields: a mapping exercise
The MoF's mandatory fields list sets 51 fields for a tax e-invoice and 49 for a commercial e-invoice. Most exist somewhere in your database already. The work is finding where, filling the gaps and agreeing a rule for each one.
| Group | Fields | Where it usually lives | Typical gap |
|---|---|---|---|
| Invoice details | 9: number, date, type code, currency, transaction-type flags, payment due date, business process type, specification ID, payment means | Invoice header, order, payment terms | The 8-digit flag string (free zone, deemed supply, margin scheme, summary, continuous supply, disclosed agent, e-commerce, exports) isn't recorded anywhere |
| Seller | 11: name, electronic address (TIN), identifier 0235, legal registration ID and type (TL, EID, PAS or CD), TRN, tax scheme, address, city, emirate, country |
Company settings | The licence-issuing authority is typed by hand, with no code list |
| Buyer | 9: name, electronic address, identifier, TRN, tax scheme, address, city, emirate, country | Customer master | TIN or Peppol ID never collected; emirate held as free text |
| Document totals | 5: line net total, total without tax, total tax, total with tax, amount due | Invoice totals | Totals that don't match the lines after rounding |
| Tax breakdown | 4: taxable amount, tax amount, category code and rate per category | Tax settings | Local tax codes that don't map to standard, zero-rated, exempt, out of scope, reverse charge or margin scheme |
| Invoice lines | 13: line ID, quantity, unit-of-measure code, net amount, net and gross price, price base quantity, tax category and rate, VAT in AED, line amount in AED, item name and description | Order lines, item master | Unit labels such as "ctn" instead of a unit-of-measure code (the MoF's example is KG); no AED amounts on USD or EUR invoices |
Three rules catch people out. Line VAT and line totals must be in AED even when you invoice in another currency, converted at the Central Bank rate, and the tax accounting currency field becomes mandatory. You can't add your own optional fields to PINT-AE, so anything your customers rely on has to fit the fields that exist. And there is no "provisional invoice" category: a provisional invoice is an e-invoice, adjusted later by a credit note or a further invoice.
IT readiness checklist
Work through this with whoever owns your billing system. The MoF publishes its own e-invoicing hub and checklists; this list is the system side of it.
- Confirm your phase from last year's revenue, and put the appointment and go-live dates in the project plan.
- Check your own registration. Trade licence, address and TRN in EmaraTax must be current. Without any tax registration, apply for a TIN first.
- Clean the customer master. For every business and government customer: legal name, TRN or TIN, Peppol participant ID, address, city and emirate. Ask customers for their Peppol ID now.
- Clean the product master. Item names and descriptions, a proper unit-of-measure code, and a tax category on every item.
- Fix invoice numbering. Unique and sequential, never reused, with cancelled invoices reversed by credit note rather than deleted.
- Make credit notes first-class documents. E-credit notes are needed for cancellations, price reductions, returns and errors, and they must reference the original invoice.
- Store AED amounts for every line on foreign-currency invoices, with the rate used.
- Record scenario data: free-zone beneficiary details where the end user differs from the buyer, export and deemed-supply flags, and summary or continuous-supply invoices.
- Do the mapping sheet. One row per mandatory field: source table and column, transformation, default, and who fixes gaps.
- Build the connection to your ASP (API, file exchange or ERP connector) and bring confirmations and rejections back into your system with an error queue your team works daily.
- Watch the 14-day clock. Alert staff when an invoice hasn't been accepted within a few days.
- Test end to end with the ASP before go-live: sending, receiving, FTA reporting, credit notes, foreign currency and every scenario you use.
- Plan the purchase side. Supplier e-invoices will arrive through the same ASP and need matching to purchase orders.
- Set up archiving for e-invoices, credit notes and confirmations for the full retention period.
How to choose an ASP
The official list of accredited and pre-approved ASPs showed 56 fully accredited providers and 8 pre-approved providers as of 24 September 2026, and it changes often. We don't recommend any particular provider. These questions, drawn largely from the MoF's considerations for selecting an ASP, separate a good fit from a poor one for a custom or in-house system:
- API: Is there a documented REST API and a test environment? Can we see the documentation before signing?
- Formats: Will it accept our data as JSON or CSV and build the XML, or must we send PINT-AE XML?
- Feedback: How do confirmations and rejections come back: webhook, polling or email?
- Connectors: Is there a ready connector for our ERP, and who maintains it when the ERP updates?
- Pricing model: Subscription or per invoice? Are receiving, storage and support charged separately? Are the 100 free e-invoices a year set by Ministerial Decision No. 64 of 2025 written into the contract?
- Data residency: Where is our data stored, and can we export all of it if we leave?
- Product ownership: Is it the ASP's own platform or a resold one?
- Service levels: What uptime and support response times are promised, and in which hours?
- Scale: Can it handle our peak invoice volume without throttling?
Storage and offshore servers
MD 243 says records must be stored "within the State". The MoF guidelines (section 5.4) explain that this is met if records sit in a secure system that preserves their integrity and can be produced promptly and in full to the FTA, whether the storage is inside or outside the UAE. Retention follows the Tax Procedures rules: normally five years after the tax period for taxable persons, seven years for real estate, with extensions during audits or disputes. This matters if your ERP runs on a non-UAE cloud or your developers are offshore.
Penalties
Cabinet Decision No. 106 of 2025 sets the e-invoicing penalties. They apply from each business's mandatory date and not to voluntary adopters.
| Failure | Penalty |
|---|---|
| Not implementing e-invoicing, including not appointing an ASP on time | AED 5,000 per month or part month |
| Not issuing or transmitting an e-invoice on time | AED 100 per invoice, up to AED 5,000 per calendar month |
| Not issuing or transmitting an e-credit note on time | AED 100 per credit note, up to AED 5,000 per calendar month |
| Not notifying the FTA of a system failure on time (issuer or recipient) | AED 1,000 per day |
| Not telling the ASP about changes to FTA-registered data | AED 1,000 per day |
Common integration pitfalls
- Expecting the ASP to fix your data. It validates and rejects. It can't invent a buyer's TIN or an emirate you never stored.
- Mapping only the standard invoice. Credit notes, foreign-currency invoices, free-zone sales, exports and summary invoices each need testing.
- Rounding. Decide whether you round per line or per total and test it against the ASP's validation before go-live.
- Dropping the PDF too early. Until a buyer is onboarded, you send a normal tax invoice as well
as the e-invoice, using the special endpoint
0235:9900000098. Exports to a buyer without a Peppol ID use0235:9900000099, and deemed supplies use0235:9900000097. - Hand-typed fields. The licence authority name has no code list, so agree one spelling per authority and store it.
- VAT-group IDs. Each member's TIN comes from its own Corporate Tax TRN, not the group representative's.
- Forgetting the purchase side. Supplier e-invoices arrive through your ASP too.
- Starting late. Integration and testing take time, and non-implementation costs AED 5,000 a month.
How we help
We're a software company with a development team in India, and we work with UAE businesses remotely. We have no UAE office or licence, and we are not an Accredited Service Provider, can't become one and aren't partnered with any ASP. What we do is build: we change your billing system, ERP or ordering portal so it holds the right master data and produces all the mandatory fields, then connect it to the ASP you choose through that ASP's API, with confirmations, rejections and an error queue brought back into your system. If your system can't be changed, we can build the layer that sits between it and the ASP.
You get a fixed quote after a 20-minute call, so the full cost is known before work starts. Book a call or ask for a price. For the invoice rules themselves, read our guide to UAE tax invoice requirements, or see what we build for UAE businesses.
Sources
- Ministry of Finance, eInvoicing programme hub (accessed 24 September 2026)
- Ministry of Finance, Accredited and pre-approved e-invoicing service providers (last updated 24 September 2026)
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System (2025)
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System (2025)
- Ministerial Decision No. 66 of 2026 (May 2026)
- Ministry of Finance, Targeted amendments to e-invoicing decisions (10 May 2026)
- Ministerial Decision No. 64 of 2025 on ASP eligibility and accreditation (2025)
- Cabinet Decision No. 106 of 2025 on e-invoicing violations and penalties (8 December 2025)
- Ministry of Finance, UAE Electronic Invoicing Guidelines v1.1 (1 June 2026)
- Ministry of Finance, UAE Electronic Invoice mandatory fields v1.0 (23 February 2026)
- Ministry of Finance, Considerations for selecting an Accredited Service Provider v1.0 (23 February 2026)
- OpenPeppol, PINT-AE specification 1.0.4 (29 July 2026)
Last reviewed 24 September 2026. This guide explains published guidance and isn't legal or tax advice.