Skip to content
Ravera

Integrations

Connecting Microsoft Dynamics to Ravera for UAE e-invoicing

Microsoft Dynamics 365 connects to Ravera through Ravera’s REST API. Your Dynamics team or partner sends posted sales invoices from Dynamics 365 Finance or Business Central to the API. Ravera converts them to PINT AE XML, validates them, exchanges them through its own Peppol Access Point and reports to the FTA as an FTA-Accredited Service Provider.

  • Dynamics 365 Finance
  • Dynamics 365 Supply Chain Management
  • Dynamics 365 Business Central

How it works

How Microsoft Dynamics connects to Ravera

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

    Microsoft Dynamics

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

Your team or integrator builds and owns the connection.

  • Trigger on posted sales invoices, free-text invoices and credit notes
  • Map legal entity, customer, sales tax codes and TRNs to the API
  • Store Ravera’s status and document references on each invoice
  • Create inbound supplier invoices in purchasing
  • Cover each legal entity with its own 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

    Dynamics 365 Finance

    Partners commonly use business events or Electronic Reporting to prepare invoice data, with Azure Logic Apps or middleware calling Ravera’s API.

  • 02

    Business Central

    On Business Central, partners usually build an AL extension that calls Ravera’s API when an invoice is posted and stores the result.

  • 03

    Inbound into purchasing

    Supplier invoices received by Ravera can be created as purchase invoices or vendor invoice journals, ready for 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

Does Ravera work with both Dynamics 365 Finance and Business Central?

Yes. Both connect to the same Ravera REST API. The work on the Dynamics side differs: Finance projects often use business events, Electronic Reporting and Azure services, while Business Central projects usually use an AL extension. Your Dynamics partner chooses the approach that fits your environment and owns the connection.

Who maintains the Dynamics side after go-live?

Your Dynamics team or partner maintains the Dynamics side, including extensions and data mapping. Ravera maintains the platform side: the API, validation rules, Peppol exchange, FTA reporting and archiving. When PINT AE rules change, Ravera updates its validation and tells your team about any data changes needed in Dynamics.

How long does it take to connect Dynamics 365 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. Environments with many legal entities or heavy customisation can take longer. Your Dynamics partner 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.