Maventa

What happens when you send a Peppol invoice to a country where the receiver needs a different local format? With Maventa, the invoice is converted and routed in the format the receiving side needs. This is one of the questions that comes up more often now, especially as European countries are moving forward with their own e-invoicing mandates and local requirements. Peppol is a powerful network, but it does not remove the reality that different countries still have their own formats, rules and ways of receiving invoices. For the sender, this should not become a manual problem. If a company sends an invoice through Peppol, they should not have to understand every local format in every country where their customers operate. They need to know that the invoice reaches the receiver in the right way, even when the technical requirements behind the scenes are different. That is where infrastructure matters. The value is not only in sending an invoice from one system to another, but in handling the conversion, routing and local requirements in a way that makes cross-border invoicing easier for the software provider and the end customer. For partners evaluating e-invoicing providers, this is one of the questions I would ask early: what happens after the invoice leaves your system, especially when Peppol, local formats and country mandates meet in the same process?

Peppol gets called a lot of things: a file format, a government mandate, a checkbox in your ERP setup. None of that quite explains what it actually is, or why it's quietly become the default way European businesses exchange invoices. In this episode of Maventa's e-invoicing masterclass, Software Architect Jussi Koljonen (interviewed by Partner Manager Max Söderlund) breaks down what Peppol really is, why it's spreading fast across Europe, and the assumptions about it that tend to cause problems down the line. If you work with invoicing, finance systems, or ERP integrations, this is 10 minutes well spent. https://lnkd.in/dKNDa99G

How many e-invoicing integrations does it take to cover Europe? If you ask us, one multi-market API is enough.

Build or buy isn't really the question. The question is what you want to own, and what you'd happily never think about again. Quite often e-invoicing infra ends up in the latter category. 👀

E-invoicing mandates are moving across Europe faster than most companies realize. I’ve spent the past few days getting into the details, and this is not something sitting somewhere in the future. The timelines are already set, and several countries are already in enforcement or very close to it. Belgium moved to mandatory B2B e-invoicing in January 2026. France is starting its rollout during 2026. Poland is advancing with its own model. Germany has already required companies to be able to receive e-invoices. And this is only part of the picture. At the same time, the EU is pushing forward with the ViDA initiative, which will expand e-invoicing and digital reporting across borders in the coming years. Step by step, this is becoming the standard way of doing business in Europe. The timelines are clear, but the reality in many companies is still very early. This is still being discussed as something to prepare for, not something that will soon block how you invoice customers if not handled. In my role as Interim Commercial Director at Maventa, this becomes very concrete very quickly. This is no longer about offering e-invoicing as a feature. It’s about making sure software providers and their customers can actually operate when these mandates kick in. Across countries. Without building a new setup every time. Because when these deadlines hit, this is no longer optional. It’s simply how invoicing is done. More info on the actual timelines: https://lnkd.in/dr9mvB6U

Hear from us more regularly by following our page.