Short answer: UAE e-invoicing for Dynamics 365 Finance & Operations becomes mandatory on 1 January 2027 for companies with revenue of AED 50 million or more. So, with about six weeks left, the work is clear: confirm your ASP, fix your data, configure F&O, connect it to the ASP, test end to end, then cut over.
The deadline to appoint an Accredited Service Provider (ASP) was 30 October 2026, and it has passed. If you have not signed with an ASP yet, the penalty for late appointment is already running at AED 5,000 per month. Therefore, the first item on this checklist is not optional.
This guide is for finance directors and IT managers at UAE companies that run Dynamics 365 F&O and fall in Phase 1. It gives you a week-by-week plan for UAE e-invoicing for Dynamics 365, from mid-November to go-live. It also covers the dates and penalties that apply, and the mistakes we see most often. Companies below AED 50 million can use the same plan for their 1 July 2027 go-live.
UAE e-invoicing dates and penalties
The Ministry of Finance moved the Phase 1 ASP deadline from 31 July to 30 October 2026. However, the 1 January 2027 go-live did not move (Deloitte, MoF).
| Group | Appoint an ASP by | Go live by |
|---|---|---|
| Revenue of AED 50 million or more (Phase 1) | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million (Phase 2) | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
The penalties come from Cabinet Decision No. 106 of 2025:
| Violation | Penalty |
|---|---|
| Not implementing e-invoicing, or not appointing an ASP on time | AED 5,000 per month or part of a month |
| E-invoice not issued or sent on time | AED 100 per invoice, capped at AED 5,000 per month |
| E-credit note not issued or sent on time | AED 100 per credit note, capped at AED 5,000 per month |
| Not telling the FTA about a system failure on time | AED 1,000 per day |
| Not telling your ASP about changes to registered data on time | AED 1,000 per day |
How UAE e-invoicing for Dynamics 365 F&O works
In short, the UAE uses a five-corner Peppol model. Your F&O system creates the invoice, and your ASP validates it and sends it to your customer’s ASP. Meanwhile, the tax data goes to the FTA. We explain the model in detail in UAE e-invoicing explained.
For F&O, three things matter:
- The format is PINT AE. In other words, it is the UAE version of the Peppol International invoice. A standard tax invoice has 51 mandatory fields, including the seller’s and the buyer’s TRN.
- Microsoft covers the format, not the delivery. Microsoft has announced UAE e-invoicing for F&O, with general availability on 1 December 2026. It generates PINT AE invoices and credit notes from sales orders, free text invoices and project invoices. To run, it also needs the E-Invoicing add-in, Azure Key Vault and Blob Storage. Invoices then leave through a third-party “last mile” connector (Microsoft Learn). So you still need an ASP and a working connection to it.
- Timing is tight. E-invoices and credit notes must be issued and sent within 14 days of the transaction date. As a result, a rejected invoice that nobody fixes becomes a late invoice.
The 6-week go-live checklist
This checklist for UAE e-invoicing for Dynamics 365 runs from 16 November to 27 December. Each week ends with something you can check. Also, keep the last days of December free as a buffer, because many teams and ASPs run on holiday staffing.
Confirm scope and your ASP (week 1: 16–22 November)
- Sign with an ASP now if you have not. Late appointment costs AED 5,000 per month.
- List every UAE legal entity in F&O and confirm which ones fall in Phase 1.
- Then note the documents you issue: sales invoices, free text invoices, project invoices and credit notes.
- Choose how F&O will create the XML: Microsoft’s E-Invoicing add-in or Electronic Reporting configurations.
- Finally, agree the connection with your ASP (API or SFTP) and book its test environment.
Fix your data (week 2: 23–29 November)
- Check that every UAE customer has a valid TRN. The buyer’s TRN is mandatory on B2B invoices.
- Next, compare your current invoice data with the 51 mandatory PINT AE fields and list the gaps.
- Map your F&O sales tax codes to the UAE tax categories.
- Clean up addresses, units of measure and payment terms on customers and items.
- Finally, decide who owns master data fixes after go-live.
Configure F&O (week 3: 30 November–6 December)
- Install the E-Invoicing add-in once it is available, or import your Electronic Reporting configurations.
- Then set up Azure Key Vault and Blob Storage if you use Microsoft’s feature.
- Configure electronic document parameters in Accounts receivable and Project management.
- Add credit note reason codes and link credit notes to their original invoices.
- Finally, build the connection to your ASP’s test environment.
Test end to end with your ASP (week 4: 7–13 December)
- Send at least one of each document type through the ASP’s test environment.
- Also test a foreign-currency invoice and check the AED amounts.
- Force a few rejections, for example a missing TRN, and check that someone sees them.
- In addition, test your largest invoices, with many lines.
- Finally, record every fix in the configuration, not in manual workarounds.
Run user testing and train the team (week 5: 14–20 December)
- Let finance users post and send real-looking invoices in the test system.
- Write the rejection process: who fixes it, and how it gets resent within 14 days.
- Similarly, document the system-failure process, including how you notify the FTA on time.
- Also plan how incoming e-invoices from suppliers will reach Accounts payable.
- After that, train the people who post invoices and the people who fix rejections.
Prepare the cut-over (week 6: 21–27 December)
- First, move the configuration to production and connect to the ASP’s production environment.
- Then hold a go/no-go meeting with finance, IT and the ASP.
- Agree what happens to invoices posted on 31 December and 1 January.
- Name a support team for the first two weeks of January, holidays included.
- On 1 January, send the first live invoice and confirm it reached your customer.
Common mistakes in the last six weeks
These are the problems we see most often in UAE e-invoicing for Dynamics 365 projects close to go-live:
- Treating Microsoft’s feature as the whole solution. It creates the PINT AE file. However, the ASP contract, the connection and the rejection handling are still yours to set up.
- Missing customer TRNs. In fact, this is the most common reason for rejections. So fix the customer master in week 2, not after go-live.
- Customizations on invoice posting. If earlier partners changed how invoices post, the e-invoice may miss fields or break. Review those customizations before you test.
- No owner for rejections. After 14 days, every rejected invoice still waiting can cost AED 100.
- Testing only the happy path. Test credit notes, foreign currency and large invoices, because those fail most often.
- A go-live with no support. 1 January falls in a holiday period, so name the support team in advance.
Frequently asked questions
We missed the 30 October ASP deadline. What now?
Sign with an ASP immediately. The penalty for late appointment is AED 5,000 for each month or part of a month, so every month you wait adds to it. Then follow this checklist from week 1.
Is Microsoft’s UAE e-invoicing feature enough on its own?
No. It generates compliant PINT AE invoices inside F&O. Even so, the law requires an Accredited Service Provider to exchange them and report to the FTA. You still need an ASP and a tested connection.
Should we connect to the ASP by API or by SFTP?
Both can work. An API gives faster status feedback, while SFTP is simpler and many ASPs support it. If you choose SFTP, our free SFTP Connector can send the e-invoice files from F&O to your ASP’s SFTP folders. It does not read the ASP’s acknowledgements or rejections, so either way, make sure someone sees them.
What happens if our system or the ASP is down?
You must tell the FTA about a system failure within the set time, or face AED 1,000 per day. So write this procedure before go-live, not during an outage.
We are below AED 50 million. Does this apply to us?
Yes, later. You must appoint an ASP by 31 March 2027 and go live by 1 July 2027. The same checklist for UAE e-invoicing for Dynamics 365 applies; however, start it about three months earlier.
Next step
SysBrilliance connects Dynamics 365 F&O to your ASP using Electronic Reporting, not custom code, so the setup stays upgrade-safe. In addition, we have already delivered Peppol e-invoicing in F&O for customers in France and Belgium. If you are short on time, we can review your data, configure F&O and run the end-to-end tests with your ASP. Book a 30-minute call and we will tell you honestly what you can still do before 1 January.