Skip to content
Ravera

Integrations

Connect your ERP to UAE e-invoicing

Ravera connects with SAP, Oracle, Microsoft Dynamics, NetSuite, QuickBooks and custom ERPs through one documented, FTA-approved REST API. Your ERP team or integrator builds and owns the connection. Ravera, an FTA-Accredited Service Provider, provides the API, sandbox and credentials, helps map your data to PINT AE, and assists testing until everything passes.

Choose your ERP

Each page explains how that ERP connects to Ravera’s API, what your integrator builds, and what to expect.

How it works

One API between your ERP and the Peppol network

Every ERP follows the same path. Your system sends invoice data once; Ravera handles the format, the network and the FTA.
  1. Your system

    Your ERP

    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

Your integrator builds. Ravera carries the compliance.

Ravera is a technology provider. We do not install software in your ERP or run your project; we give your team everything it needs to build and test.

What your ERP team or integrator builds

Your team or integrator builds and owns the connection.

  • Send invoice data from your ERP to Ravera’s API when an invoice is posted
  • Map your ERP’s fields to the API, with Ravera’s help on PINT AE
  • Write Ravera’s status and document references back to the ERP
  • Bring inbound supplier invoices into accounts payable
  • Monitor and retry failed calls

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

Onboarding

From sandbox to production in three steps

  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

No ERP connection? You can still comply.

Lower-volume entities can issue and receive compliant e-invoices without any build.
  • REST API

    Documented and FTA-approved. Your ERP team or integrator connects once and sends every document.

  • Web invoicing

    Create and send compliant invoices in the browser. Suited to lower-volume entities.

  • Supplier portal

    Give smaller suppliers a simple way to send you compliant invoices.

FAQ

Integration questions

Do we need to replace our ERP to comply?

No. Your existing ERP stays in place. It connects to your Accredited Service Provider through an API, sending invoice data out and receiving supplier invoices back. Ravera connects with SAP, Oracle, Microsoft Dynamics, NetSuite and QuickBooks, and with custom ERPs through its REST API. Your ERP team or integrator builds and owns that connection, with Ravera assisting during testing.

Which ERPs connect with Ravera?

Ravera connects with SAP, Oracle, Microsoft Dynamics, NetSuite and QuickBooks, and support for Odoo is in progress. Custom and regional ERPs connect through the same documented REST API. For lower volumes, Ravera also offers web invoicing and a supplier portal, so entities without an ERP connection can still issue and receive compliant e-invoices.

Who builds the connection between our ERP and Ravera?

Your ERP team or your system integrator builds and owns the connection. Ravera provides the API, documentation, sandbox and credentials, helps map your invoice data to PINT AE, and assists testing until validation, Peppol exchange and FTA reporting all pass. Ravera is a technology provider and does not carry out end-to-end implementation projects.

How long does onboarding with Ravera take?

A typical onboarding runs in three stages. In week 1, Ravera helps your integrator map invoice data to PINT AE and issues API credentials and sandbox access. In weeks 2 to 6, your integrator builds to the API while Ravera assists testing. From week 7, production credentials are issued. Timelines depend on your ERP and data.

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.