SAP and UAE e-invoicing

In short: SAP Middle East & North Africa LLC appeared on the UAE Ministry of Finance register of Accredited Service Providers on 27 October 2026, with accreditation number 197202. SAP users can use SAP's own compliance route or connect to another accredited provider. Which fits depends on whether you run ECC, S/4HANA or Business One, your release, and how much invoicing happens outside SAP.

For most first-wave businesses, SAP is where e-invoicing gets real: high volumes, many document types, and invoices created across sales, services and intercompany flows.

ECC, S/4HANA or Business One?

SAP ECC — check with SAP which releases its UAE compliance route supports. Many ECC customers are also planning S/4HANA migrations; design the e-invoicing integration so it survives the move.
SAP S/4HANA — on-premise, private cloud and public cloud editions differ in what can be installed and extended.
SAP Business One — a different product with its own partner ecosystem; most connect to an accredited provider through a partner add-on.

What the integration has to cover

Billing documents, credit memos and self-billing mapped to PINT AE
Customer and vendor master data: TRNs, Peppol IDs, tax codes
Rejections and status written back to the billing document
Inbound supplier e-invoices into accounts payable
Intercompany and multi-entity scope, entity by entity

SAP’s route or a third-party provider?

Compare on the same four questions as any provider — integration depth, rejection handling, pricing shape and exit terms — plus fit with your SAP roadmap. Our ASP selection guide covers them; ERP integration is how SHORIQ scopes and builds it.

Last reviewed: 27 October 2026 · Reviewed by: SHORIQ