e-Invoicing
What is EmaraTax onboarding for e-invoicing (UAE)
What is EmaraTax onboarding for e-invoicing: the direct answer for UAE e-invoicing, with the instruments named and the next step clear.
what is emaratax onboarding for e-invoicing uae
The FTA platform flow that links your business identity to the e-invoicing system, walked through with your ASP. It connects your TIN-linked identity to the network: complete it before Peppol registration and testing. Transmission runs through an Accredited Service Provider over the DCTCE network, and the 51 PINT AE mandatory fields (49 for a commercial invoice) define the document.
Basis: UAE Ministry of Finance - the framework decision for the e-invoicing system
- Mandatory fields, electronic tax invoice
- 51
- UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026
- Mandatory fields, commercial electronic invoice
- 49
- UAE Electronic Invoice mandatory fields, version 1.0, 23 February 2026
- Revenue threshold splitting the two phases
- AED 50,000,000
- Article 5(1), Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System
# The direct answer
The FTA platform flow that links your business identity to the e-invoicing system, walked through with your ASP. It connects your TIN-linked identity to the network: complete it before Peppol registration and testing.
# What you need to know
The instruments behind the answer: MD No. 243 of 2025 (the system), MD No. 244 of 2025 as amended by MD No. 66 of 2026 (the timetable), MD No. 168 of 2026 (providers), Cabinet Decision No. 106 of 2025 (penalties), and the MOF mandatory-fields v1.0 (23 February 2026). Work from the instruments, not from summaries.
# How to handle it
Work through these in order.
-
Confirm your position
Check the scope and phase rules against your facts: entity, revenue, transaction types.
-
Act on the answer
The FTA platform flow that links your business identity to the e-invoicing system, walked through with your ASP. It connects your TIN-linked identity to the network: complete it before Peppol registration and testing.
-
Evidence it
Keep the records the framework expects: transmissions, validations, reconciliations, archive.
# Practical notes
If the answer changes your plan, update the plan in writing with an owner and a date. E-invoicing rewards the businesses that treat it as a project with artefacts, not as news to have read.
# Pitfalls to design around
Mapping without tax advice is the quietest pitfall: every ERP tax code must resolve to exactly one PINT AE category, and the person doing it needs the VAT legislation open, not just the field list. Designated Zone scenarios, reverse charge and zero-rated versus exempt distinctions are where 'close enough' codes become misreported positions.
Numbering discipline is the next: sequential, gap-free series per entity, separate series for credit and debit notes, documented void handling. Validators and the FTA both read numbering as a completeness signal.
Finally, the moving target: PINT AE, the PASR and FTA guidance will evolve, especially in the first two years. Assign someone to track publications now, because a specification change with a compliance date is a project with a deadline, and the network enforces the new rules whether you tracked them or not. Pilot where you can: a bounded pilot with real invoices finds every one of these problems while they are still cheap.
# What the FTA would ask for
In a review, the authority asks for records, not narratives: the transmitted documents, the validation history, the correction trail from original through credit note, the monthly reconciliations, and the archive. Each should be producible within a timeframe the request respects.
Correction trails deserve emphasis: every credit and debit note referencing its original, every resubmission logged with its rejection. A ledger that matches the network record is the strongest position a business can hold.
Keep the rule-change log too: which PINT AE or guidance updates arrived, when, and what changed in your process in response. It shows a compliance function that tracks its obligations, which is exactly what a reviewer wants to see.
Sources and legal basis
Legislation and decisions6
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System
- Ministerial Decision No. 66 of 2026 (amending the implementation timeline in MD No. 244 of 2025)
- Ministerial Decision No. 168 of 2026 on the eligibility criteria and accreditation procedure for Service Providers
- Cabinet Decision No. 106 of 2025 on Violations and Administrative Penalties for the Electronic Invoicing System
- Federal Decree-Law No. 28 of 2022 on Tax Procedures
Authorities, systems and registers3
- Federal Tax Authority (FTA)
- UAE Ministry of Finance
- EmaraTax
Terms used5
- Accredited Service Provider (ASP)
- Decentralised Continuous Transaction Controls and Exchange (DCTCE)
- Peppol
- PINT AE
- UAE Peppol Authority Specific Requirements (PASR)
- UAE Electronic Invoicing System - Ministerial Decision No. 243 of 2025UAE Ministry of Finance - the framework decision for the e-invoicing system
- Implementation of the Electronic Invoicing System - Ministerial Decision No. 244 of 2025UAE Ministry of Finance - phases, thresholds and the revenue definition
- UAE Electronic Invoice mandatory fields, version 1.0 (23 February 2026)UAE Ministry of Finance - the 51/49 mandatory field lists for PINT AE invoices
- Federal Tax Authority - official portalFederal Tax Authority - enforcement, EmaraTax onboarding and published guides
Rates, thresholds and deadlines change. Every figure above is linked to the authority that publishes it — if the two ever disagree, the authority is right and this page is out of date. Tell us and we will fix it.
Frequently asked questions
I am not registered for VAT. Do I still need e-invoicing?
Quite possibly: the mandate applies to persons conducting business, not to VAT registrants. If you are in scope without any tax registration, register with the FTA to obtain a Tax Identification Number, which the network requires. Make the TIN the first milestone: nothing downstream works without it.
How long does an e-invoicing implementation take?
A single-entity SME with clean data and a standard connector can be done in weeks to a couple of months; a multi-entity enterprise is a multi-month programme. The long poles are master-data cleansing, provider selection and testing. Start all three early rather than compressing them against the deadline.
Does e-invoicing apply to B2C sales?
Not in the current scope: business-to-consumer transactions are excluded for now. B2B and B2G transactions are in scope. Mixed businesses implement for the B2B stream and should design the stream classification so B2C can be added later if the scope widens.
What is the 14-day rule?
Article 6(5) of Ministerial Decision No. 243 of 2025 requires each invoice to be transmitted through the system within 14 days of the business transaction. Rejections do not pause the clock, so the error queue needs same-day triage and the flow to the ASP should be automated or tightly scheduled.
When does e-invoicing become mandatory for my business?
From 1 January 2027 if your revenue is AED 50 million or more, and from 1 July 2027 for everyone else conducting business in the UAE. Phase-1 businesses must appoint an Accredited Service Provider by 30 October 2026. Revenue means gross income for the most recent accounting period per your financial statements. A voluntary pilot has run since 1 July 2026.
What are the penalties for e-invoicing non-compliance?
Cabinet Decision No. 106 of 2025 lists the e-invoicing violations and their administrative penalties: failures to implement the system or appoint an Accredited Service Provider on time, to issue and transmit e-invoices and credit notes on time, to notify the FTA of a system failure, and to tell the provider about changes to registered data. Read the penalty table in the decision itself. You have 40 business days to seek reconsideration of a penalty decision, and 20 business days from awareness to voluntarily disclose your own error.