The PEPPOL connector I designed and built for Microsoft Dynamics 365 Business Central is in production worldwide today. This is the engineering story behind it — and the playbook I bring to client integration work.
The problem
Swedish and EU e-invoicing requirements keep tightening, and most ERP estates were not built for them. Documents have to leave Business Central as valid UBL, traverse the PEPPOL network to the right access point, and — just as importantly — failures have to be visible. An invoice that silently fails validation is not an integration problem, it is a cash-flow problem that shows up weeks later.
What was built
A connector layer between Business Central and the PEPPOL network: document mapping to UBL, validation pipelines that catch errors before they reach the wire, dispatch through certified access points, and archiving that satisfies auditors. Built inside the ExFlow suite at SignUp Software (now Truvio), 2024–2025, deployed for customers across multiple countries.
- Validation first — every document passes structural and business-rule checks before dispatch; failures surface with actionable messages instead of network rejections
- EDI-grade discipline — PEPPOL is EDI with better governance: participant identifiers (GLN), transport profiles, and document types all pinned down before a single byte moves
- Built to survive upgrades — the connector isolates BC version churn from the e-invoice flow, so ERP upgrades do not become compliance incidents
What it means for your stack
The same pattern generalizes: banking files, CRM sync, supplier portals, AI agents that read and write ERP data. Map the documents, validate at the boundary, make every failure observable, and keep the integration layer thin enough that upgrades never scare you. That is the work I do at AINDUSTRIES — from a single connector to the full e-invoicing pipeline, including the Swedish requirements that EU directives keep adding to.