How do you integrate Oracle with UAE e-invoicing? The 30 October sequence on EBS and Fusion

An Oracle UAE e-invoicing project starts from a plainer fact than its SAP equivalent: the vendor is not on the list. When we checked the Ministry of Finance's published provider list on 5 October 2026, it carried 42 names — SAP Middle East & North Africa LLC among them, no Oracle entity anywhere. The mandate itself — Ministerial Decisions 243 and 244 of 2025, with the first phase re-dated by Ministerial Resolution No. 66 of 2026 — requires businesses at or above AED 50 million in revenue to appoint an Accredited Service Provider by 30 October 2026 and to issue e-invoices from 1 January 2027. So where an SAP shop can at least debate a single-vendor chain, an Oracle shop has one architecture family and one open question: which provider, consuming what, extracted how. That is a narrower problem — and with 25 days left on the appointment clock, narrower is a gift, if you treat it as one.

What the calendar says, precisely

The facts, verified against the Ministry of Finance's publications on the day this was written. The pilot began on 1 July 2026, with voluntary adoption open from the same date. Businesses whose annual revenue is AED 50 million or more appoint an accredited provider by 30 October 2026 and go live on 1 January 2027. Businesses below the threshold appoint by 31 March 2027 and go live on 1 July 2027; government entities appoint by 31 March 2027 and go live on 1 October 2027. The penalty regime exists under Cabinet Decision No. 106 of 2025, and it does not apply to voluntary early adopters. The scope is B2B and B2G; B2C stays out until a further decision. The full legal picture is on the UAE compliance page, which we keep current against the Ministry's announcements.

Where Oracle actually is

Three statements describe the Oracle position, and none of them is controversial among the people doing the work. First, neither E-Business Suite nor Fusion Cloud Financials produces the UAE's PINT AE document out of the box — there is no UAE equivalent of the single-vendor route SAP sells through DRC cloud edition. Second, no Oracle company appeared on the Ministry's published provider list when we checked on 5 October 2026 — the list carried 42 names, and the only ERP vendor on it was SAP. Third, the integration pattern the market has converged on is extract-and-transform: invoice data leaves Oracle through the interfaces the platform already has — the REST APIs and BI Publisher on Fusion, PL/SQL or BI Publisher extracts on EBS 12.x, with Oracle Integration Cloud commonly sitting between as the integration layer — and the ASP constructs, validates and exchanges the PINT AE document on its own platform. Your provider holds the Peppol corner; Oracle holds the books. The Saudi-specific mechanics — certificates, stamping, the hash chain — are treated fully on the Oracle integration page; this note is the UAE sequence.

The absence of a vendor option is not a disadvantage

SAP shops spend September debating whether the vendor's accreditation settles the architecture. Oracle shops skip that meeting. The decision compresses to the questions that were always the real ones: which legal entity's invoices flow through which registration; what exactly the provider consumes from your system — a BI Publisher output, a REST extraction, an agent, an interface table — and who owns that extract when the field list moves; where the invoice data is stored, because UAE rules require storage within the State; and what the exit terms return to you. Run the scorecard and the lock-in questions against every candidate. And run two clocks: the appointment is due 30 October 2026 — 25 days from this page's verification date — while the integration workstream runs to 1 January. The appointment is the long pole now. If nothing else in this note survives contact with your steering committee, let that sentence survive.

The six-stage sequence

1. Scope: which entities, which phase, which Oracle. List every entity in the group, its revenue against the AED 50 million test, and which system issues its invoices. The obligation applies regardless of VAT registration status, subject to the published exclusions — the revenue test, not the VAT register, decides your phase. EBS and Fusion are two different projects wearing the same word: the data model, the extraction mechanism and the release cadence all differ, and a group running both after a partial migration is one programme with two technical baselines. Add the satellites while you are at it — the point-of-sale system, the legacy billing engine, the subsidiary on something that is not Oracle at all — because every system that issues a tax invoice needs a route to the network.

2. Audit the data before touching the architecture. The Ministry's field list defines 51 mandatory fields on an electronic Tax Invoice, 13 of them on the invoice line, validated field by field; the e-invoicing participant identifier is not your 15-digit TRN, and the distinction generates rework when discovered late. In Oracle terms this is a customer-master and configuration audit: seller records that match registrations character for character, structured addresses instead of the free-text lines AR has tolerated for a decade, tax classification per line, buyer identifiers you currently have no field discipline for. It is measurable today with no provider appointed, and the remediation transfers whichever provider you pick. We publish both the field-by-field guide and the 25-point self-scoring checklist — run the checklist before the first vendor demo.

