UAE E-Invoicing: Peppol capability

The ASP operates as your access point: confirm Peppol interoperability, SMP publication handling and invoice-response support. In the UAE this is an accreditation condition: under Ministerial Decision No. 168 of 2026 a provider must be an active Peppol-certified service provider that has passed the OpenPeppol conformance tests (Article 4), and before accreditation it must pass OpenPeppol interoperability testing under PINT AE and obtain a production Peppol PKI certificate (Article 12). Since 1 October 2026 there is no pre-approved stage (see our summary of Ministerial Decision 168 of 2026), so check the Accreditation Number on the register, and ask anyway.

Accreditation under MD No. 168 of 2026 (which replaced MD No. 64 of 2025 and MD No. 56 of 2026 from 1 October 2026 and removed the pre-approval stage) lasts two years, is renewed on an application filed at least 70 business days before expiry, and can be terminated: the register is the source of truth at signing and afterwards. A provider is business-critical infrastructure once you transmit through it: diligence accordingly.

Work through these in order.

The cheapest provider is rarely the cheapest outcome. Weight onboarding quality, error handling and support responsiveness alongside price: the first quarter after go-live is when the decision is truly tested.

Mapping without tax advice is the quietest pitfall: every ERP tax code must resolve to exactly one PINT AE category, and the person doing it needs the VAT legislation open, not just the field list. Designated Zone scenarios, reverse charge and zero-rated versus exempt distinctions are where 'close enough' codes become misreported positions.

Numbering discipline is the next: sequential, gap-free series per entity, separate series for credit and debit notes, documented void handling. Validators and the FTA both read numbering as a completeness signal.

Finally, the moving target: PINT AE, the PASR and FTA guidance will evolve, especially in the first two years. Assign someone to track publications now, because a specification change with a compliance date is a project with a deadline, and the network enforces the new rules whether you tracked them or not. Pilot where you can: a bounded pilot with real invoices finds every one of these problems while they are still cheap.

In a review, the authority asks for records, not narratives: the transmitted documents, the validation history, the correction trail from original through credit note, the monthly reconciliations, and the archive. Each should be producible within a timeframe the request respects.

Correction trails deserve emphasis: every credit and debit note referencing its original, every resubmission logged with its rejection. A ledger that matches the network record is the strongest position a business can hold.

Keep the rule-change log too: which PINT AE or guidance updates arrived, when, and what changed in your process in response. It shows a compliance function that tracks its obligations, which is exactly what a reviewer wants to see.