Key takeaways
- Point-to-point e-invoicing creates unsustainable complexity as organisations scale across countries and vendors.
- Fragmented systems multiply technical debt through custom mappings, certificates, and archiving requirements.
- Hub-based models enable faster market entry and compliance updates through centralized infrastructure management.
The problem most global enterprises are facing today
Most organisations don’t fragmentation coming. They start with one country, one vendor, one integration. It works. Then they add a second country, a second vendor, a second integration. Still manageable. Then a third. Then a fourth. And before they realise what’s happening, they’re drowning in a web of connections that’s operationally impossible to maintain.
Welcome to the ‘integration explosion’, the most common of all e-invoicing problems facing global enterprises today.
What is the trap that compounds with every expansion?
The point-to-point trap starts simply enough – one more country, one vendor, one integration is included without thought. It works for now. Then once you add additional countries, vendors, and integrations, the problems start to show, and start compounding.
What isn’t so visible is the operational burden multiplying behind the scenes. Instead of a single, unified strategy, organisations implement individual integrations for each new country or mandate, creating an unsustainable web of mixed e-invoice formats and country-specific compliance regulations. Each new requirement demands a unique technical configuration, often built in isolation and for the one regulation.
Death by a thousand links
The integration explosion is more than just a theoretical problem. It’s a daily stressor disguised as “just one more link”. These e-invoicing problems compound as an organisation scales.
Every new point-to-point connection involves hidden technical and operational debt:
- Digital signatures: Each country has different requirements for digital certificates. Some require government-issued certificates. Others accept third-party providers. A few require both. Managing these certificates across dozens of connections means tracking hundreds of expiration dates, renewal processes, and vendor dependencies.
- Custom XML/UBL mappings: No two systems use identical data structures. Every integration requires custom field mapping, translating your ERP’s data model into the format each local system expects. Build one mapping wrong, and invoices fail validation. Update your ERP, and every mapping must be rebuilt.
- Local archiving laws: Some jurisdictions require seven years of retention. Others require ten. Some mandate local storage. Others accept cloud storage with specific security requirements. Each connection must handle archiving independently, creating multiple data repositories that must be maintained, secured, and audited separately.
When a format changes (which happens a lot in the e-invoicing world), every link breaks. As a result, someone on your team must manually identify, diagnose, and fix each connection. Meanwhile, invoices queue up, compliance clocks tick down, and your trading partners wait.
Compare that to the hub model, which includes only one integration to your ERP and one connection to the ONESOURCE Pagero network. From there, the hub manages 100+ interoperability links to government systems and business partners across 80+ countries. When mandates change, the hub updates once and your connection stays stable.
The growth barrier nobody talks about with fragmented e-invoicing
Fragmentation becomes truly insidious when considering how point-to-point architectures make growth nearly impossible.
Consider what happens when you:
- Acquire a company: Due diligence takes weeks. Integration planning takes months. Connecting the acquired entity’s systems to your compliance infrastructure can take six months or more. This is not because the work is technically complex, but because you’re adding new connections to an already fragmented system. It made sense when you started, but it doesn’t make sense anymore.
- Enter a new market: Every new country means negotiating with new vendors, understanding new regulations, building new integrations, and testing new workflows. A hub-based organisation can onboard a new country in under 30 days. A point-to-point organisation measures the same process in quarters.
- Launch a new product line: A new product line requires more trading partners, invoice volumes, and connection points. In a point-to-point model, growth creates geometric increases in operational complexity. Eventually, you hit a ceiling where the cost of adding the next connection exceeds its business value. You don’t stop growing because you want to, but because your infrastructure can’t support it.
The e-invoicing mandates on the horizon
ViDA 2030 is coming. The EU’s digital reporting and B2B mandates will require real-time transaction reporting, standardised data formats, and government-approved platforms. If you’re running a point-to-point model, it means that every connection must be rebuilt to meet new requirements. Every trading partner must be revalidated. Every integration must pass compliance checks. If even one link in your fragmented e-invoicing network isn’t ready by the deadline, your entire operation in that market grinds to a halt.
The ONESOURCE Pagero network handles this differently. When mandates change, the hub updates only once. The 100+ interoperability links are managed centrally, updated proactively, and tested continuously. Rather than needing to rebuild your infrastructure, you gain compliance.
What’s the real cost of “just one more link”?
The point-to-point trap is appealing because each individual connection seems manageable. It’s the cumulative effect that stalls growth. You could build 45 integrations, but you can’t maintain or scale them in a way that doesn’t slow down high-value activities. Plus, the opportunity cost of what you’re not building is unaffordable because your team is buried in integration maintenance.
The trap is clear and the pattern is unforgiving. The longer you stay trapped in point-to-point thinking, the harder (and more expensive) escape becomes.
Frequently asked questions
The integration explosion is when a point-to-point e-invoicing setup — one direct connection per country or vendor — multiplies as an organization scales, creating an unsustainable web of custom mappings, certificates, and compliance rules that becomes operationally impossible to maintain.
Point-to-point e-invoicing requires a separate integration for every country, vendor, or mandate, multiplying technical debt with each addition. A hub-based model uses one connection to a central network (which then manages links to government systems and trading partners), so compliance updates happen once instead of across every connection.
Each point-to-point connection carries its own digital certificates, custom XML/UBL field mappings, and jurisdiction-specific archiving rules. When formats change or an ERP updates, every mapping must be rebuilt manually, and certificates and retention requirements must be tracked separately for each connection.
With point-to-point architecture, integrating an acquired company’s systems can take six months or more, and entering a new market can take quarters, because each new entity or country requires its own vendor negotiations, regulatory research, and custom integration. Hub-based organizations can onboard a new country in under 30 days.
ViDA 2030 will require real-time transaction reporting, standardized data formats, and government-approved platforms across the EU. Organizations on point-to-point systems must rebuild and revalidate every connection to comply, while hub-based networks update centrally once, so users inherit compliance rather than rebuilding infrastructure.
