Skip to content
Ravera

Integrations

Connecting Oracle to Ravera for UAE e-invoicing

Oracle ERP connects to Ravera through Ravera’s REST API. Your Oracle team or integrator sends receivables transactions from Oracle Fusion Cloud ERP, E-Business Suite or JD Edwards to the API. Ravera converts them to PINT AE XML, validates them, exchanges them over its own Peppol Access Point and reports to the FTA as an FTA-Accredited Service Provider.

  • Oracle Fusion Cloud ERP
  • Oracle E-Business Suite
  • JD Edwards EnterpriseOne

How it works

How Oracle connects to Ravera

Your system sends invoice data to Ravera’s API. Ravera handles the format, the network and the FTA.
  1. Your system

    Oracle

    Creates the invoice and sends the data

  2. Ravera

    Ravera API

    Converts to PINT AE XML, validates and signs

  3. Ravera

    Peppol network

    Exchanged through Ravera’s own Access Point

  4. Buyer’s ASP

    Your buyer

    Receives it through their own provider

FTA reporting: Ravera reports tax data from each invoice to the Federal Tax Authority in near real time, and archives it for 7 years in the UAE.

Who does what

What your integrator builds, and what Ravera provides

Ravera is a technology provider. Your team or integrator builds and owns the connection; Ravera gives it everything it needs to build and test.

What your Oracle team or integrator builds

Your team or integrator builds and owns the connection.

  • Pick up completed receivables invoices and credit memos
  • Map business unit, legal entity, customer, tax and TRN data to the API
  • Store Ravera’s status and document references against each transaction
  • Import inbound supplier invoices into Payables
  • Cover every legal entity and ledger with UAE tax registration

What Ravera provides

The accredited platform, and help at every step of testing.

  • A documented, FTA-approved REST API
  • API credentials and sandbox access in week 1
  • Help mapping your invoice data to PINT AE
  • Testing support until validation, Peppol exchange and FTA reporting all pass
  • In production: exchange through our own Peppol Access Point, FTA reporting and 7-year UAE archiving
  • PINT AE rule updates and local support on UAE hours

Common ways to build the connection

Your integrator chooses the approach that fits your landscape. These are the patterns we see most often.
  • 01

    Through Oracle Integration Cloud

    Fusion Cloud customers often use Oracle Integration Cloud to pick up completed transactions, call Ravera’s API and update the transaction with the result.

  • 02

    From E-Business Suite

    On E-Business Suite, integrators typically use PL/SQL, concurrent programs or existing middleware to send documents and store the response.

  • 03

    Inbound into Payables

    Supplier invoices received by Ravera can be imported into Oracle Payables, ready for matching and approval.

Onboarding

From sandbox to production

  1. 1Week 1

    Map

    We help your integrator map your invoice data to PINT AE, and issue API credentials and sandbox access.

    Who does the work: Ravera and your integrator

  2. 2Weeks 2–6

    Integrate

    Your integrator builds to our API. We assist testing until validation, Peppol exchange and FTA reporting all pass.

    Who does the work: Your integrator, with Ravera assisting

  3. 3Week 7+

    Go live

    Production credentials are issued. Ravera carries exchange, reporting, archiving and rule updates, with local support on call.

    Who does the work: Ravera

FAQ

Frequently asked questions

Do we need to install anything from Ravera in Oracle?

No. Ravera does not install software in your Oracle environment. Ravera provides a documented REST API, sandbox and credentials. Your Oracle team or integrator builds the flows using the tools you already use, such as Oracle Integration Cloud, PL/SQL or middleware, and owns that connection. Ravera assists testing until validation, exchange and reporting all pass.

Can Oracle send invoices to Ravera in real time?

Yes. Your integrator can send each invoice to Ravera’s API as soon as it is completed in Oracle, for example through Oracle Integration Cloud, and write the response back straight away. Ravera validates the document, exchanges it over Peppol and reports it to the FTA in near real time, so your finance team sees the status of every invoice.

How long does it take to connect Oracle to Ravera?

A typical project follows Ravera’s onboarding model: data mapping and sandbox access in week 1, build and testing in weeks 2 to 6, and production from week 7. Multi-ledger Oracle environments or heavily customised E-Business Suite instances can take longer. Your integrator owns the build plan, and Ravera supports testing throughout.

Start testing in the sandbox this week.

Get API credentials and sandbox access for your ERP team or integrator. No API fees, no onboarding fees.