SAP e-invoicing in the UAE: PINT AE readiness guide for 2027

SAP e-invoicing in the UAE is no longer a planning exercise. The UAE Ministry of Finance (MoF) set 1 January 2027 as the mandatory go-live for businesses with annual revenue of AED 50 million or more, and the window to appoint an Accredited Service Provider (ASP) for that group closes on 30 October 2026. This guide is for SAP finance, tax and IT teams who now have to turn a provider contract into a working integration: the timeline, the five-corner model, what SAP does and does not provide, the integration routes, an ASP checklist, the master data that decides whether invoices pass validation, and a readiness plan. As of October 2026, everything below is taken from MoF documents and named sources, and where sources conflict or are silent we say so.

UAE e-invoicing timeline: what the MoF has confirmed

Several vendor pages quote slightly different dates. The table below uses only the MoF guidelines, the MoF’s own announcements and the Ministerial Decision text. One caution first: the MoF Electronic Invoicing Guidelines V1.1 (1 June 2026) still print 31 July 2026 in their timeline table for the larger cohort. The extension to 30 October 2026 came from Ministerial Decision 66 of 2026, which the MoF announced on 10 May 2026, so cite that decision, not the guideline table, for that date.

Three points about this table matter for planning.

• The extension covers one cohort only. The sources we reviewed show the 30 October change applying to the AED 50 million and above group. The 31 March 2027 date for smaller businesses and government entities is unchanged in those sources.
• “No further extension” is opinion, not policy. A provider quoted by Gulf News (5 October 2026) suggests treating 30 October as final. That is a vendor view, not an MoF statement. Plan as if it holds, because the go-live date has not moved.
• Little time follows the deadline. Deloitte Middle East notes that a provider signed on 30 October leaves roughly two months for onboarding, testing and training before 1 January 2027. If you have not signed, the rest of this guide is a compression exercise, not a leisurely programme.

The legal framework behind these dates, per the MoF Guidelines, is Ministerial Decision 243 of 2025 (the Electronic Invoicing System), Ministerial Decision 244 of 2025 (implementation), Ministerial Decision 64 of 2025 (service provider eligibility and accreditation) and Cabinet Resolution 106 of 2025 (violations and penalties). Two October 2026 changes post-date the Guidelines. First, Ministerial Decision 168 of 2026 repealed Ministerial Decision 64 of 2025 and replaced the accreditation framework with effect from 1 October 2026; it removes the pre-approval stage, so providers are accredited only after assessment and testing (MoF announcement of 9 October 2026). Second, Ministerial Decision 197 of 2026, announced by the MoF on 19 October 2026 and effective from 1 October 2026, amends Ministerial Decision 243: it adds a temporary exclusion for transactions between members of the same Tax Group, removes the requirement to store e-invoice data within the UAE, and repeals the system-failure provisions in Article 12. Your tax team should read the primary texts: the MoF Electronic Invoicing Guidelines V1.1 and Ministerial Decision 243 of 2025.

SAP e-invoicing in the UAE: what the rules require of an SAP invoice

Before choosing a route, be clear about what changes in the invoice itself. Per the MoF:

• An e-invoice is structured XML exchanged over the Peppol network using PINT-AE, the UAE specification, with the UAE requirements set out in the UAE Data Dictionary. There is no QR code or barcode. A PDF, a scan or a manually issued invoice is not a compliant e-invoice.
• Buyers that have not yet onboarded still get an e-invoice. Per Guidelines V1.1 section 10.2.2, when the buyer has not implemented e-invoicing and has no Peppol participant ID, the supplier must include the predefined endpoint 0235:9900000098 on the e-invoice and also issue a regular Tax Invoice (for example a PDF). That PDF satisfies the Tax Invoice requirement for that buyer; it does not replace the e-invoice.
• Business transactions are generally in scope regardless of VAT registration, subject to the exclusions in Article 4 of Ministerial Decision 243 of 2025 and later amendments. B2B, B2G and G2B transactions are covered, and G2G transactions only where a government entity is not acting in its sovereign capacity; supplies to or from consumers are out of scope, and certain financial services are excluded. Under Ministerial Decision 197 of 2026, business transactions between members of the same Tax Group are treated as excluded transactions for 24 months from 1 January 2027.
• E-invoicing does not replace the Tax Invoice obligation. The Tax Invoice or Tax Credit Note must itself be issued as an e-invoice or e-credit note (VAT Decree-Law Article 65(5), as cited in the Guidelines).
• One ASP covers both sending (accounts receivable) and receiving (accounts payable). Your AP process changes as well as your billing run.

