Why myKMO implemented Peppol directly
“Thanks to Flowin, we were able to integrate Peppol directly into our existing software”
myKMO has been supporting SMEs with their invoicing processes since 2017. From the beginning, users could create and send UBL invoices, and everything was properly structured. The only missing piece was a direct, stable connection to Peppol, an essential requirement for the new e‑invoicing mandate. But with mandatory e-invoicing in sight, one crucial link was still missing: a direct and stable connection to the Peppol network. For myKMO, this is not a detail, but a strategic choice.
A connection that fits the architecture: myKMO needed a Peppol solution that integrated seamlessly with its existing setup and could scale alongside the platform.
The solution had to clearly identify erros and provide enough technical information to analyze and be able to internally solve problems. This is crucial, especially for smaller organizations. Being depedent on external intermediaries or complex processes was not an option.
“We absolutely wanted to avoid having to rework our existing UBL structure. The Peppol link had to fit into what was already there, not the other way around.”
Bart Van der Donck, CEO of myKMO
A smooth Peppol integration thanks to Flowin’s API
Flowin emerged as the most logical choice after a thorough market comparison. myKMO was already working in line with OpenPeppol and European standards, such as BIS Billing 3.0.18 and PINT, so the Flowin API aligned seamlessly with their existing setup from day one.
The integration was done very smoothly and without further adjustments to the existing data structure. This not only saved time but also reduced the susceptibility to errors during implementation.
Three functions were added to myKMO’s existing system via the API:
- send sales invoices via Peppol,
- Automatically receive incoming invoices,
- check upfront whether a recipient is registered on Peppol.
This last capability ensures that it is possible to automatically choose the most suitable and secure sending channel, without any additional actions for the user.
Full visibility of every step
One of the biggest benefits for myKMO are Flowin’s logbooks. For every document, they can see exactly which technical steps were executed and where any errors occurred. This level of transparency proved especially valuable during testing and in exceptional cases, making troubleshooting faster and more efficient.
Additionally, myKMO built its own management application to monitor daily document flows. During the testing phase, the error messages provided clear and actionable insights, highlighting issues like missing parameters or incorrect codes. This made it easy to reproduce problems and resolve them quickly.
A rigorous but reliable technical foundation
The Flowin API requires a structured approach. Elements like certificate management and security need to be configured correctly from the start. While this requires some initial effort, it ensures the entire setup is technically robust.
This technical rigor also guarantees that every document meets the applicable regulations. There’s very little room for interpretation, and that’s exactly what provides reliability and peace of mind.
Combined with Flowin’s stable test environment and comprehensive documentation, myKMO had all the guidance needed to roll out the integration in a controlled and efficient way.
” myKMO now fully complies with Belgian and European e‑invoicing regulations. The Flowin API runs smoothly within our existing software and adds an extra layer of technical security, while still allowing us to stay fully in control. The Peppol connection has become a natural part of our platform. For us, that was exactly the combination we needed. ”
Bart Van der Donck, CEO of myKMO