When a Swiss company decides to implement structured e-invoicing, one of the first practical questions is whether to build on open-source tools or buy a commercial platform. Both routes work. The right answer depends on your technical capacity, invoice volumes, integration requirements, and how much control you want over the implementation.
This post lays out what each approach actually involves, where each one breaks down, and how most companies end up combining elements of both.
What open-source tools give you
The Swiss and European e-invoicing ecosystem has a reasonably strong set of open-source components. For Swiss-specific formats, there are libraries that generate and validate QR-Rechnung, parse camt.054 XML, and produce pain.001 payment files. For PEPPOL, there are open-source implementations of the AS4 transport protocol, the SMP client for participant lookup, and UBL generation. The SwissDIGIN validation tool itself is open source.
What open-source gives you is the building blocks — well-tested, standards-compliant components you can integrate into your own systems. If you have developers who know the domain, you can assemble these components into a pipeline that does exactly what you need, without paying per-transaction fees or being constrained by a vendor's feature roadmap.
The cost is low in the sense that the software itself is free. The cost that is often underestimated is the integration work, the maintenance overhead when standards update, and the time needed to develop the operational tooling around the core library — monitoring, error handling, retry logic, and so on.
What commercial platforms give you
A commercial e-invoicing platform is a managed service. You connect your ERP to it — typically via an API or a certified ERP connector — and it handles the translation, routing, delivery, and receipt of structured invoices. The vendor manages PEPPOL certification, standard updates, and access point infrastructure. You pay a subscription or per-transaction fee.
The main advantages are speed of implementation and reduced operational burden. A certified access point provider connected to your SAP, Microsoft Dynamics, or Abacus instance can have you sending PEPPOL invoices within weeks, without requiring your team to understand the protocol stack. For eBill, SIX's own portal and API are what most billers use, and several commercial platforms have pre-built eBill connectors.
The trade-offs are cost at scale (per-transaction fees add up at high volumes), dependency on the vendor's roadmap and pricing, and less flexibility when you need to handle unusual scenarios — partial credit notes, complex multi-currency invoices, non-standard buyer requirements — that the platform was not designed for.
Where each approach struggles
Open-source struggles with operational readiness. A library that generates valid PEPPOL BIS Billing 3.0 XML is only part of the picture. You also need to handle delivery failures, manage participant ID lookups, deal with access point downtime, and ensure your output passes the Schematron validation rules for every document type you send. None of that is in the library. Building a production-ready pipeline on top of open-source components is a meaningful engineering project, not a weekend integration.
Standards also change. PEPPOL BIS Billing 3.0 has had multiple updates since its introduction. SwissDIGIN publishes new profile versions. When the standard updates, open-source libraries need to update too — and if you are maintaining your own integration, you own that update process. Commercial vendors absorb that work as part of their service.
Commercial platforms struggle with unusual requirements and exit flexibility. If your invoicing process has edge cases that the platform does not handle — say, you need to send invoices with a non-standard document type, or you need to integrate with a procurement system the vendor does not support — you may hit walls quickly. Vendor lock-in is also a real concern: switching platforms means reconfiguring integrations, potentially changing participant IDs, and re-onboarding trading partners.
The hybrid approach most companies actually use
In practice, the open-source vs commercial choice is rarely absolute. Most mid-sized Swiss companies end up with a hybrid:
- A commercial access point provider for PEPPOL transport and eBill delivery (where operational reliability and certification are non-negotiable)
- Open-source or custom code for the ERP-side data extraction and XML generation (where the business logic is specific to their processes)
- Open-source validation tools for pre-flight checks before documents leave the company's systems
This separation makes sense. The transport layer is infrastructure — reliability matters more than flexibility, and the cost of certification makes it impractical to run in-house. The document generation layer is business logic — it needs to map cleanly from your ERP's data model to the target format, which often requires custom work regardless of what tooling you start with.
What to evaluate in either case
Whether you are assessing open-source libraries or commercial platforms, the questions worth asking are similar:
Swiss-specific support. Does it handle QR-IBAN, Swiss UID, the SwissDIGIN profile extensions, and camt.054 reconciliation? Generic European e-invoicing platforms sometimes have shallow Swiss support.
Update policy. How quickly do standard updates get incorporated? For open-source, check the commit history and issue tracker. For commercial vendors, ask specifically about the timeline for the last PEPPOL BIS or SwissDIGIN version update.
ERP integration. What does the integration with your specific ERP look like? Off-the-shelf connectors exist for SAP, Microsoft Dynamics, and Abacus. For others, you may need custom API work either way.
Error handling and monitoring. What happens when a document is rejected? How are delivery failures surfaced? This is often where open-source implementations are thinner, and where commercial platforms earn their fees.
Total cost of ownership. For open-source, include developer time for integration, ongoing maintenance, and incident response. For commercial, include per-transaction costs at your expected volume, plus any ERP connector fees. The ROI framework post can help structure this comparison for your CFO.
For most Swiss companies without a dedicated integration team, a commercial platform is the lower-risk starting point. For companies with strong technical capacity and specific requirements, an open-source-based approach — possibly combined with a commercial access point for transport — often delivers more control at lower long-term cost.