Open source e-invoicing and Peppol

Issuing and receiving structured e-invoices from self-hosted ERP and accounting systems, running Peppol access points and SMP servers, and meeting national mandates in Germany, France, Poland and the EU ViDA rules.

Open source e-invoicing for Germany: XRechnung and Factur-X

Meeting the German B2B e-invoice rules from self-hosted Odoo or ERPNext: receiving structured invoices since 2025, the 2027 turnover threshold and EDI exception, XRechnung and Factur-X output, validation, archiving and GoBD-compliant storage.

Open source e-invoicing for the French e-invoicing reform

What French companies running self-hosted ERP need for the reform starting September 2026: issuing and receiving through an approved platform, connecting Odoo or ERPNext to it, Factur-X, e-reporting data and the 2027 date for SMEs.

Open source e-invoicing for Poland's KSeF

Connecting self-hosted ERP to the National e-Invoice System: KSeF 2.0 dates for large and other businesses, FA(3) structured invoices, Odoo's Polish e-invoicing module, authentication and handling KSeF numbers in receivables and payables.

Preparing self-hosted ERP for ViDA intra-EU e-invoicing

What the EU VAT in the Digital Age rules mean for companies on Odoo or ERPNext: national mandates allowed since April 2025, digital reporting for cross-border B2B from July 2030, EN 16931 formats, and how to plan ERP changes country by country.

Running a self-hosted Peppol access point

When an enterprise or service provider should run its own Peppol access point and SMP instead of buying one: Oxalis-NG for AS4, phoss SMP for capability lookup, Peppol certificates and accreditation, operations and the move off frozen Oxalis.

Peppol e-invoicing from a self-hosted ERP

Sending and receiving Peppol BIS Billing 3.0 invoices from Odoo or ERPNext: Odoo's Peppol module and its proxy dependency, connecting to an external access point instead, participant registration, supported countries and testing with trading partners.

E-invoicing compliance checklist

Checklist for a company preparing its ERP for mandatory e-invoicing: countries and dates that apply, formats and networks per country, master data such as tax IDs and Peppol IDs, inbound processing, validation, archiving and partner testing.

E-invoicing solution RFP questions

Questions for vendors and partners proposing an e-invoicing setup around self-hosted ERP: country and format coverage, access point accreditation, validation and error handling, archiving, monitoring, change handling as mandates evolve and support terms.

E-invoicing cost: self-hosted access point vs service provider

Cost components of running Oxalis-NG and phoss SMP yourself against paying a Peppol service provider or an ERP vendor's network: accreditation, certificates, infrastructure, integration, monitoring and per-document fees, and the volumes where each makes sense.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.