For SAP teams, the last point is easy to miss. Scope the AP inbound flow as well as SD billing output: inbound supplier invoices arrive as structured data that has to be matched, validated and posted.

The five-corner model and where SAP sits

The UAE uses a decentralised, five-corner model on the Peppol network. The corners are:

1. Corner 1, the supplier. This is your SAP system as the system of record for the sale.
2. Corner 2, the supplier’s ASP. It receives your data, validates it and converts it to the UAE standard XML, sends it to the buyer’s ASP and reports the tax data to the Federal Tax Authority (FTA) in parallel.
3. Corner 3, the recipient’s ASP. It validates the invoice, delivers it to the buyer and also reports to the FTA.
4. Corner 4, the recipient. The buyer’s ERP or AP system.
5. Corner 5, the Federal Tax Authority. It receives the reported tax data. Confirmations flow back along the chain.

The practical consequence for SAP landscapes is that SAP does not talk to the FTA directly. SAP, as corner 1 (and corner 4 for your own purchasing), exchanges data with an ASP, and the ASP carries the Peppol and FTA interfaces. Your integration work sits between SAP and the ASP.

The MoF also splits responsibilities (Guidelines section 5.2). The supplier calculates invoice values and gathers the buyer’s Peppol ID. The ASP handles encrypted transmission, Peppol ID lookup and UUID generation. The compliance obligation stays with the supplier, or with the buyer for self-billed invoices. Appointing an ASP does not transfer your liability.

Peppol participant ID, TIN and TRN

The participant ID is “0235” followed by the 10-digit Tax Identification Number (TIN). The TIN is the first 10 digits of the Tax Registration Number (TRN). Persons that are not VAT-registered must obtain a TIN through the FTA. Each member of a Tax Group uses its own TIN and is onboarded separately. If you run several legal entities under one group registration, review identifiers for each legal entity rather than assuming one onboarding for the group. Intercompany flows between members of the same Tax Group are temporarily excluded for 24 months from 1 January 2027 (Ministerial Decision 197 of 2026), so they need not be in your first-wave e-invoicing build. Do not drop them from the design: the exclusion is temporary, it does not cover intercompany flows with entities outside the Tax Group, and you should confirm with your tax adviser which of your entities and flows qualify.

What SAP provides, and what to confirm

On 7 April 2026 SAP stated in a press release from Abu Dhabi that the UAE Ministry of Finance had named SAP a pre-approved e-invoicing service provider, the first ERP provider on the pre-approved list. ERP Today reported the same pre-approval and added that SAP customers can still pair SAP systems with external providers. That status has since moved on: the MoF list of accredited service providers (checked 21 October 2026) names “SAP Middle East & North Africa LLC” among the accredited providers, not among the pre-approved providers still under final assessment. The product SAP names is SAP Document and Reporting Compliance, a UAE solution that links SAP ERP invoicing to the government ecosystem.

Two cautions. First, the listing is for a named legal entity; make sure the entity in your contract is the accredited one. Second, the framework changed on 1 October 2026: Ministerial Decision 168 of 2026 removed the pre-approval stage, and providers that hold only preliminary approval have 30 days from that date (to about 31 October 2026) to meet the accreditation requirements or lose that approval. The MoF says the list is updated periodically, so check the live list for whichever provider you choose, SAP included, at the time you sign.

