Appendix 3 of the UAE Electronic Invoicing Guidelines V1.1 maps the specific responsibilities of each party in the 5-Corner model: the Ministry of Finance, the Federal Tax Authority, Persons and Government Entities (suppliers and buyers), Accredited Service Providers, and Peppol. The division is more consequential than it first appears. In a system where five actors process the same invoice data, clarity about who owns each obligation — and who is liable when it is not met — is the foundation of defensible compliance.
The Ministry of Finance
The Ministry holds the regulatory and standards-setting role. It establishes and enforces the laws governing the Electronic Invoicing System, develops and maintains the PINT-AE format and protocol standards, and grants or removes accreditation from Service Providers under Ministerial Decision No. 64 of 2025. The Ministry also carries the day-to-day coordination role with Peppol, ensuring that UAE-specific ASP obligations align with the latest PINT-AE specifications.
The regulatory ownership of the Ministry over the standard matters for enterprises. When the Ministry publishes updated guidance — as it did with the V1.1 Guidelines on 1 June 2026 — businesses and their ASPs are responsible for tracking those changes. The Ministry does not individually notify registrants of standard updates; awareness and adaptation are part of the ongoing compliance obligation.
The Federal Tax Authority
The FTA sits at Corner 5, receiving Tax Data reported by ASPs and using it for compliance monitoring and audit. Its operational responsibilities under Appendix 3 include facilitating the registration of Persons and the generation of TINs and TRNs, supporting the ASP accreditation process through testing, providing the EmaraTax platform through which businesses onboard with ASPs, and analysing invoice data for tax audits and fraud detection.
The FTA's data analysis role is worth noting in its practical implication. Corner 5 data is structured, machine-readable, and arrives in near-real time. The FTA's stated responsibility to analyse it for compliance purposes means that the quality of the data a business sends through its ASP — not just whether the invoice transmitted successfully — is a live compliance variable from day one of the mandate.
Persons and Government Entities
The Guidelines assign a substantial list of operational responsibilities to suppliers and buyers. These include: reviewing and understanding the Electronic Invoicing requirements; verifying company details in EmaraTax before onboarding; selecting an ASP and completing all contractual and commercial steps; completing ERP or accounting system changes; testing the full exchange and reporting cycle with the ASP; and ensuring that any changes in circumstances — joining or leaving a Tax Group, deregistering from VAT, closing the business — are promptly updated with the ASP.
One obligation that sits entirely with the business and is not delegatable to the ASP: ensuring that all Tax Data is shared with the FTA. The ASP facilitates the reporting, but the obligation remains with the Person. If the ASP fails to report, or if the reporting is incomplete, the liability under Cabinet Decision No. 106 of 2025 falls on the business.
Accredited Service Providers
ASPs carry the technical execution role: onboarding businesses onto the Peppol network, implementing the encryption and secure transmission requirements, validating and converting invoice data into PINT-AE XML where necessary, and exchanging invoices between Corner 2 and Corner 3. The Guidelines also make ASPs responsible for notifying both the business and the FTA (at [email protected]) in the event of any service disruption, and for exchanging and reporting all delayed invoices once service resumes.
The accreditation obligation is ongoing. An ASP must continue to meet all accreditation requirements — Peppol membership, company registration, information security — and must ensure timely renewals. Businesses selecting an ASP should treat continued accreditation status as a live due-diligence item, not a one-time check at the point of contract.
Peppol
Peppol's responsibilities under Appendix 3 are standards-level: providing the framework specifications for Electronic Invoice exchange, defining the requirements for access points, testing and certifying ASPs, facilitating the creation of Participant Identifiers, and monitoring ASP compliance on the Peppol network. The governance structure Peppol maintains ensures that the PINT-AE standard remains technically current as Peppol itself evolves.
For an enterprise, the practical consequence of Peppol's monitoring role is that the ASP carries a compliance obligation not just to the UAE Ministry of Finance but also to Peppol as the network authority. An ASP that loses its Peppol certification — whether through a technical failure, a security incident, or a governance breach — loses its ability to operate on the network, which terminates its ability to route invoices regardless of its UAE accreditation status.