3. Make the architecture decision deliberately. The shape is fixed — Oracle extracts, the ASP transforms and exchanges — but three choices inside it carry the risk. Where the extract runs: BI Publisher and the REST APIs on Fusion, PL/SQL or BI Publisher on EBS, an agent or interface file where a provider supplies one — pick the mechanism your own team can operate at month-end, not the one that demos best. Where the mapping lives: in an OIC layer you own, or in the provider's platform — the first costs more now and less at exit, the second reverses that trade. And how inbound flows home: receiving is part of the mandate, and an inbound PINT AE document needs a landing path into Payables that somebody has designed, not assumed. In every variant, the work that is never thrown away is the master data layer. Build that first.

4. Appoint the ASP — by 30 October, and formally. The appointment is an act, not a default: a signed contract per in-scope entity, custody terms read, exit terms read. Add the Oracle-specific question — what exactly does your connector consume from my system, on which release? An answer given for Fusion 24D does not transfer to EBS 12.1 unexamined, and the answer sizes your integration work more than any brochure does. The Ministry's list moves — names were being added through September — so check it again the day you sign, and verify the accreditation status, not the marketing page, because pre-approved is not accredited and production go-live needs the latter.

5. UAT with production-shaped data, including the ugly documents. Clean invoices pass first time almost everywhere. Failures concentrate in credit notes referencing originals, foreign-currency invoices with their AED amounts, prepayments, self-billing and inter-company charges — and in Oracle estates, in the AR transaction types and descriptive flexfields nobody remembered were still in use. Test the 14-day issuance-and-transmission window against your actual month-end batch behaviour, because a billing run that releases three thousand documents on the night of the 30th behaves differently from the demo. And resist copying a Saudi design: UAE invoices carry no QR code, there is no clearance ceremony and no certificate lifecycle on your side of the fence — a point that catches every team that ran a ZATCA programme on Oracle first.

6. Cut over, then run it as an operation. Go entity by entity where structure allows. Staff the run state: a named owner for rejections who fixes root causes in master data — the rejection log is a data audit you didn't order — and treat every Oracle patch, quarterly Fusion update and provider release as a planned change window with its own regression cycle. The extract you built is now a compliance interface; the field list it serves moves with the regulation, which means it moves.

Where Oracle projects slip

Three patterns repeat. First, assuming the Saudi build covers the UAE: a ZATCA Phase 2 programme on Oracle produced UBL documents, certificates and a hash chain, and none of that plumbing exchanges a PINT AE document through a five-corner network. What transfers from Riyadh to Dubai is your master data and your team's scar tissue, not the pipe. Second, letting the extract become nobody's asset: when the provider writes the extraction logic, the mapping knowledge leaves with the contract; when your team writes it, the month-end operation owns a new interface. Either answer can be right — the slippage comes from not deciding, in writing, who maintains the extract when the Ministry revises the field list. Third, designing for outbound only: receiving is part of the mandate, inbound documents arrive whether or not Payables is ready, and the teams that treat inbound as a phase-two nicety spend January reconciling by hand.

How long does this take?

Counting back from 1 January 2027: UAT through November–December, ASP contract signed and onboarding started by late October, data remediation running now — which makes a Phase 1 Oracle estate starting this week on time, with no slack for a second attempt. The scoping and the data audit are stages one and two of the readiness assessment, and that conversation is free, with a senior practitioner. The remediation itself is the data practice's bread and butter; the extract and middleware work sits with the ERP integration practice; and the compliance framing is described plainly on the e-invoicing practice page.

Dates, thresholds and the provider-list check were verified on 5 October 2026 against the Ministry of Finance's publications — Ministerial Decisions 243 and 244 of 2025, Ministerial Resolution No. 66 of 2026, Cabinet Decision No. 106 of 2025, and the Ministry's provider list published under Ministerial Decision No. 64 of 2025 (42 names, no Oracle entity among them, on the day of writing; the Ministry has restructured these pages more than once, so counts and labels move). Statements about Oracle product behaviour reflect the extraction interfaces Oracle documents for EBS and Fusion and the integration patterns we and the wider implementer community run on them — Oracle publishes no UAE PINT AE generator for either platform as of this writing. All of these are revised without ceremony — check the primary documents before relying on any date here.