On the technical side, SAP Community material describes what the UAE solution rests on:

• UAE Peppol e-document processing depends on SAP Note 3705171, “Electronic Document Processing for United Arab Emirates – Peppol: Implementation Overview”.
• It uses the eDocument processes AEINV and AEINVIN, modelled on the EU Peppol process (EUINV), with UBL 2.1 interfaces.
• For utilities (IS-U), a SAP Community post says custom extensibility is needed.
• SAP Community event pages from March and August 2026 describe SAP Document and Reporting Compliance, cloud edition, as supporting UAE e-invoicing. Those pages do not give a release matrix.

ECC and SAP Business One

For ECC, SAP documents a route. SAP Help describes UAE electronic document processing for SAP ERP: you create electronic customer invoices in the eDocument Cockpit (EDOC_COCKPIT) and submit them, and as a buyer you receive supplier invoices, with the Peppol exchange running through SAP Document and Reporting Compliance, cloud edition. SAP lists it as available as of SAP ERP 6.0 EHP8 SP26, EHP7 SP32 and EHP6 SP37, with SAP Note 3705171 for lower levels. A separate SAP Help page covers submitting UBL 2.3 invoices created in external systems through the same solution (SAP Notes 3742431 and 3713764). Confirm your exact release, Support Package and prerequisites with SAP before you sign. For SAP Business One we found no SAP Help page on UAE e-invoicing, so treat it as an open question. ClearTax, an integration vendor, states that Business One needs integration and does not connect to the FTA natively. Ask SAP and your ASP in writing which version and add-on they support, and get the answer before you sign. SAP’s own mainstream maintenance dates for ECC are a separate matter that your SAP account team can confirm.

SAPinsider makes a related point: structured exchange depends on accurate master data, tax determination and consistent ERP configuration, validation can reject invoices before they reach accounting, and SAP landscapes will rely on external compliance and integration layers.

Integration route options and their trade-offs

There is no single correct route. These four are the routes SAP customers can weigh. The trade-offs are our assessment, not a vendor or MoF ranking, so test them against your own landscape.

Whichever route you pick, three design questions decide the outcome.

• Where does validation happen? If the ASP rejects a document, the status must come back to a person who can fix the data in SAP. A route that hides rejections in an ASP portal creates an invoicing backlog.
• How are credit notes tied to originals? Under Ministerial Decision 243 Article 6(2), an e-credit note is required for cancellation, reduced consideration, returned consideration (full or part), or an administrative or numerical error. Make sure your returns, price-adjustment and cancellation flows all produce one.
• Who supports it after go-live? Rejections, resubmissions and master-data fixes are an operational process, not a project deliverable. Decide the owner now. Our SAP application management services page describes our general approach to ongoing SAP support.

ASP selection checklist for SAP customers

The MoF’s own readiness steps (Guidelines section 9 and Appendix 1) start with understanding the requirements and gap-analysing your ERP data points, then selecting an ASP, contracting, onboarding through EmaraTax (the person initiates) and obtaining a Peppol ID via the ASP. The questions below turn that into a procurement checklist for an SAP shop.

