TECHNICAL
UAE E-Invoicing Implementation Roadmap: Step-by-Step from Zero to Go-Live
The UAE Ministry of Finance has published a clear four-step process for implementing e-invoicing. This article follows that official process, translates each step into practical tasks, and gives you realistic timelines based on what businesses have experienced in Saudi Arabia, India, Italy, and Singapore. If you are starting now, this is where to begin.
reading time: 13 min
SOURCES: MOF OFFICIAL PUBLICATIONS
may 2026
aiverix research
Most finance leaders who need to implement UAE e-invoicing know they need to do it — but they are not sure exactly what the process looks like, how long it takes, or who is responsible for what. The UAE Ministry of Finance has published the answer in the official Electronic Invoicing Guidelines. Section 9 and Appendix 1 of that document describe a four-step implementation process: understand the requirements, select an ASP, test, and go live. This article follows that official process step by step, fills in the practical details that the guidelines summarise, and gives you a realistic view of the timelines based on what actually happens during implementation — not what looks good in a brochure.
4
Official implementation steps from the FTA Guidelines
2–6
Weeks for ERP integration — depending on your system
JULY 31
2026 — last date to appoint ASP for Wave 1 businesses
JULY 1
2026 — voluntary pilot opens, no penalties during this period
“
OFFICIAL SOURCE:
UAE Electronic Invoicing Guidelines V1.0, Section 9 and Appendix 1 — Ministry of Finance, 23 February 2026
UAE Electronic Invoicing Guidelines V1.0, Section 9 and Appendix 1 — Ministry of Finance, 23 February 2026
Before You Start: Know Your Deadline
The implementation process is the same for every business — but your urgency depends on which wave you are in. The two key dates for Wave 1 businesses are October 30, 2026 (ASP appointment deadline) and January 1, 2027 (mandatory go-live). If your annual revenue is below AED 50 million, your deadlines are March 31, 2027 and July 1, 2027.
There is also a voluntary pilot period that opens on July 1, 2026. Any business — regardless of revenue — can go live voluntarily from that date. No penalties apply during the voluntary period. This makes it the ideal window to complete your full implementation and work through any technical issues before your mandatory date arrives.
There is also a voluntary pilot period that opens on July 1, 2026. Any business — regardless of revenue — can go live voluntarily from that date. No penalties apply during the voluntary period. This makes it the ideal window to complete your full implementation and work through any technical issues before your mandatory date arrives.
Now — June 2026
Preparation window
Preparation window
Best time to complete Steps 1 and 2 — understand requirements, select and appoint your ASP. Begin ERP integration work.
July 1, 2026
Voluntary pilot opens
Voluntary pilot opens
Go live and test with real invoices — no penalties for any business during this period. Best window to complete Steps 3 and 4.
October 30, 2026
Wave 1 ASP appointment deadline
Wave 1 ASP appointment deadline
Revenue ≥ AED 50M — signed contract AND EmaraTax onboarding completed. Missing this date: AED 5,000/month fine starts immediately.
January 1, 2027
Wave 1 mandatory go-live
Wave 1 mandatory go-live
All B2B and B2G invoices must be transmitted through EIS. Non-compliant invoices are legally void.
March 31, 2027
Wave 2 ASP appointment deadline
Wave 2 ASP appointment deadline
Revenue < AED 50M — signed contract and EmaraTax onboarding completed.
July 1, 2027
Wave 2 mandatory go-live
Wave 2 mandatory go-live
All remaining businesses with B2B or B2G transactions must be live.
Step 1: Understand the Requirements
1. Understand the Electronic Invoicing Requirements
ESTIMATED TIME: 1–2 WEEKS · WHO DOES IT: CFO, FINANCE MANAGER, IT LEAD
Before you can make good decisions about implementation, your team needs to understand three things: what the law requires, when it applies to your business, and what changes are needed in your current systems. This step is about building that understanding — not about starting technical work.
- Task 1A – confirm your wave and deadlinesReview your most recent annual revenue figures. If revenue is AED 50 million or above, you are Wave 1. If below, you are Wave 2. If you are part of a VAT group, each entity in the group is assessed individually — the group representative’s revenue does not determine your wave.
- Task 1B – map your transaction typesGo through your business and identify which of your transactions involve other businesses or government entities. These are your in-scope transactions. Also identify if any of your transactions involve free zones, exports, deemed supply, agent billing, or continuous supply arrangements — these require additional data fields on the invoice (see the invoice transaction type code in Article 2 of this series).
- Task 1C – review your current invoicing systemLook at how invoices are currently generated in your ERP or accounting system. The key questions are: can your system output the 51 mandatory data fields? Does your system currently capture buyer TRNs and Peppol IDs? Are your customer master records complete and accurate? Most businesses find gaps at this stage — and that is good. Finding gaps now is cheap. Finding them after go-live is expensive.
- Task 1D – confirm your TIN statusYour Tax Identification Number (TIN) is the first 10 digits of your TRN. If you are registered for VAT or Corporate Tax with the FTA, you already have a TIN. If you are not registered for any tax type but are in scope for e-invoicing, you must register with the FTA to get a TIN before you can proceed with ASP onboarding. This registration is done through the EmaraTax portal.
The output of Step 1 is a clear picture of your scope, your deadlines, your transaction types, and the gaps between your current systems and the 51 mandatory field requirements.
Step 2: Select and Appoint Your ASP
2. Select an ASP and Complete Onboarding via EmaraTax
ESTIMATED TIME: 2–4 WEEKS · WHO DOES IT: CFO DECISION + FINANCE/IT FOR ONBOARDING
Your Accredited Service Provider (ASP) is the company that connects your business to the UAE Peppol network, converts your invoice data into PINT AE XML format, and transmits invoices on your behalf. You must appoint exactly one ASP — one ASP handles both your outgoing invoices (accounts receivable) and incoming invoices (accounts payable). You cannot use different ASPs for different purposes.
The official list of FTA-accredited ASPs is available on the Ministry of Finance website and within the EmaraTax portal. Only providers on this list are legally authorised to transmit UAE e-invoices. A provider that is "in the process of accreditation" or "applying for accreditation" is not yet authorised and cannot legally transmit invoices on your behalf from your mandatory date.
The official list of FTA-accredited ASPs is available on the Ministry of Finance website and within the EmaraTax portal. Only providers on this list are legally authorised to transmit UAE e-invoices. A provider that is "in the process of accreditation" or "applying for accreditation" is not yet authorised and cannot legally transmit invoices on your behalf from your mandatory date.
- Task 2A – evaluate and select your ASPWhen evaluating providers, the key questions are: Is FTA accreditation confirmed? Are they a certified Peppol Access Point? Have they run live e-invoicing deployments in comparable markets such as Saudi Arabia’s ZATCA? What is the realistic integration timeline for your specific ERP? What is their SLA for system downtime and invoice rejection resolution? What does the compliance dashboard look like — can your CFO and finance team see real-time invoice status?
- Task 2B – sign the contractOnce you have selected your ASP, finalise all commercial and contractual obligations. The signed contract is a prerequisite for the EmaraTax onboarding step. For Wave 1 businesses, this contract must be signed and the EmaraTax onboarding completed before July 31, 2026.
- Task 2C – onboard via EmaraTaxThe formal ASP appointment is not complete until it is registered in the FTA’s EmaraTax system. This process is initiated by you — not by your ASP. Log into EmaraTax, navigate to the E-INVOICING section, find your ASP in the official list, select them, and click "Proceed to ASP." You will be redirected to your ASP’s portal to complete the onboarding process. Upon completion, your ASP will provide you with your Peppol Participant Identifier — this is your address on the UAE Peppol network.
A note on tax groups: if your business is part of a VAT group, each entity in the group must be onboarded separately. Each entity has its own TIN and its own Peppol Participant Identifier. Different group members can use different ASPs if they choose.
WHAT HAPPENS DURING EMARATAX ONBOARDING
When you click "Proceed to ASP" in EmaraTax, you will see a confirmation message: "You are about to leave the Federal Tax Authority EmaraTax system. Do you want to proceed?" Once you confirm, you are redirected to your ASP's portal. Your ASP then completes the technical onboarding — connecting your account, verifying your TIN, and registering your Peppol Participant Identifier on the network.
Your Peppol Participant Identifier will be in the format 0235: followed by your 10-digit TIN. For example: 0235:1234567890. Once this identifier is registered, you have an address on the UAE Peppol network and are technically ready to exchange invoices.
When you click "Proceed to ASP" in EmaraTax, you will see a confirmation message: "You are about to leave the Federal Tax Authority EmaraTax system. Do you want to proceed?" Once you confirm, you are redirected to your ASP's portal. Your ASP then completes the technical onboarding — connecting your account, verifying your TIN, and registering your Peppol Participant Identifier on the network.
Your Peppol Participant Identifier will be in the format 0235: followed by your 10-digit TIN. For example: 0235:1234567890. Once this identifier is registered, you have an address on the UAE Peppol network and are technically ready to exchange invoices.
Step 3: Test Electronic Invoice Exchange and Reporting
3. Test End-to-End Invoice Exchange and Tax Data Reporting
ESTIMATED TIME: 3–6 WEEKS · WHO DOES IT: FINANCE TEAM + IT + ASP TECHNICAL TEAM
Testing is the step that separates businesses that go live cleanly from those that face their first wave of rejections on their mandatory date. The purpose of testing is to find and fix problems before they become compliance issues. The voluntary pilot period — which opens July 1, 2026 — is the ideal environment for this step, because any errors during the pilot carry no penalty risk.
- Task 3A – agree on how invoice data will be transmitted to your ASPYour ASP connects to your ERP through one of several methods: REST API (for modern cloud ERP systems like SAP Business One, Oracle, MS Dynamics, Odoo), SFTP file transfer, web portal manual entry, or CSV/XML file upload. The right method depends on your ERP and your invoice volume. Your ASP will discuss this with you during implementation scoping. Standard API integration for a modern ERP typically takes 2−4 weeks. Custom or legacy ERP integrations can take up to 30 business days.
- Task 3B – test the full end-to-end processThe official guidelines specify exactly what must be tested. You need to confirm six things: first, that your ERP can transmit invoice data to your ASP correctly; second, that your ASP converts and transmits the invoice to the buyer’s ASP correctly; third, that you receive a confirmation message from your ASP about the success or failure of the transmission; fourth, that you can receive an incoming electronic invoice from a supplier through your ASP; fifth, that your ASP reports the required tax data to the FTA (Corner 5); and sixth, that you receive confirmation from your ASP about the success of that tax data reporting. All six must work before go-live.
- Task 3C – tens with real transaction types from your businessDo not only test a single standard invoice. Test every transaction type your business issues — including any that involve free zones, exports, continuous supply, or other special scenarios. These require the invoice transaction type code flag string to be set correctly, and errors in this field are not always caught in basic testing.
- Task 3D – validate buyer data qualityDuring testing, transmit invoices to a sample of your actual customers. Check whether buyer TRNs are valid, whether Peppol IDs route correctly, and whether any customer records contain address or name data that fails validation. Correct all issues in your ERP customer master before go-live — not after.
Testing is not a checkbox activity. It is a debugging process. Every market that has implemented e-invoicing — Saudi Arabia, India, Italy, Singapore — has seen businesses discover data quality problems during testing that they had no idea existed. The businesses that discovered these problems during testing fixed them at low cost. The businesses that discovered them after go-live paid much more in rejected invoices, delayed payments, and emergency remediation.
THE MOST COMMON TEST FAILURES — BASED ON GLOBAR EXPERIENCE
Buyer TRN invalid or missing. The TRN in your ERP customer master does not match the FTA’s official record, or was never captured. This affects field 24 and causes immediate rejection.
Invoice transaction type code incorrect. The 8-character flag string is all zeros when it should have a 1 in the export or free zone position — or vice versa. This affects how the FTA classifies the transaction.
Legal name mismatch. Your seller name in field 10 does not exactly match the name on your trade licence. Common with businesses that use shortened trading names.
AED conversion missing. For non-AED invoices, fields 48 and 49 (VAT line amount and invoice line amount in AED) are not populated because the ERP was not configured to calculate them.
Rounding errors. ERP applies rounding at line-item level instead of invoice total level, creating a mismatch between the sum of lines and the stated total.
Buyer TRN invalid or missing. The TRN in your ERP customer master does not match the FTA’s official record, or was never captured. This affects field 24 and causes immediate rejection.
Invoice transaction type code incorrect. The 8-character flag string is all zeros when it should have a 1 in the export or free zone position — or vice versa. This affects how the FTA classifies the transaction.
Legal name mismatch. Your seller name in field 10 does not exactly match the name on your trade licence. Common with businesses that use shortened trading names.
AED conversion missing. For non-AED invoices, fields 48 and 49 (VAT line amount and invoice line amount in AED) are not populated because the ERP was not configured to calculate them.
Rounding errors. ERP applies rounding at line-item level instead of invoice total level, creating a mismatch between the sum of lines and the stated total.
Step 4: Go Live
4. Go Live with Electronic Invoicing
ONGOING · WHO MANAGES IT: FINANCE TEAM WITH ASP SUPPORT
Going live means your ERP starts transmitting all in-scope invoices through your ASP from your agreed date. For businesses using the voluntary pilot period, this can happen any time from July 1, 2026 with no penalty risk. For Wave 1 businesses that have not gone live voluntarily, the mandatory go-live date is January 1, 2027.
- Task 4A – establish a governance model with your ASP before go-liveBefore your first live invoice is transmitted, agree with your ASP on exactly what happens when something goes wrong. Specifically: who is the named contact at your ASP for invoice issues? What is the response time for a rejection notification? What is the process for correcting and retransmitting a failed invoice? What happens if your ASP’s system has downtime? These answers should be in your contract, but they should also be understood by the people in your finance team who will handle day-to-day operations.
- Task 4B – train your finance teamYour finance team does not need to become XML experts. But they need to know three things: how to check invoice transmission status in the compliance dashboard, what to do when they receive a rejection notification, and who to call at the ASP when they cannot resolve an issue themselves. This training is typically one or two hours, not a week-long course.
- Task 4C – monitor actively during the first monthThe first four weeks after go-live are the highest-risk period. New edge cases will appear — transaction types you did not test, customers with unexpected data issues, ERP configurations that behave differently in production than in testing. Assign someone in your finance team to review the compliance dashboard daily during the first month and escalate any rejection patterns to your ASP immediately.
Ongoing: Managing Changes After Go-Live
Implementation is not a one-time project. After you go live, your e-invoicing setup needs to be maintained as your business circumstances change and as the UAE regulatory framework evolves.
If your business circumstances change after go-live — you register for VAT, you join or leave a VAT group, you deregister from a tax type, or you change your legal structure — you must update your ASP promptly using the reverification or offboarding processes in EmaraTax. Your ASP cannot know about these changes automatically. Outdated information in EmaraTax can cause your invoices to be routed to incorrect endpoints or fail validation.
The Ministry of Finance will update the PINT AE technical specifications over time as the system matures. Your ASP is responsible for staying current with these updates and ensuring the latest version is always used when transmitting invoices. This is one of the most important ongoing services your ASP provides — regulatory maintenance is not a one-time setup cost, it is a continuous obligation.
If your business circumstances change after go-live — you register for VAT, you join or leave a VAT group, you deregister from a tax type, or you change your legal structure — you must update your ASP promptly using the reverification or offboarding processes in EmaraTax. Your ASP cannot know about these changes automatically. Outdated information in EmaraTax can cause your invoices to be routed to incorrect endpoints or fail validation.
The Ministry of Finance will update the PINT AE technical specifications over time as the system matures. Your ASP is responsible for staying current with these updates and ensuring the latest version is always used when transmitting invoices. This is one of the most important ongoing services your ASP provides — regulatory maintenance is not a one-time setup cost, it is a continuous obligation.
Realistic Implementation Timelines by ERP Type
The Official Readiness Checklist
The UAE Electronic Invoicing Guidelines include an official readiness checklist in Appendix 2. Here it is in full, formatted as a practical pre-go-live checklist for your finance team.
Ready to go live with Electronic Invoicing as per the roll-out plan
Finance team trained on compliance dashboard, rejection handling, and escalation process
Established a governance model with your ASP for error resolution
Completed end-to-end testing of invoice exchange and tax data reporting with your ASP
Completed integration between your ERP and your ASP's system
Completed all necessary ERP changes to generate the required data fields
Agreed with your ASP on data hosting and security requirements
Agreed with your ASP on how you will receive confirmation and rejection notifications
Agreed with your ASP on how invoice data will be transmitted — API, SFTP, or portal
Obtained your Peppol Participant Identifier (0235: + 10-digit TIN) via your ASP
Completed formal ASP onboarding via EmaraTax
Registered with the FTA and obtained your TIN (if not already registered for a tax type)
Created a profile on your ASP's system
Selected an FTA-accredited ASP and completed all contractual obligations
Identified the 51 mandatory data fields required for your invoice types and confirmed your ERP can produce them
Reviewed Cabinet Decision No. 106 of 2025 — the penalty framework
Wave 1 (≥ AED 50M): July 31, 2026 ASP / January 1, 2027 live · Wave 2 (< AED 50M): March 31, 2027 ASP / July 1, 2027 live
Identified your mandatory go-live date and ASP appointment deadline based on your revenue
Understood MD No. 243 of 2025 and the changes to UAE VAT and Tax Procedures law arising from e-invoicing
The Most Important Thing to Understand About This Process
The four steps described in this article are straightforward. The reason businesses run into trouble is not that the process is complicated — it is that they start too late and then have no room to absorb the delays and discoveries that are a normal part of every implementation.
Data quality issues in the customer master always take longer to fix than expected. ERP configurations always surface edge cases that were not anticipated. Testing always finds at least one thing that needs to be corrected before go-live. None of this is unusual or alarming — it is simply the reality of any system integration project. The businesses that manage it well are the ones that gave themselves enough time.
For Wave 1 businesses, the ideal sequence is: appoint your ASP by June 2026, complete integration by late July, run testing throughout August and September in the voluntary pilot period, and go live in October or November — giving yourself a two-month buffer before the January 1, 2027 mandatory date. That is a comfortable, well-managed implementation. The alternative — starting in October and rushing to January — is possible, but it is the France case study scenario: the same outcome at four times the cost and twice the stress.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point. Standard implementation takes 2−4 weeks for modern ERP systems. We conduct a no-cost compliance assessment that gives you a specific, realistic timeline for your ERP environment — not a general estimate. Request yours at aiverix.ae.
Data quality issues in the customer master always take longer to fix than expected. ERP configurations always surface edge cases that were not anticipated. Testing always finds at least one thing that needs to be corrected before go-live. None of this is unusual or alarming — it is simply the reality of any system integration project. The businesses that manage it well are the ones that gave themselves enough time.
For Wave 1 businesses, the ideal sequence is: appoint your ASP by June 2026, complete integration by late July, run testing throughout August and September in the voluntary pilot period, and go live in October or November — giving yourself a two-month buffer before the January 1, 2027 mandatory date. That is a comfortable, well-managed implementation. The alternative — starting in October and rushing to January — is possible, but it is the France case study scenario: the same outcome at four times the cost and twice the stress.
Aiverix is an FTA-accredited Accredited Service Provider and certified Peppol Access Point. Standard implementation takes 2−4 weeks for modern ERP systems. We conduct a no-cost compliance assessment that gives you a specific, realistic timeline for your ERP environment — not a general estimate. Request yours at aiverix.ae.