Integrations
Connecting SAP to Ravera for UAE e-invoicing
SAP connects to Ravera through Ravera’s REST API. Your SAP team or integrator sends billing documents from SAP S/4HANA or SAP ECC to the API. Ravera converts them to PINT AE XML, validates them, exchanges them through its own Peppol Access Point and reports them to the FTA. Ravera is an FTA-Accredited Service Provider.
- SAP S/4HANA
- SAP ECC
- SAP Business One
How it works
How SAP connects to Ravera
Your system
SAP
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 SAP team or integrator builds
Your team or integrator builds and owns the connection.
- Trigger on posted SD billing documents and FI invoices, including credit memos
- Map company code, customer master data, tax codes and TRNs to the API
- Write Ravera’s status and document references back to the SAP document
- Route inbound supplier invoices into accounts payable
- Handle each company code 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
- 01
Through SAP Integration Suite or middleware
Many integrators route documents through SAP Integration Suite or existing middleware, which calls Ravera’s API and returns the status to SAP.
- 02
Directly from SAP
Others trigger an outbound call when a billing document is posted, using output management or custom ABAP, and store the response on the document.
- 03
Inbound into accounts payable
Supplier invoices received by Ravera can be brought into SAP accounts payable through the same route, ready for matching against purchase orders.
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 install anything from Ravera in SAP?
No. Ravera does not install software in your SAP system. Ravera provides a documented REST API, sandbox and credentials. Your SAP team or integrator builds the outbound and inbound flows with the tools you already use, such as SAP Integration Suite, middleware or ABAP, and owns that connection. Ravera assists testing until everything passes.
Does Ravera work with both SAP S/4HANA and SAP ECC?
Yes. Ravera’s API does not depend on your SAP release. S/4HANA, ECC and SAP Business One systems can all send invoice data to the same REST API. What differs is how your integrator extracts documents and writes statuses back, which depends on your release, your customisations and the middleware already in your landscape.
How long does it take to connect SAP 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. SAP landscapes with many company codes, heavy customisation or a busy change calendar 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.