UAE E-Invoicing ERP Integration: Complete SAP & Oracle Guide

The UAE's mandatory e-invoicing deadline is 1 January 2027 for businesses with annual revenue at or above AED 50 million. That's not much runway. The standard your ERP must produce — PINT AE — contains 51 mandatory fields across 130+ total fields, built on UBL 2.1 XML (UAE Ministry of Finance, "Electronic Invoicing Guidelines V1.1", 2026). Missing the deadline costs AED 5,000 per month in penalties.

The question finance and IT teams are asking right now is a practical one: how does our ERP actually connect to all of this? This guide answers that for SAP, Oracle, and Microsoft Dynamics — the three ERPs running the majority of Phase 1 businesses in the UAE. You'll find ERP-specific paths, realistic timelines, common data mapping problems, and a clear action list. For the full mandate overview, see the UAE e-invoicing complete guide.

Key Takeaways- PINT AE has 51 mandatory fields; your ERP must map to all of them before go-live.- Cloud ERPs (SAP S/4HANA Cloud, Oracle Fusion, Dynamics 365 BC) take 6-14 weeks to integrate; on-premise ERPs can take 14-24 weeks.- Phase 1 businesses (revenue >= AED 50M) must appoint an ASP by 30 October 2026 and go live by 1 January 2027 (UAE Ministry of Finance, Ministerial Decision No. 66 of 2026).- All invoices must route through a pre-approved ASP — no direct FTA connection is permitted.- Start your ASP selection now; ERP integration cannot begin without a confirmed ASP and its technical documentation.

---

How does UAE e-invoicing connect to your ERP?

Under Federal Decree-Laws No. 16 and No. 17 of 2024, the UAE Ministry of Finance established a five-corner Peppol model as the mandatory routing path for all B2B e-invoices, with the technical architecture published in the Electronic Invoicing Guidelines V1.1 (UAE Ministry of Finance, mof.gov.ae, 2026). Your ERP sits at corner one: it generates the invoice data. Everything else — transmission, validation, FTA reporting — happens outside your ERP through your chosen Accredited Service Provider (ASP).

Here's how the five corners work in practice:

1. Your ERP (Corner 1) generates an invoice in PINT AE format (UBL 2.1 XML) or sends structured data to your ASP for conversion.
2. Your ASP (Corner 2) validates the invoice against PINT AE rules and transmits it over the Peppol network.
3. The buyer's ASP (Corner 3) receives from the Peppol network and delivers to the buyer.
4. The buyer's ERP (Corner 4) receives and processes the invoice.
5. The FTA (Corner 5) receives a copy of every invoice for tax verification.

So your ERP's job is to produce clean, complete invoice data. The ASP handles the Peppol plumbing.

There are three integration methods: API (real-time, preferred for Phase 1 businesses), SFTP (batch file submission, suitable for high-volume less time-sensitive invoicing), and portal upload (manual, only viable for very low invoice volumes). Most Phase 1 businesses will use API integration.

The five-corner model means your ERP integration project has two distinct workstreams running in parallel: the technical ASP connection (API or SFTP configuration) and the PINT AE data mapping (making sure all 51 mandatory fields are populated correctly from your existing master data). Teams that treat these as one workstream consistently underestimate the timeline.

For a detailed look at how the Peppol network handles invoice routing, the UAE Peppol network guide walks through each of the five corners.

---

How does SAP integrate with UAE e-invoicing?

SAP S/4HANA Cloud includes UAE e-invoicing localization through SAP Document and Reporting Compliance (DRC), which connects to a pre-approved ASP via API or SAP's integration middleware (SAP, "SAP Document and Reporting Compliance", 2025). This is the fastest SAP path to compliance: configuration rather than custom development.

SAP S/4HANA Cloud

If you're on S/4HANA Cloud, you're in the best position of any SAP customer. The SAP DRC module already supports Peppol-based submissions in other markets. Your integration runs through SAP Integration Suite or SAP BTP to connect to your chosen ASP's API endpoint. Expect roughly 8-12 weeks from ASP selection to go-live, depending on your master data quality.

What does configuration actually involve? You'll need to map your existing customer and vendor master data to PINT AE buyer and seller identification fields, configure your tax codes to produce correct UAE VAT output tax lines, and validate your item data against PINT AE line-item requirements. None of this is trivial — but it's configuration work, not development.

SAP S/4HANA On-Premise

On-premise is more complex. You'll need either the SAP Document Compliance add-on or a third-party middleware layer sitting between your S/4HANA instance and your ASP. Timeline: roughly 14-20 weeks. The extra time goes into middleware configuration, testing across your invoice scenarios, and the inevitable master data cleanup that surfaces during UAT.

SAP Business One and SAP ECC

