Reconciling Peppol BIS Billing 3.0 with Poland's KSeF via Middleware Integration

Context

Poland's Krajowy System e-Faktur (KSeF) mandate requires all covered invoices to be submitted through a centralized government platform using the FA(3) XML schema. This system processes invoices via a single government API, assigning each a unique identification number upon successful submission. KSeF's centralized clearance model stands in stark contrast to Peppol's decentralized four-corner network, which routes UBL-based BIS Billing 3.0 invoices directly between trading partners.

The architectural mismatch means Peppol BIS Billing 3.0 invoices cannot be submitted directly to KSeF without format translation and data mapping. Businesses operating in Poland must either rebuild their ERP output processes for each country or introduce a middleware solution to bridge the gap. The latter approach is gaining traction as it allows companies to maintain consistent upstream ERP processes while complying with both systems.

Middleware Architecture

A middleware integration layer positioned between the ERP system and both KSeF and Peppol can resolve the incompatibility. This layer performs several critical functions:

1. Receiving Peppol UBL Output: The middleware takes the standard Peppol UBL invoice generated by the ERP.
2. Translation and Mapping: It converts the UBL payload into FA(3) XML format, ensuring compliance with KSeF requirements.
3. API Communication: The middleware manages authenticated communication with KSeF's API, submitting the translated invoice.
4. Identification Number Storage: Upon successful processing by KSeF, the middleware retrieves and stores the unique identification number assigned to the invoice.
5. Parallel Routing: The middleware separately routes the original Peppol-formatted invoice to the appropriate Peppol access point for buyer delivery.

This architecture treats KSeF submission and Peppol delivery as parallel, non-substitutable obligations. It ensures that invoices meet both the legal requirements of KSeF and the operational needs of Peppol's decentralized network.

Implications for Multinational Businesses

For multinational businesses operating in Poland, adopting a middleware integration layer offers several advantages:

• ERP Consistency: Companies can maintain their existing ERP systems without country-specific modifications, reducing complexity and costs.
• Compliance: The middleware ensures invoices comply with both KSeF's FA(3) XML schema and Peppol's BIS Billing 3.0 format.
• Efficiency: Automating the translation and submission process minimizes manual intervention, reducing errors and improving processing times.

However, businesses must carefully evaluate middleware providers to ensure they meet all technical and regulatory requirements. The choice of middleware should be based on its ability to handle the specific data mapping needs between UBL and FA(3) XML, as well as its integration capabilities with existing ERP systems.

Outlook

As of October 2026, the KSeF mandate remains in effect with FA(3) XML as the operative schema. No superseding regulatory changes to Poland's e-invoicing framework are known at this time. The middleware integration approach is likely to become more widespread as businesses seek scalable solutions to manage the complexities of operating in multiple regulatory environments.

Future developments may include enhancements to middleware capabilities, such as improved automation and broader integration with other e-invoicing systems. Businesses should monitor regulatory updates and technological advancements to ensure ongoing compliance and operational efficiency.