UAE e-invoicing
PINT AE requirements, in plain terms
PINT AE (Peppol International Invoice, UAE) is the structured XML format every in-scope invoice and credit note must follow under the UAE's Electronic Invoicing System. A PDF emailed to a customer, or a scanned paper invoice, no longer counts once your phase goes live. Your ERP has to produce complete, correct invoice data. An Accredited Service Provider (ASP) then validates that data, converts it to PINT AE where needed, delivers it over the Peppol network and reports the tax data to the Federal Tax Authority (FTA).
For companies running Microsoft Dynamics 365, the practical question is whether your current version, master data, tax setup and integrations can feed that chain without manual fixes. The Ministry of Finance's specification lists 51 mandatory fields for a PINT AE tax invoice. Most readiness problems start in the ERP, long before an invoice reaches the ASP.
Scope
Who the UAE e-invoicing mandate covers
- B2B and B2G transactions, invoices and credit notes exchanged between businesses and with government entities, subject to specific exclusions set out in the framework.
- VAT registration is not the trigger, the mandate applies to persons conducting business in the UAE, so non-registered businesses that issue in-scope invoices should check their position.
- Large businesses first, companies with annual revenue of AED 50 million or more form the first mandatory wave.
- All other businesses next, companies below AED 50 million follow in the second wave, then in-scope government entities.
- Pilot participants, a selected group began on 1 July 2026, and participants are temporarily exempt from penalties during the pilot.
- Both sides of the invoice, suppliers must be able to issue PINT AE invoices, and buyers must be able to receive and store them through their own ASP.
The dates that matter
The legal basis is Ministerial Decisions No. 243 and No. 244 of 2025. In May 2026 the Ministry of Finance amended Decision 244 and moved the ASP appointment deadline for large businesses from 31 July to 30 October 2026. The go-live date did not move. The timeline below reflects the position as of 6 October 2026.
-
1 July 2026
Pilot phase begins
Selected taxpayers test the system ahead of mandatory enforcement.
-
30 October 2026
Large businesses appoint an ASP
Applies to revenue of AED 50 million or more. This was moved from the original 31 July 2026 date.
-
1 January 2027
Large businesses go live
PINT AE invoices must be sent and received through the Electronic Invoicing System.
-
31 March 2027
Everyone else appoints an ASP
Applies to businesses below AED 50 million and to in-scope government entities.
-
1 July 2027
Remaining businesses go live
The second business wave becomes subject to mandatory e-invoicing.
-
1 October 2027
Government entities go live
B2G e-invoicing becomes mandatory for in-scope government bodies.
How an e-invoice travels from Dynamics 365 to your customer
The UAE uses a Peppol-based, decentralised "five-corner" model. Dynamics 365 sits at corner one. Your ERP never talks to the FTA directly. Every invoice passes through accredited providers who carry legal responsibility for validation and exchange.
Dynamics 365 creates the invoice
Posting a sales, free text or project invoice produces the structured data: parties, TRNs, lines, VAT and totals.
Your ASP validates it
The ASP checks the data against PINT AE rules, converts it to PINT AE XML if needed and rejects anything incomplete.
The buyer's ASP delivers it
The invoice crosses the Peppol network to the buyer's ASP, which passes it into the buyer's own system.
Tax data reaches the FTA
Required tax data is reported to the FTA platform (corner five), and status messages flow back to your ERP.
Invoice data
What PINT AE needs from your invoice data
PINT AE is built on the international Peppol PINT model (UBL 2.1 under the hood) with a UAE-specific layer for local VAT rules. The data dictionary holds more than 135 elements across mandatory, conditional and optional fields. The 51 mandatory fields for a tax invoice fall into a few groups your ERP must fill every time.
- Invoice details: number, issue date, invoice type and currency
- Seller and buyer identity, including Tax Registration Numbers (TRNs)
- Line items with quantities, prices and recognised unit-of-measure codes
- VAT breakdown by tax category, plus document totals and amount due
- Credit notes in the same structured format, linked to the original invoice
- Electronic archiving of records for at least five years
How Dynamics 365 supports PINT AE compliance
Microsoft Dynamics 365 already holds most of what a PINT AE invoice needs: customers, items, tax codes and posted transactions. Compliance comes from shaping that data correctly and connecting it to an ASP. Dynamics 365 is not itself an ASP. Here is where each part of the work happens.
VAT and invoice data
Sales tax groups, item tax groups and customer TRNs determine the VAT category and amounts that land in each PINT AE field.
Structured e-invoicing
In Finance and Supply Chain Management, Electronic Reporting (ER) configurations and the Electronic invoicing service turn posted invoices into structured XML.
Validation
Mandatory fields, tax categories and number sequences can be checked before posting, so the ASP rejects fewer documents.
Status and reporting
Two-way communication returns accepted or rejected statuses to the ERP, giving finance one place to track every document.
ASP integration
An ASP connector or API carries invoices out of Dynamics 365 and onto the Peppol network as the last-mile link.
Archiving
Submitted XML and responses need to be retained and retrievable for audit, either in the ERP, the ASP platform or both.
Dynamics 365 Finance, Business Central and legacy versions compared
"Dynamics 365" covers very different products, and the route to PINT AE depends on which one you run. Microsoft has announced built-in UAE e-invoicing for Dynamics 365 Finance. It covers B2B and B2G invoices and credit notes from sales orders, free text invoices and project invoices, sent in PINT XML over Peppol with an ASP as the last-mile connector. Its release timing has shifted between update waves, so confirm the current status on Microsoft's roadmap for your exact version before you plan around it.
| Area | D365 Finance / SCM (cloud) | D365 Business Central | AX 2012, NAV or on-premises |
|---|---|---|---|
| E-invoicing engine | Electronic invoicing service with ER configurations | E-Documents framework | None built in |
| UAE PINT AE output | Microsoft-announced UAE functionality, or an ASP connector | Extension or ASP connector mapped to the 51 mandatory fields | Middleware or ASP integration built around the database |
| Cloud dependency | Service runs in Azure, including a UAE geography | SaaS, connector-based | The Electronic invoicing service does not support on-premises |
| Typical effort | Configure, map, test | Extend, map, test | Integrate, or upgrade first |
| Main risk | Waiting on roadmap features with a fixed deadline | Customisations that break on updates | Fragile integrations on unsupported versions |
If you are still on AX 2012 or NAV, the mandate is a good moment to weigh a short-term connector against moving the ERP to the cloud. A connector bought only to meet the 2027 deadline may cost more over three years than the upgrade it postpones.
Self-check
PINT AE readiness checklist for Dynamics 365
Run through this with finance and IT in the same room. Any item you cannot answer with confidence becomes a work item before your ASP deadline.
- ERP version: on a supported, current Dynamics 365 release
- ERP version: cloud or on-premises status confirmed
- Master data: valid TRNs on every UAE customer and vendor
- Master data: addresses, emirates and legal names cleaned
- Tax configuration: every VAT scenario mapped to a PINT AE tax category
- Tax configuration: zero-rated, exempt and reverse-charge cases tested
- Invoice formats: sales, free text, project invoices and credit notes covered
- Invoice formats: units of measure mapped to recognised codes
- Integrations: ASP shortlisted, appointed and connected
- Integrations: third-party billing systems feeding the same flow
- Workflows: owners for rejected invoices and status monitoring
- Workflows: archiving and audit retrieval agreed
Common implementation mistakes, and what good looks like
- Treating e-invoicing as a finance project and bringing IT in late.
- Choosing an ASP on price before checking how it connects to your Dynamics version.
- Mapping only the standard tax invoice and forgetting credit notes and project billing.
- Assuming the ASP will fix bad customer TRNs and missing fields.
- Counting the ASP appointment as the finish line instead of the start of testing.
- A joint finance, tax and IT owner group from the first workshop.
- ASP selection driven by integration fit, support model and Peppol certification.
- Every invoice type and VAT scenario tested end to end before go-live.
- Master data cleaned in the ERP, where the error starts.
- Testing time reserved between ASP appointment and the go-live date.
After go-live: system failures and the two-business-day rule
Most guides end at go-live, but the mandate keeps applying afterwards. Under Cabinet Decision No. 106 of 2025, a "system failure" includes ASP outages, network disruptions and software faults. Any failure that stops you issuing or receiving e-invoices must be reported to the FTA within two business days.
In practice, someone has to watch the connector, the ASP status feed and the ERP job queue, and must know who files the notice. That is an IT operations duty as much as a tax one. Monitoring, alerting and escalation should be part of your managed support arrangement. Because invoice data now leaves the ERP for external platforms, it is also worth checking where your ASP stores and processes that data against UAE data localization and privacy rules.
Penalties
What non-compliance costs
- Failure to implement on time, including not appointing an ASP by the deadline: AED 5,000 for each month of delay or part of a month.
- Late e-invoices: AED 100 per invoice, capped at AED 5,000 per month.
- Late electronic credit notes: AED 100 per credit note, capped at AED 5,000 per month.
- Late notice of a system failure: AED 1,000 for each day of delay.
Preparation
Key steps to prepare
Assess your current state
Confirm your Dynamics version and revenue cohort, then measure current invoices against the 51 mandatory fields.
Fix data and tax setup
Clean TRNs and addresses, then map every VAT scenario and unit of measure to its PINT AE value.
Choose and appoint an ASP
Shortlist accredited, Peppol-certified providers that fit your Dynamics edition, and appoint before your deadline.
Build, test, then go live
Connect the ERP, test every invoice type with real scenarios, train staff on rejections and set up monitoring.
Why starting early pays off
Better ASP choice
ASP capacity is finite. Early movers compare integration fit and pricing instead of signing whatever is still available in December.
Real testing time
The deadline extension gave more time to appoint an ASP, not to build. Starting now protects the weeks needed for end-to-end testing.
Cleaner finance data
Master data and tax fixes made for PINT AE also improve VAT returns, reconciliations and reporting long after go-live.
Frequently asked questions
What are the PINT AE requirements in simple terms?
Every in-scope invoice and credit note must be issued as structured XML that follows the PINT AE data model, including the 51 mandatory fields for a tax invoice. It must be sent through an Accredited Service Provider over the Peppol network, with tax data reported to the FTA. PDFs and paper invoices are not compliant once your phase goes live.
Does the mandate apply if my business is not VAT registered?
VAT registration is not the trigger. The mandate applies to persons conducting business in the UAE for in-scope B2B and B2G transactions, subject to specific exclusions. A non-registered business issuing such invoices should confirm its position with a tax adviser.
Can Dynamics 365 send e-invoices directly to the FTA?
No. Dynamics 365 produces the invoice data, but transmission must go through an Accredited Service Provider. The ASP validates the invoice, delivers it to the buyer's ASP over Peppol and reports the tax data to the FTA. Dynamics 365 is not an ASP.
Does Business Central support PINT AE out of the box?
Business Central includes an E-Documents framework for electronic document exchange. For UAE PINT AE, businesses currently rely on an extension or an ASP connector that maps invoice data to the mandatory fields. Check the current localisation status for your version before choosing a route.
We run Dynamics AX 2012 or NAV on-premises. Can we still comply?
Yes, but not through Microsoft's Electronic invoicing service, which does not support on-premises deployments. You would need middleware or an ASP integration built around your existing system, or an upgrade to a cloud version of Dynamics 365. Compare the cost of both over several years rather than only against the deadline.
What happens if our ASP or ERP goes down after go-live?
An outage that prevents you from issuing or receiving e-invoices counts as a system failure. It must be reported to the FTA within two business days, and late notification carries a penalty of AED 1,000 per day of delay. Monitoring and a clear escalation owner should be in place before go-live.
When does my business need to appoint an ASP?
Businesses with annual revenue of AED 50 million or more must appoint an ASP by 30 October 2026 and go live on 1 January 2027. Businesses below that threshold and in-scope government entities must appoint an ASP by 31 March 2027. Those businesses go live on 1 July 2027, and government entities on 1 October 2027.
Not sure where your Dynamics 365 stands?
Rounak Computers has supported UAE businesses from Bur Dubai since 2004 as a Microsoft Gold partner with certified in-house engineers. We can review your ERP version, master data, tax configuration and integrations against PINT AE, then support the implementation and the monitoring after go-live.
