Integrations
Connecting a custom or in-house system to Ravera
Any system that can make secure HTTPS calls can connect to Ravera’s REST API, including in-house ERPs, regional ERPs, billing platforms, core banking and policy administration systems. Your developers send invoice data to the API; Ravera converts it to PINT AE XML, validates it, exchanges it over Peppol and reports to the FTA as an FTA-Accredited Service Provider.
- In-house ERPs
- Regional ERPs
- Billing platforms
- Core banking systems
- Policy administration systems
How it works
How Your system connects to Ravera
Your system
Your system
Creates the invoice and sends the data
Ravera
Ravera API
Converts to PINT AE XML, validates and signs
Ravera
Peppol network
Exchanged through Ravera’s own Access Point
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
What your developers build
Your team or integrator builds and owns the connection.
- Send invoice data to the API in the documented request format
- Authenticate with the API credentials Ravera issues
- Handle validation responses and store Ravera’s status on each invoice
- Retrieve inbound supplier invoices for accounts payable
- Monitor, retry and alert on 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
Common ways to build the connection
- 01
Direct API calls
Your system calls Ravera’s API as each invoice is issued and stores the response, giving near real-time status.
- 02
Through middleware
If you run an enterprise service bus or integration platform, it can collect invoices from several systems and send them to Ravera.
- 03
Inbound through the API
Your system retrieves supplier invoices received by Ravera through the API and passes them to accounts payable.
Onboarding
From sandbox to production
- 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
- 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
- 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 produce PINT AE XML ourselves?
No. Your system sends invoice data to Ravera’s API, and Ravera converts it to PINT AE XML, validates it and signs it before submission. Your developers work with the documented request format rather than the full PINT AE specification. Ravera helps map your data during week 1 so every required field is covered.
Can several internal systems send invoices to Ravera?
Yes. Several systems, such as an ERP, a billing platform and a core banking system, can each send invoices to the same Ravera API. Each system is mapped during onboarding. Ravera exchanges and reports every invoice under the correct entity, so the business keeps one provider and one support team for all its e-invoicing.
Other ERPs that connect with Ravera
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.