UAE E-Invoicing and SAP: What Finance Teams Must Do Before 1 January 2027

UAE e-invoicing becomes mandatory on 1 January 2027 for businesses with annual revenue of AED 50 million or more, and the first hard deadline arrives sooner: those companies must appoint an Accredited Service Provider (ASP) by 30 October 2026, according to the Ministry of Finance timeline as summarised by major tax advisers. A voluntary pilot has been open since 1 July 2026. For finance teams running SAP, the work is less about the law and more about data. Customer records, tax codes and invoice layouts built for PDFs now have to produce structured e-invoices that a government-connected network can validate.

What UAE e-invoicing actually requires

The UAE has chosen a Peppol-based model known as DCTCE (Decentralised Continuous Transaction Control and Exchange). In practice it is a five-corner design. The supplier sends an invoice to its own ASP. That ASP validates it and passes it across the Peppol network to the buyer’s ASP, which delivers it to the buyer. At the same time, the supplier’s ASP reports the tax data to the Federal Tax Authority (FTA). Invoices use PINT AE, the UAE version of the Peppol invoice standard.

Two consequences follow. A PDF or emailed invoice is no longer the legal document for in-scope transactions; the structured data file is. And every company needs an ASP, because businesses do not connect to Peppol or to the FTA directly.

Who is in scope and when

• Pilot: from 1 July 2026, businesses can e-invoice voluntarily.
• Large businesses (revenue of AED 50 million or more): appoint an ASP by 30 October 2026, with mandatory go-live on 1 January 2027.
• Smaller businesses: appoint an ASP by 31 March 2027, with go-live on 1 July 2027.
• Government entities: go-live from 1 October 2027.

The mandate covers B2B and B2G transactions, and published guidance indicates it applies whether or not a company is VAT-registered, including free zone businesses unless specifically excluded. Dates have moved before, so confirm the current position with the Ministry of Finance or your ASP before you finalise a plan.

Where SAP landscapes usually struggle

Most readiness gaps are data problems, not software problems:

• Customer and supplier master data: missing or inconsistent tax registration numbers, legal names that differ from the trade licence, and no Peppol participant identifier.
• Tax codes: VAT codes that mix zero-rated, exempt and out-of-scope treatments, so the e-invoice cannot state the correct category for each line.
• Invoice content: free-text lines, missing units of measure and bundled charges that a structured line-item format will not accept.
• Credit notes and corrections: processes that rely on manual re-issue instead of a traceable credit note linked to the original invoice.
• Multiple entities: several company codes, free zone and mainland entities, or more than one ERP, each needing its own route to an ASP.

Fixing these during the pilot window is far cheaper than discovering them when rejected invoices start holding up customer payments.

How SAP fits in

In April 2026, SAP announced that the UAE Ministry of Finance named it among the pre-approved e-invoicing service providers, with SAP Document and Reporting Compliance as the solution. SAP describes this as pre-approval, subject to final accreditation within the Ministry’s timeline, so confirm the current status when you evaluate it. The solution connects invoicing in your SAP system to the government-mandated e-invoicing network and supports generating, transmitting, validating and reporting invoices.

That is not the only route. Many companies will pick another accredited provider and connect it to SAP through a connector, which is common for older ECC systems. Whichever route you take, check three things: which SAP releases and support packages are covered, whether incoming supplier invoices (the buyer side) are supported on the same timeline as outgoing ones, and how rejected invoices are surfaced to your accounts receivable team.

If you are still on ECC, the timing overlaps with a bigger decision. SAP has published that mainstream maintenance for ECC 6.0 (EhP 6 to 8) ends on 31 December 2027, with an optional extension to 2030. Our guide to migrating from SAP ECC to S/4HANA covers how to sequence that move alongside compliance work.

A practical readiness checklist

• Confirm scope: your revenue band, the entities and transaction types covered, and which deadline applies to you.
• If your revenue is AED 50 million or more, shortlist and appoint an ASP before 30 October 2026.
• Audit master data: tax registration numbers, legal names, addresses and Peppol identifiers, starting with your top customers.
• Review tax codes and map each one to the categories PINT AE expects.
• Test in the pilot window with a small set of customers, and track every rejection reason.
• Decide who owns exceptions: rejected invoices, credit notes and system outages.
• Train accounts receivable and accounts payable teams on the new flow before go-live.

What non-compliance can cost

Published guidance on Cabinet Decision No. 106 of 2025 lists penalties that include AED 5,000 for each month a business is late implementing the system or appointing an ASP, and AED 100 per invoice or credit note not issued or transmitted on time, capped at AED 5,000 a month. Smaller daily penalties apply to late reporting of system failures. Check the amounts against the official text. The operational risk matters more than the fine: an invoice that cannot be issued is a payment that cannot be collected.

Where Infrabeat fits

Infrabeat approaches UAE e-invoicing readiness for SAP landscapes in the order above: scope and data audit first, then tax code mapping, then connection to your chosen provider and testing. For companies that want to modernise at the same time, RISE with SAP bundles the cloud ERP with the integration platform. For budgeting, see our SAP implementation cost and pricing guide. If you are comparing ERP options more broadly, our ERP software in the UAE buyer’s guide covers the wider compliance picture.

FAQ

Does my business have to e-invoice if revenue is below AED 50 million?

Yes, on a later timetable. Published timelines give smaller businesses until 31 March 2027 to appoint an ASP and 1 July 2027 to go live, and say the mandate applies whether or not a business is VAT-registered. Confirm your own scope with your ASP or tax adviser.

Can we keep sending PDF invoices?

For in-scope B2B and B2G transactions, the structured e-invoice becomes the invoice of record, so a PDF alone will not satisfy the requirement. A readable PDF copy can still accompany it for your customer’s convenience.

Do we need S/4HANA to comply?

No. Older SAP ECC systems can connect through an accredited provider’s connector. The end of ECC mainstream maintenance in 2027 is a separate reason to plan a move to S/4HANA.

Is SAP an approved UAE e-invoicing provider?

SAP announced in April 2026 that the Ministry of Finance named it among pre-approved providers, subject to final accreditation. Check the Ministry’s current list and SAP’s release coverage before you rely on it.

Ready to talk? Talk to Infrabeat about a UAE e-invoicing readiness review for your SAP landscape. Contact us.