1. Accreditation status. Is the provider’s contracting legal entity on the MoF list of accredited service providers today, and can it evidence it? The pre-approval stage no longer exists under Ministerial Decision 168 of 2026. Get the status in the contract as a representation, with remedies if it lapses.
2. SAP release coverage. Which S/4HANA releases, ECC levels or Business One versions are supported, and by which connector or add-on? Ask for the documented prerequisites.
3. Outbound and inbound. One ASP covers both sending and receiving. Confirm both are live for your go-live date, not only outbound.
4. Mapping ownership. Who maintains the mapping from SAP fields to PINT-AE and the UAE Data Dictionary, and who pays when a specification changes?
5. Error handling. What does a rejection look like, how fast does it return to SAP, and what is the resolution governance? The MoF checklist expects error-resolution governance to be agreed before go-live.
6. Data hosting and security. The MoF checklist includes agreeing data hosting and security with the ASP. Ask where data is processed and stored and how it is encrypted in transit.
7. Retention and retrieval. Article 11 of Ministerial Decision 243, as amended by Ministerial Decision 197 of 2026, requires e-invoices, e-credit notes and their associated data to be kept for the period set under the Tax Procedures Law and made available to the FTA on request. The amendment removed the earlier requirement to store that data within the UAE. Confirm who holds the archive and how you get it back if you change provider.
8. Test environments and timeline. Is there a sandbox, how many test cycles are included, and can the provider support end-to-end tests with a counterparty’s ASP?
9. Exit terms. Peppol IDs and archives should not trap you. Ask what migration support exists if you change ASP.
10. Support model. Hours, escalation path and named contacts around the first weeks of January 2027.

Master data and field-mapping readiness

The MoF assigns the supplier the job of calculating invoice values and gathering the buyer’s Peppol ID. In SAP terms, that means your master data has to be right before the ASP sees the document. We have not verified a field-by-field PINT-AE count, so we do not quote one: take the field list from the UAE Data Dictionary and from your ASP’s mapping specification. What we can say from the MoF documents is where SAP teams should start the gap analysis.

Identifiers

• Your own TRN and TIN, per legal entity. The Peppol participant ID is 0235 plus the 10-digit TIN, the first 10 digits of the TRN. Check every legal entity, and remember each Tax Group member is onboarded separately.
• Customer TRN and Peppol ID. The supplier must gather the buyer’s Peppol ID. Decide where it lives in the customer master and who maintains it, then run a data-collection exercise with your top customers by invoice volume. For buyers not yet onboarded, Guidelines V1.1 section 10.2.2 requires the predefined endpoint 0235:9900000098 on the e-invoice plus a regular Tax Invoice alongside it, so the customer master needs a flag for onboarding status and your output determination needs to produce both documents until the buyer has its own participant ID.
• Unregistered customers. Scope covers transactions regardless of VAT registration, and persons that are not registered must obtain a TIN through the FTA. Expect customers in this position, and plan how you will capture their identifiers.

Tax codes and determination

• Review tax codes and determination logic against what the UAE Data Dictionary expects, so that every tax code in use maps to a valid tax category and rate in the structured message. Pay particular attention to mixed-rate, exempt and zero-rated lines.
• Check the Article 4 exclusions in Ministerial Decision 243 for flows that may fall outside the system, such as VAT-exempt or zero-rated financial services, and confirm each with your tax advisers before excluding them from your build.

Credit notes, timing and corrections

• Credit notes. Cover cancellation, price reductions, returns and corrections of administrative or numerical errors, per Article 6(2).
• Issuance timing. Article 6(5) requires the e-invoice or e-credit note to be issued and transmitted through the system within 14 days from the Date of Business Transaction, subject to Article 6(4): a VAT registrant issues within the VAT Law timeline. The Date of Business Transaction is the earlier of the transaction date or the date payment is received. Billing runs that batch invoices weekly or monthly need a check against this rule. Article 6(6) leaves reporting to the FTA to the timeline set by the Minister.
• Changes to registered data. Under Article 5(3), the issuer and the recipient notify their ASP in writing of any change to the data registered with the FTA within five business days from receiving the FTA’s confirmation of the amendment. Add this to your master-data change process, with the FTA confirmation as the trigger.
• System failure. Article 12 of Ministerial Decision 243 originally required system failures to be notified to the Authority within two business days. Ministerial Decision 197 of 2026 repealed Article 12 with effect from 1 October 2026, so that notice is no longer required. Your incident process still needs a tax contact, because invoices must still be issued within the Article 6 timelines.

Penalties your programme should plan against