SAP Business One doesn't have native Peppol support. You'll need an ASP-provided connector or a certified third-party add-on. SAP ECC is in the same position — and ECC customers should evaluate whether this compliance project is a natural trigger for a migration to S/4HANA. That said, middleware on ECC or Business One is a fully valid long-term path; several ASPs offer pre-built connectors for both platforms with ongoing maintenance included. The question isn't whether middleware works — it does — but whether you want to maintain that layer alongside your core ERP for the foreseeable future.

---

How does Oracle integrate with UAE e-invoicing?

Oracle Fusion Cloud Financials includes UAE VAT localization, and Peppol connectivity is added through either an Oracle-certified ISV partner or your chosen ASP's API integration (UAE Ministry of Finance, mof.gov.ae, 2026). Oracle's own e-invoicing solution for UAE is available as of 2025 for Fusion Cloud customers. Expect 10-14 weeks for a Fusion Cloud integration.

Oracle Fusion Cloud Financials

Fusion Cloud is the easier Oracle path. The platform's UAE tax configuration handles VAT calculations; the remaining work is connecting the PINT AE output to your ASP via API, mapping your supplier and customer identifiers to the PINT AE specification, and running end-to-end invoice scenario testing. Oracle's Electronic Business Documents (EBD) framework supports outbound structured document formats, which your ASP will integrate with.

One thing Fusion Cloud customers often overlook: the FTA requires specific UAE business registration identifiers in the seller and buyer fields. If your customer master records don't carry TRN (Tax Registration Number) data consistently, that gap surfaces during testing, not during configuration.

Oracle E-Business Suite (EBS)

Oracle EBS is the harder path. There's no native Peppol support. You'll need custom middleware or an ASP-provided API connector built specifically for EBS. Timeline: roughly 18-24 weeks, making EBS the longest integration path among the major ERPs. If your business is on EBS and in Phase 1, you needed to start this project months ago. If you haven't, prioritize ASP selection immediately — some ASPs have pre-built EBS connectors that compress the timeline.

EBS integrations consistently surface a specific problem: EBS stores invoice data in formats that don't map directly to UBL 2.1 XML fields. The translation layer between EBS output and PINT AE input is where most integration delays occur. Budget testing time accordingly.

---

How does Microsoft Dynamics integrate with UAE e-invoicing?

Microsoft Dynamics 365 Finance & Operations (F&O) includes UAE tax configuration in its standard localization, and Peppol integration runs through ASP API connectors or Microsoft's Electronic Reporting (ER) framework (UAE Ministry of Finance, mof.gov.ae, 2026). Dynamics 365 Business Central offers ISV extensions from Microsoft AppSource specifically for UAE Peppol compliance, making it one of the simpler integration paths available.

Dynamics 365 Finance & Operations

F&O's Electronic Reporting (ER) framework is the key tool here. It's designed to export structured financial documents in configurable formats — including UBL 2.1 XML for PINT AE. Your ASP will provide either an ER configuration or an API endpoint that F&O connects to via Electronic Messaging or a direct API call.

The localization already handles UAE VAT computation. What you're configuring is: the ER format mapping for PINT AE fields, the outbound channel to your ASP, and the error-handling workflow for rejected invoices. Expect 10-16 weeks for F&O. The wider range reflects variation in customization levels — heavily customized F&O instances take longer to validate.

Dynamics 365 Business Central

Business Central is the most straightforward integration path in the Dynamics family. ISV extensions on Microsoft AppSource provide UAE PINT AE output and ASP connectivity as packaged solutions. You're typically installing an extension, configuring your ASP connection credentials, and running scenario tests. Timeline: roughly 6-10 weeks. That's the shortest estimate across all the major ERP options.

Why is Business Central faster? It's a more standardized environment than F&O, with less customization to account for and a growing AppSource ecosystem built specifically for UAE compliance.

---

How long does UAE e-invoicing ERP integration actually take?

Integration timelines vary significantly by ERP type and deployment model. Based on practitioner experience across typical ERP implementation projects, cloud-hosted ERPs require 6-14 weeks while on-premise and legacy systems run 14-24 weeks. Phase 1 businesses going live on 1 January 2027 need to account for that full range when setting their project start date.

These numbers assume clean master data and a clear project scope. What extends timelines in practice? Four things consistently add weeks:

Master data gaps. PINT AE requires your customer and vendor records to carry TRN numbers, complete address fields, and consistent legal entity identifiers. Most businesses discover gaps during mapping, not during planning.

Custom invoice workflows. If your business has non-standard invoice types — rebate invoices, self-billed invoices, credit notes with complex VAT scenarios — each one needs to be validated against the 16 PINT AE invoice scenarios defined by the UAE MoF.

IT resource contention. ERP integration competes with other projects for the same SAP Basis, Oracle DBA, or Dynamics developer resources. Timeline slippage here isn't a technical failure; it's a resource allocation problem.

ASP onboarding delays. Each ASP has its own onboarding process. Some have waiting lists for technical onboarding. Don't assume that appointing your ASP is the same as beginning integration — there's a separate technical onboarding step that can take 2-4 additional weeks.

