As many people already know, Belgium is set to make electronic invoicing via Peppol compulsory for B2B transactions. However, if you’re using Oracle ERP Cloud, there’s no need to overhaul your invoicing processes. We can implement an excellent solution with minimal disruption. While your team continues to create and receive invoices as usual, we handle the conversion to the correct format and ensure delivery through the appropriate channel – fully compliant with regulations. No changes are needed to receive invoices either.
Everything is seamlessly managed for clients operating in multiple countries, using various invoicing systems or dealing with a mix of B2B and B2C customers – ensuring a smooth transition without any friction.
Standard in Oracle Cloud ERP
We leverage the out-of-the-box Collaboration Messaging module in Oracle ERP to support electronic invoicing. This module is the core of our solution for both incoming and outgoing e-invoices.
We specify the channel and format for sending or receiving invoices in the master data of each customer and supplier – which makes the system flexible and scalable for all types of customers and suppliers worldwide.
Behind the scenes, an outgoing invoice is automatically converted to an XML format according to the UBL 2.1 Peppol standard, a feature offered by the Collaboration Messaging module. This XML is then sent to a Peppol Access Point of your choice. If you haven’t chosen one yet, we recommend Routty – a tool from our sister company, Dynatos.
For incoming invoices, we receive XML files via the selected Access Point. The Collaboration Messaging module in Oracle then automatically processes these into a readable document within the ERP environment. All other incoming invoices are processed by the same module – regardless of format.
You can also use Invoice Acknowledgements to inform suppliers that an invoice has been received, whether it was sent in the Peppol format or not. This tool is optional but contributes to a transparent and efficient invoicing process.
Customisable requirements
We can further customise the Peppol UBL 2.1 structure. Through message definitions, we can add or modify fields to meet the requirements of specific customers, countries or sectors. Invoices to France or Germany, for example, might need additional information.
For complex implementations across multiple countries, we organise a workshop and provide a tailored design document for your organisation – an approach that aligns perfectly with your processes and legal obligations.
Our solution – with standard modules, configurable flows and design adjustments where necessary – facilitates an efficient and almost invisible transition to electronic invoicing in Oracle ERP. All without disrupting your existing processes.