Section 9 of the UAE Electronic Invoicing Guidelines V1.1 sets out the structured process that every Person or Government Entity subject to the mandate must follow before going live. The process moves through four sequential steps, each with specific sub-tasks. This article summarises the framework; the full step-by-step detail is in Appendix 1 of the Guidelines.
The Four Steps
Step 1: Understand Electronic Invoicing Requirements
Before any system work begins, the Person or Government Entity must understand the legislative changes introduced across the Tax Procedures Law, VAT Decree-Law, and VAT Executive Regulation. This means reading MD No. 243 of 2025 (scope of application), MD No. 244 of 2025 (phased implementation plan), and CD No. 106 of 2025 (violations and penalties) and identifying when the mandatory implementation date applies to the specific entity.
A gap analysis of current accounting, ERP, and invoicing systems against PINT-AE requirements is required at this stage — not deferred until the ASP selection is complete. The gap analysis determines which invoice categories will be required, which data fields the system must generate, and what data migration or master data remediation is necessary before go-live.
Step 2: Select and Onboard with an ASP
The Ministry of Finance publishes the list of Accredited Service Providers (ASPs) on its website. Each Person or Government Entity must select one ASP to handle both sending (accounts receivable) and receiving (accounts payable) Electronic Invoices — not a different ASP for each direction.
Onboarding is initiated by the entity itself via the FTA's EmaraTax portal — not by the ASP. The Account Admin of the Taxable Person must access the E-Invoicing tile in EmaraTax, select the required ASP, and proceed to that ASP's portal to complete onboarding. A Peppol participant identifier is obtained through this process. The ASP contract must be finalised and all commercial obligations fulfilled before onboarding commences.
Each member of a Tax Group must onboard individually. Each group member has its own TIN and may onboard with a different ASP from other group members.
Step 3: Test Electronic Invoice Exchange and Reporting
Before go-live, the Person or Government Entity must agree with its ASP on the technical approach for transmitting invoice data, confirm that its systems can generate and transmit that data to the ASP's interface, and run end-to-end tests covering the exchange and reporting of Electronic Invoices across all transaction types and scenarios applicable to its business.
Testing must cover the specific Electronic Invoice categories relevant to the entity — electronic Tax Invoices, Commercial Invoices, self-billed invoices, and electronic Credit Notes as applicable — as well as any of the eight scenarios (Free Zone, deemed supply, margin scheme, summary invoice, continuous supply, agent billing, e-commerce, exports) that apply to its transactions.
Step 4: Go Live with Electronic Invoicing
At go-live, roles and responsibilities between the entity and its ASP must be agreed for ongoing transmission oversight and error resolution. The FTA's 5-Corner model means that transmission errors — whether at the Access Point layer or the FTA's reporting layer — need a defined escalation path with the ASP so that failed invoices are remediated promptly and not left unreported.
Ongoing: Managing Changes
Electronic Invoicing obligations do not end at go-live. The Guidelines specify that entities must keep their ASP informed of any changes in circumstances using the reverification or offboarding processes in EmaraTax, and must follow the governance arrangements agreed with their ASP to handle those changes systematically.
Changes that trigger reverification or offboarding include changes to trade licence status, ASP switching, corporate restructuring, and changes to the scope of transactions covered. The Guidelines do not treat these as administrative details — they are part of the compliance framework under MD No. 243 of 2025.
What Practitioners Should Note
The four-step framework places the initiation of each step with the Person or Government Entity, not the ASP. The ASP is a technical intermediary; the compliance obligation and the timeline risk sit with the entity. Initiating onboarding late — after a contract is signed but without allowing time for testing — is one of the most common implementation failure modes in phased mandate rollouts. The Guidelines are explicit that the ASP onboarding process should be initiated via EmaraTax by the entity's Account Admin, which means EmaraTax access, user permissions, and TIN confirmation must all be in place before Step 2 can begin.