The MoF announced the fines under Cabinet Resolution 106 of 2025 on 8 December 2025. The Cabinet Resolution’s penalty table also lists AED 1,000 per day for late notice of a system malfunction. We leave that row out below because Ministerial Decision 197 of 2026 repealed the underlying notification duty in Article 12 from 1 October 2026; the MoF’s announcement of that amendment does not say the penalty text itself was changed, and it does not mention any change to the other fines. The per-day item is the one operations teams are most likely to overlook:

Voluntary participants are exempt from these fines until their mandatory date; the Guidelines state that penalties apply only from the mandatory date. In our view, fines are a smaller risk than invoices that cannot be issued: a rejected invoice that cannot be corrected quickly delays your billing and your customers’ payments.

A readiness plan for SAP teams: 90-day and compressed tracks

The 90-day plan below suits the 1 July 2027 and 1 October 2027 cohorts, and anyone with that much runway. Only about 72 days remain between 21 October 2026 and 1 January 2027, so if you are in the AED 50 million or more cohort use the compressed track after the plan. The plan follows the sequence in the MoF’s readiness steps, with SAP-specific work added. The durations are our planning assumptions, not MoF requirements.

Days 1 to 30: decide and baseline

• Confirm cohort and dates against the table above, using your latest annual revenue.
• Appoint the ASP (by 31 March 2027 for the smaller cohorts, 30 October 2026 for the larger one) and start onboarding through EmaraTax.
• Confirm SAP release, notes and add-ons with SAP and the ASP; for ECC or Business One, get written confirmation.
• Run the data-point gap analysis between your SAP invoice data and the UAE Data Dictionary.
• Inventory invoice flows: standard billing, credit and debit memos, returns, intercompany, self-billing, and AP inbound.

Days 31 to 60: build and cleanse

• Select the integration route, build or configure the SAP-to-ASP interface, and agree the transmission and confirmation messages with the ASP.
• Cleanse and enrich master data: TRN and TIN, customer Peppol IDs, tax code mapping.
• Design the rejection-handling process and assign owners in finance, tax and IT support.
• Review billing schedules against the 14-day rule and the VAT timing carve-out.

Days 61 to 90: test and go live

• Run end-to-end tests of exchange and FTA reporting, including credit notes, multi-rate invoices and inbound documents. Test with a real counterparty’s ASP where you can.
• Train billing, AP and tax teams on rejections and corrections.
• Agree the hypercare plan and the escalation path with the ASP.
• Hold a go/no-go review against the MoF’s go-live readiness steps, then switch over.

Compressed track for the 1 January 2027 cohort (about 60 days)

• Weeks 1 to 2: sign the ASP by 30 October 2026, confirm cohort and SAP release coverage in writing, and start EmaraTax onboarding.
• Weeks 2 to 5: run the data-point gap analysis, cleanse the highest-volume customer and tax master data, and build or configure the interface for the simplest invoice flows first.
• Weeks 5 to 8: test end to end, including credit notes and inbound documents, train billing, AP and tax teams, and agree hypercare. Defer lower-volume flows only where your tax adviser confirms it is acceptable.

If you are still unsigned close to 30 October, do not wait for the perfect route. Appoint the ASP first to protect your compliance position, and design the SAP integration inside that contract. Compare the same work in Saudi Arabia on our page about the ZATCA e-invoicing mandate for SAP: the two regimes are separate, so check interface details for each rather than assuming they carry over.

Frequently asked questions

When does UAE e-invoicing become mandatory?

Per the MoF Guidelines V1.1, 1 January 2027 for businesses with annual revenue of AED 50 million or more, 1 July 2027 for smaller businesses, and 1 October 2027 for government entities. Businesses may implement voluntarily from 1 July 2026.

What is the 30 October 2026 deadline?

