Skip to content
Ravera

Integrations

Connecting QuickBooks to Ravera for UAE e-invoicing

QuickBooks Online connects to Ravera through Ravera’s REST API, usually with a small integration built by your developer or accounting partner. Invoices created in QuickBooks are sent to Ravera, which converts them to PINT AE XML, validates them, exchanges them over Peppol and reports to the FTA. Lower-volume businesses can use Ravera’s web invoicing instead.

  • QuickBooks Online

How it works

How QuickBooks connects to Ravera

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

    QuickBooks

    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 QuickBooks team or integrator builds

Your team or integrator builds and owns the connection.

  • Pick up new invoices and credit memos from QuickBooks Online
  • Map customer, tax rate and TRN data to the API
  • Record Ravera’s status against each invoice
  • Create inbound supplier invoices as bills

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

    QuickBooks Online API

    A developer uses the QuickBooks Online API and its notifications to pick up new invoices, send them to Ravera and record the result.

  • 02

    Web invoicing

    For modest volumes, Ravera’s web invoicing lets your team create compliant e-invoices in the browser with no build at all.

  • 03

    Inbound as bills

    Supplier invoices received by Ravera can be created as bills in QuickBooks, ready for payment.

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

Should a small business use the API or web invoicing?

It depends on volume. If you issue a modest number of invoices each month, Ravera’s web invoicing lets you create compliant e-invoices in the browser with no build. If you issue more, or want invoices to flow from QuickBooks automatically, a developer or accounting partner can connect QuickBooks Online to Ravera’s REST API.

Who builds the QuickBooks connection?

Your developer or accounting partner builds and owns the connection between QuickBooks Online and Ravera’s REST API. Ravera provides the 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 does not build the connection for you.

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.