So you’ve read through the UAE eInvoicing guidelines, you understand the scope, the timeline, the scenarios, and the penalties. Now comes the most important question of all: “What do I actually do next?”

This blog is your practical, no-jargon action guide – built directly from the FTA’s official readiness framework, appendices, and roles & responsibilities documentation. Whether you’re a large business racing towards January 2027 or a smaller business with more runway, this checklist gives you a clear path from where you are today to full eInvoicing compliance.

The 4-Stage Readiness Journey

The FTA’s official guidelines break down the implementation journey into 4 clear stages, followed by an ongoing management phase. Let’s walk through each one in detail.

Stage 1: Understand Your eInvoicing Requirements

Before you touch any technology or contact any ASP, you need to build internal awareness and clarity. This stage is about making sure the right people in your organisation understand what is coming, what it means for them, and what needs to change.

What to do:

• Review the legal framework – Familiarise yourself with Ministerial Decision No. 243 of 2025 (the core eInvoicing obligations), MD No. 244 of 2025 (the implementation timeline), and Cabinet Decision No. 106 of 2025 (the penalties). These are the three documents that govern everything.
• Identify your mandatory go-live date – Based on your revenue (≥ AED 50M = Jan 1, 2027; < AED 50M = Jul 1, 2027), confirm exactly when your obligations become enforceable and work backwards from there.
• Map your transaction types – Which of your transactions are B2B or B2G? Do you have Free Zone customers, export transactions, continuous supply contracts, or margin scheme products? Identify all 8 scenario types that apply to your business.
• Assess your current invoicing system – Is your ERP or accounting system capable of generating XML-format invoice data? Can it capture all mandatory fields? Does it support the 8 scenario flags? Document every gap between your current capability and what eInvoicing requires.
• Build your internal project team – eInvoicing is not just an IT project. It touches finance, tax, operations, procurement, and sales. Assign a project owner and make sure all departments understand their role.

Who is involved at this stage:

• CFO / Finance Director (ownership and budget)
• Tax team (compliance obligations mapping)
• IT / ERP team (system gap assessment)
• Operations / procurement (process changes)

Stage 2: Select and Onboard Your ASP

Once you understand your requirements, it’s time to find the right technology partner – your Accredited Service Provider (ASP). This is arguably the most critical decision in the entire journey.

What to do:

• Shortlist 3 ASPs using the FTA’s official selection criteria (experience, integration capability, security, support SLAs, pricing, scalability – covered in detail in our Blog 1).
• Run a formal RFP process – Share your ERP details, transaction volumes, scenario types, and timeline with shortlisted ASPs. Ask them to demonstrate a live integration with your system.
• Evaluate integration depth – Does the ASP have a native connector for your ERP (SAP, Oracle, Microsoft Dynamics, Tally, Zoho, etc.)? Will they support your specific scenarios (Free Zone, exports, continuous supply)?
• Check the contractual terms carefully – Ensure the contract includes: defined SLAs for uptime and support response times, the mandatory 100 free invoices per year clause, data residency commitments, security certifications, and clear error resolution accountability.
• Onboard via EmaraTax – Critically, the onboarding process with your chosen ASP must be initiated by you (not the ASP) through EmaraTax, accessible via the FTA’s official website. This is the official channel through which your Peppol Participant Identifier is registered.
• Obtain your Peppol Participant Identifier — Your unique network address on the UAE eInvoicing system is formatted as 0235 followed by your 10-digit TIN (first 10 digits of your TRN). This is your “electronic address” on the Peppol network.

Key deadline reminder:

• Large businesses (≥ AED 50M): ASP must be appointed by July 31, 2026
• Smaller businesses and Government entities: March 31, 2027

Stage 3: Test Your eInvoicing Setup End-to-End

This is the stage that separates businesses that are genuinely ready from those that think they are ready. Testing is not optional – it is the only way to discover issues before they become compliance problems or business disruptions.

What to do:

• Agree on data transmission approach – How will your ERP send invoice data to your ASP? Via API? SFTP? Direct integration? Document the exact technical flow and ensure it is signed off by both your IT team and your ASP.
• Validate your mandatory fields – Run sample invoices through the ASP’s validation engine and confirm all 50+ mandatory fields are correctly populated. Pay special attention to:
  • TIN (first 10 digits of TRN) correctly mapped as seller identifier
  • Buyer electronic address and Peppol ID correctly captured
  • Unit of measure codes standardised across all product/service lines
  • All 8 scenario flags correctly set based on transaction type
• Test all your scenario types – Don’t just test standard B2B invoices. Test every scenario that applies to your business: Free Zone (with beneficiary), export (with predefined endpoint), credit notes, summary invoices, continuous supply – all of them.
• Test error handling – Deliberately submit an invoice with a missing field or incorrect format and observe how your ASP handles the rejection. Understand the error notification flow and how to resubmit corrected invoices.
• Do an end-to-end buyer test – If possible, arrange a test with one of your key buyers where you send a test Electronic Invoice through your ASP to their ASP and confirm receipt and confirmation messages flow correctly all the way through the 5-corner network.
• Test your data retention process – Confirm that invoices are being stored in a retrievable, reproducible format that meets the 5-year or 7-year retention requirements.