Working backwards from 1 January 2027, Phase 1 businesses running on-premise ERPs should have started their integration projects by June 2026 to allow adequate buffer. Cloud ERP customers have slightly more time, but "more time" shouldn't be read as "time to spare."

---

What are the key PINT AE data mapping challenges?

The PINT AE specification published by OpenPeppol defines 51 mandatory fields from a total of 130+ across 16 invoice scenarios (OpenPeppol, "PINT AE — Peppol International UAE", 2025). Getting all 51 fields populated correctly from your ERP's existing data structures is where most integration projects hit their first real friction.

Here's what the five categories actually mean for your ERP data:

Invoice header fields (12 mandatory). These include invoice ID, issue date, due date, invoice type code, currency, and document reference fields. Most ERPs populate these natively — the challenge is ensuring your invoice numbering sequence meets FTA requirements for uniqueness and sequential issuance.

Seller and buyer identification (10 mandatory). This is where most businesses encounter their biggest data gap. PINT AE requires the supplier's TRN, legal name, and registered address fields in a specific format. Buyer TRN is also required for B2B invoices. If your customer master doesn't consistently carry TRN data, you'll need a data remediation project running in parallel with your ERP integration.

Line item details (12 mandatory per line). Each invoice line needs: item name, quantity, unit price, line extension amount, and VAT category code, among others. ERPs generally store this data, but the mapping to UBL 2.1 XML field names and code lists requires careful translation — particularly for VAT category codes, which follow EN 16931 standards.

Tax totals (9 mandatory). VAT calculation fields, tax category, tax amount, and taxable amount per VAT rate. UAE's single 5% VAT rate simplifies this compared to multi-rate jurisdictions, but exempt supplies and zero-rated exports still require correct category coding.

Payment and delivery terms (8 mandatory). Payment means code, payment ID, and delivery date fields. These are often less consistently populated in ERP records for service businesses than for product-based businesses.

Which field group causes the most project delays? Seller and buyer identification, consistently. TRN data quality in customer master records is almost always worse than finance teams expect when they begin the mapping exercise.

---

What should you do right now to meet the 2027 deadline?

Phase 1 businesses (revenue at or above AED 50 million) must appoint their ASP by 30 October 2026 and go live by 1 January 2027, per Ministerial Decision No. 66 of 2026 (UAE Ministry of Finance, mof.gov.ae, 2026). That ASP appointment deadline is closer than it looks. And ERP integration can't begin in earnest until you've selected your ASP and received its technical integration documentation.

Here's the sequence that works:

Step 1 — Confirm your phase and your ERP deployment type. Are you Phase 1 or Phase 2? Cloud or on-premise? The answers determine your timeline and urgency.

Step 2 — Select your ASP. The Ministry of Finance maintains a list of 41 pre-approved ASPs (as of June 2026) including Comarch, Pagero, Cygnet, Defmacro, and Deloitte (UAE Ministry of Finance, "Pre-Approved E-Invoicing Service Providers", 2026). Different ASPs have different ERP-specific integration packages. Choose one that has documented experience with your specific ERP. For help evaluating your options, read the how to choose a UAE e-invoicing service provider guide. Free zone businesses should also check the UAE e-invoicing free zones guide for DIFC, JAFZA, and ADGM-specific obligations.

Step 3 — Run a PINT AE data mapping assessment. Before your integration team begins technical work, your finance team should audit customer and vendor master data against PINT AE mandatory field requirements. Find the gaps early.

Step 4 — Begin ERP integration. Work with your ASP's technical team and your ERP team to configure the connection, map data fields, and test all 16 invoice scenarios. Don't skip scenario testing — the FTA will validate invoice format on submission.

Step 5 — Join the voluntary pilot from 1 July 2026. The UAE MoF has opened a penalty-free voluntary pilot from 1 July 2026 (UAE Ministry of Finance, Ministerial Decision No. 66 of 2026). This is the best way to catch production issues before the mandatory deadline.

For a step-by-step project tracker, download the UAE e-invoicing readiness checklist, which walks through all 20 preparation steps.

---

Frequently asked questions about UAE e-invoicing ERP integration

---

Sources

1. UAE Ministry of Finance, "E-Invoicing," retrieved 2026-06-21, https://mof.gov.ae/en/about-us/initiatives/einvoicing/
2. OpenPeppol, "PINT AE — Peppol International UAE," retrieved 2026-06-21, https://docs.peppol.eu/poac/ae/2025-Q2/pint-ae/
3. UAE Ministry of Finance, "Pre-Approved E-Invoicing Service Providers," retrieved 2026-06-21, https://mof.gov.ae/en/about-us/initiatives/einvoicing/pre-approved-einvoicing-service-providers/
4. SAP, "SAP Document and Reporting Compliance," retrieved 2026-06-21, https://www.sap.com/products/financial-management/document-reporting-compliance.html