It is the date by which businesses with annual revenue equal to or exceeding AED 50 million must appoint an ASP. Ministerial Decision 66 of 2026, announced by the MoF on 10 May 2026, moved it from 31 July 2026 by amending Ministerial Decision 244 of 2025. The go-live date of 1 January 2027 did not change.

Does SAP e-invoicing in the UAE work without an ASP?

Not directly. Per the MoF five-corner model, the invoice flows through an ASP, which exchanges documents over Peppol and reports to the FTA. That ASP can be SAP or another provider. SAP Middle East & North Africa LLC appears on the MoF’s accredited list as of 21 October 2026; check the live list when you sign.

Is SAP an accredited UAE e-invoicing provider?

Yes, as of 21 October 2026. The MoF list of accredited service providers names SAP Middle East & North Africa LLC among its accredited providers. SAP had announced pre-approval on 7 April 2026; Ministerial Decision 168 of 2026 has since removed the pre-approval stage. The list is updated periodically, so check it at signing and confirm your contracting entity matches. Altivate is not an accredited provider.

What is PINT AE mapping in SAP S/4HANA?

PINT-AE is the UAE Peppol specification for the structured XML invoice. In SAP, the mapping means translating invoice, tax, party and reference data from your SAP documents to the UAE Data Dictionary fields. Depending on your route, SAP’s eDocument framework, the ASP’s connector or your middleware performs it. Get the mapping specification in writing from your provider.

Does SAP ECC support UAE e-invoicing?

Yes, through SAP Document and Reporting Compliance. SAP Help documents UAE electronic document processing for SAP ERP, covering outgoing customer invoices and incoming supplier invoices in the eDocument Cockpit, available as of SAP ERP 6.0 EHP8 SP26, EHP7 SP32 and EHP6 SP37 (SAP Note 3705171 for lower levels), with the Peppol exchange running through the cloud edition. Confirm your exact release, Support Package and prerequisites with SAP before committing.

How quickly must an e-invoice be issued?

Article 6(5) of Ministerial Decision 243 requires issuance and transmission within 14 days from the Date of Business Transaction, which is the earlier of the transaction date or the date payment is received. Article 6(4) means a VAT registrant must still issue within the VAT Law timeline.

Are PDF invoices still acceptable?

Not as the e-invoice. The MoF states that PDFs, scans and manual invoices are not compliant e-invoices. The invoice must be structured XML on Peppol using PINT-AE. A PDF still has a role during the transition: per Guidelines V1.1 section 10.2.2, when a buyer has not yet implemented e-invoicing and has no participant ID, the supplier issues the e-invoice to the predefined endpoint 0235:9900000098 and also issues a regular Tax Invoice, for example in PDF.

What are the penalties for non-compliance?

Under Cabinet Resolution 106 of 2025, they include AED 5,000 per month for not implementing or appointing a provider in time, AED 100 per late e-invoice or e-credit note (each capped at AED 5,000 per month), and AED 1,000 per day for late notice to the ASP of changes in registered data, where the five-business-day notice period runs from the FTA’s confirmation of the change. Cabinet Resolution 106 also lists AED 1,000 per day for late notice of a system malfunction, but Ministerial Decision 197 of 2026 repealed the notification duty that fine attaches to from 1 October 2026; the MoF has not said the penalty text itself was amended. Voluntary participants are exempt until their mandatory date.

Sources: UAE Ministry of Finance (Electronic Invoicing Guidelines V1.1, 1 June 2026; Ministerial Decision 243 of 2025; Ministerial Decision 66 of 2026; MoF announcements of 8 December 2025, 10 May 2026 (also reported by WAM), 9 October 2026 and 19 October 2026; MoF list of accredited service providers, checked 21 October 2026); SAP News Center (7 April 2026); SAP Community; ERP Today; SAPinsider; ClearTax; Deloitte Middle East; Gulf News. Rules and provider lists can change. This guide is general information, not tax or legal advice. Confirm current requirements with the MoF, the FTA and your advisers.