Oracle Fusion, E-Invoicing
UAE E-Invoicing Readiness, Timeline & ASP Guide for Oracle Fusion
The UAE e-invoicing programme changes invoicing from a document-delivery process into a structured, near-real-time data exchange. For Oracle Fusion customers, readiness requires much more than selecting an Accredited Service Provider (ASP).
It requires clean master data, an agreed Oracle-to-PINT AE mapping, new controls for invoice status and a tested operating model across finance, tax and IT.
The important question is no longer, “Can Oracle generate an invoice?” It is, “Can every in-scope transaction move from Oracle Fusion through the UAE network, reach the buyer, be reported correctly and remain fully traceable?”
This guide explains the current timeline and the work Oracle Fusion users should complete before mandatory implementation. See the Innovage UAE e-invoicing solution and PINT-AE resource centre for additional guidance.
Is UAE e-invoicing mandatory in 2027?
UAE e-invoicing becomes mandatory in phases from January 2027 for in-scope B2B and B2G transactions. Businesses with annual revenue of AED 50 million or more implement first, while smaller businesses and government entities follow later in 2027. Oracle Fusion customers should prepare data, integrations and ASP connectivity early.
UAE e-invoicing mandate: deadlines for Oracle Fusion customers
The Ministry of Finance announced phased implementation for in-scope B2B and B2G transactions. As of 1 September 2026, the published milestones include:
| Category | ASP appointment | Mandatory implementation |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| In-scope government entities | 31 March 2027 | 1 October 2027 |
The pilot began on 1 July 2026. The large-business ASP deadline moved from 31 July to 30 October 2026, while the 1 January 2027 implementation date remained unchanged. See the MoF timeline announcement and May 2026 amendment.
An eInvoice is structured data—not a PDF
Under the UAE model, an eInvoice is structured invoice data exchanged electronically and reported to the Federal Tax Authority. A PDF, Word file, scanned invoice, image or email attachment is not an eInvoice.
Human-readable documents may continue to have a role, but do not by themselves satisfy the requirement described on the official UAE eInvoicing portal.
Understanding the five-corner model
The UAE is implementing a Decentralized Continuous Transaction Control and Exchange model:
- C1 — SupplierOracle Fusion creates the invoice data.
- C2 — Supplier's ASPValidates, transforms and sends the data onward.
- C3 — Buyer's ASPValidates, returns status and delivers the invoice.
- C4 — BuyerReceives structured data in its business system.
- C5 — Tax authorityReceives Tax Data Documents and returns statuses.
This model changes both outbound Receivables and inbound Payables. A complete programme must cover both.
Oracle Fusion e-invoicing integration architecture for PINT AE
A practical design has four responsibilities:
- Oracle Fusion remains the source of transactions, parties, tax and accounting status
- Oracle Integration Cloud orchestrates events, data, services, statuses and exceptions
- The ASP performs regulated validation, exchange and authority reporting
- A compliance repository stores requests, responses, statuses and reconciliation results
Oracle supports UBL 2.1 XML transaction delivery, but PINT AE is a UAE-specific Peppol specialization. Generic UBL output is not automatically PINT AE-compliant.
Outbound Receivables flow
- An eligible invoice or credit note is completed in Oracle Fusion Receivables
- The integration determines scope, transaction type and route
- Header, line, party, tax, reference, payment and totals are extracted
- Business pre-validation checks mandatory and conditional data
- The payload is mapped to the ASP contract and PINT AE
- The ASP validates, exchanges and reports the data
- Network, delivery and reporting statuses are captured
- Status is visible to finance and reconciled to Oracle
Define when an invoice is legally issued, technically delivered and operationally complete. These are not always the same status.
Inbound Payables flow
An inbound eInvoice should be transformed into an Oracle-compatible payload, validated and matched to supplier and procurement data. Review Oracle's guidance for electronic invoices in Payables and processing electronic invoices.
- Supplier identification and site selection
- Purchase-order matching
- Tax-code derivation
- Duplicate detection
- Attachments and readable representations
- Validation holds and rejections
- Credit notes and preceding references
- Status messages to the supplier network
Eight readiness workstreams
1. Scope and transaction inventory
Inventory legal entities, registrations, business units, source systems and transaction types—including invoices, credit notes, self-billing, intercompany, project, manual and recurring billing, and inbound supplier documents. Record volume, currency, party type, tax treatment, channel and Oracle source.
2. Data dictionary and gap assessment
Map Oracle data to PINT AE. Classify each field as directly available, transformed, sourced elsewhere, requiring a flexfield, conditionally required or not applicable. Focus on identifiers, addresses, registrations, tax categories, exemption reasons, references, service codes, units and AED tax amounts. Check samples with the PINT AE Validator before formal testing.
3. Master-data remediation
Assign ownership for every critical element. Find blank values, invalid formats, duplicates and unsupported codes, then add preventive validation where practical.
4. ASP selection and interface contract
Select from the official pre-approved ASP list. Assess Oracle experience, APIs, inbound and outbound coverage, status model, testing, security, support, residency, archive and change management. Agree who owns transformation, validation, Tax Data Documents and rendering.
5. Integration and status design
Define events, APIs, authentication, payload limits, timeouts, idempotency, sequencing and retries. Separate source validation, ASP acceptance, delivery, buyer-ASP result, authority reporting and final completion.
6. Tax and calculation controls
Confirm tax lines, allowances, charges, rounding and totals. Test inclusive and exclusive pricing, foreign currency, tax currency, zero-rated and exempt transactions, credit notes and adjustments. Keep Oracle, customer and reported data reconcilable.
7. Testing and cutover
Test normal, boundary and failure scenarios across entities, currencies, treatments, references, discounts, charges, credit notes, invalid data, duplicates, ASP downtime and integration failures. Include volume, reconciliation, credentials, monitoring, rollback and hypercare.
8. Governance and change management
Create joint governance across tax, finance, IT, procurement, sales operations and the ASP. Assign ownership for regulation, PINT AE changes, Oracle updates, mappings and incidents. Train users on statuses and corrections.
A 90-day readiness plan
Discover
- Confirm scope and deadlines
- Inventory inbound and outbound flows
- Assess Oracle and integrations
- Start ASP evaluation and mapping
- Run data-quality reports
Design
- Finalize architecture and responsibilities
- Confirm ASP contracts and statuses
- Approve mappings and calculations
- Design exceptions and reconciliation
- Begin data remediation
Build and prove
- Build an outbound flow
- Prototype inbound Payables
- Validate samples and connectivity
- Demonstrate finance visibility
- Reconcile and plan delivery
Readiness checklist for Oracle Fusion customers
- Applicability and date confirmed for each entity
- ASP selected within the deadline
- All invoice sources inventoried
- Receivables and Payables included
- Oracle-to-PINT AE mapping approved
- Master-data gaps remediated
- Conditional tax rules documented
- Idempotency and retries designed
- Statuses mapped to actions
- Reconciliation and retention designed
- Failure and recovery tests completed
- Change process agreed
Readiness should start before the build
The strongest programmes begin with data and operating controls, not code. Before development starts, the organisation should know its scope, ASP responsibilities, Oracle data gaps and every status meaning.
Innovage Cloud helps Oracle Fusion customers prepare across scope, data mapping, OIC integration, inbound and outbound processing, exceptions and reconciliation. Explore our Oracle ERP services and Oracle Integration Cloud and API integration services. For Saudi Arabia requirements, see our ZATCA e-invoicing with Oracle Fusion guide.
UAE e-invoicing FAQs
Is UAE e-invoicing mandatory for Oracle Fusion customers?
Yes. Oracle Fusion customers with in-scope UAE B2B or B2G transactions must meet the applicable UAE e-invoicing requirements and rollout date.
What is the UAE e-invoicing deadline for businesses with AED 50 million or more in revenue?
Mandatory implementation begins on 1 January 2027. Confirm the latest ASP appointment requirement directly with UAE Ministry of Finance guidance.
What is PINT AE?
PINT AE is the UAE-specific Peppol invoice specification used to exchange structured e-invoice data.
Does Oracle Fusion create PINT AE invoices by default?
Not automatically. Oracle Fusion data normally requires mapping, transformation, validation and integration with an ASP.
What does an Accredited Service Provider do?
An ASP validates, exchanges and reports structured invoice information within the UAE e-invoicing network.