Stage 4: Go Live with eInvoicing

After successful testing, you’re ready to go live. But going live is not just pressing a button – it requires clear governance and active monitoring, especially in the early weeks.

What to do:

• Agree roles and responsibilities with your ASP – Who monitors invoice transmission success? Who owns error resolution? What’s the escalation path for system failures? What are the notification timelines for FTA reporting? Document all of this formally.
• Train your finance and AR/AP teams – Ensure they understand: how to identify failed invoices, how to trigger resubmission, how to handle buyer queries about eInvoice format, and what to do if the system goes down.
• Establish a system failure notification process – Remember: failing to notify the FTA of a system failure within the prescribed timeline triggers AED 1,000/day penalties. Have a clear internal escalation process ready from day one.
• Communicate with your buyers – Let your key customers know you are now live on eInvoicing. Share your Peppol Participant Identifier with them so they can receive your invoices correctly. During the transition period, consider also sharing a readable commercial invoice copy for buyers who haven’t implemented eInvoicing yet.
• Monitor your first 30 days closely – Track invoice success rates, rejection rates, confirmation message receipt, and FTA reporting confirmations. Address any patterns quickly.
• Go live voluntarily before your mandatory date – Ideally, you want to be live and stable for at least 3 months before your mandatory deadline. This gives you a real safety buffer.

Ongoing: Manage Changes

eInvoicing is not a “set and forget” system. After go-live, ongoing management is essential.

Key ongoing responsibilities:

• Keep your ASP updated – Any change in your company details (address, TRN, legal name, ownership) must be communicated to your ASP promptly via the EmaraTax reverification or offboarding process. Delays trigger AED 1,000/day penalties.
• Monitor regulatory updates – The Ministry of Finance may issue new Ministerial Decisions, add exclusion categories, or update technical specifications. Subscribe to FTA communications and work with your tax advisor to stay current.
• Review scenario changes – If your business expands into new markets, adds Free Zone customers, starts exporting, or changes its supply model, review your scenario flags and mandatory field requirements accordingly.
• Annual compliance review – Build eInvoicing into your annual tax compliance calendar. Review data retention, ASP performance, SLA adherence, and any regulatory updates at least once per year.

The Official FTA Readiness Checklist (From Appendix 2)

The FTA has published an official readiness checklist as part of the guidelines. Here are the key items every business should verify before go-live:

Legal and compliance readiness:

• Identified mandatory go-live date based on revenue
• Reviewed all relevant Ministerial Decisions and Cabinet Decisions
• Identified all transaction types and applicable scenarios
• Assessed VAT group or holding company specific requirements

Technical readiness:

• ERP/accounting system gap assessment completed
• ASP selected and contract signed
• Onboarded via EmaraTax and Peppol Participant ID obtained
• All mandatory fields mapped and validated in ERP
• 8 scenario flags configured correctly
• XML output tested and validated against PINT-AE specifications

Process readiness:

• Buyer Peppol identifiers collected for key customers
• AR and AP teams trained on eInvoicing workflows
• Error resolution and resubmission process documented
• System failure notification process established
• Data retention and archival process confirmed

Go-live readiness:

• End-to-end test completed with ASP
• Roles and responsibilities agreed with ASP in writing
• Voluntary go-live completed at least 3 months before mandatory date
• First 30-day monitoring plan in place

Roles and Responsibilities: Who Does What?

One of the most useful sections of the FTA guidelines is the clear breakdown of roles across all parties involved in eInvoicing:

FAQs

1) Where exactly do I go to onboard with my ASP?
Onboarding is initiated by you through EmaraTax – the FTA’s official online portal. You cannot simply sign a contract with an ASP and consider yourself onboarded. The formal registration through EmaraTax is the official step that assigns your Peppol Participant Identifier and registers you on the Central Register.

2) How long does the full implementation journey typically take?
For a well-prepared business with a reasonably modern ERP, allow 3 to 6 months from ASP selection to stable go-live. This includes integration development, testing, staff training, and buyer communication. Complex businesses (VAT groups, multiple scenarios, legacy systems) should budget 6 to 9 months.

3) Do we need to collect Peppol IDs from all our buyers before go-live?
Yes – for buyers who are already on the eInvoicing system, you need their Peppol Participant Identifier to deliver invoices to them correctly. This is your responsibility as the supplier. Build buyer Peppol ID collection into your standard customer onboarding and account management processes.

4) What if our ERP cannot generate XML format invoices?
Most ASPs can accept invoice data in various formats (CSV, JSON, ERP-native formats) and convert it to the required XML. However, the closer your ERP can get to structured data output, the smoother the integration. Work with your ASP to agree on the most practical data submission format for your setup.

5) Can we implement eInvoicing for some transaction types and not others?
No – once you are in the mandatory phase, eInvoicing applies to all your in-scope B2B and B2G transactions. You cannot cherry-pick which invoices to run through the system. This is why thorough scenario mapping in Stage 1 is so important – you need to be ready for all your transaction types, not just the simple ones.