Poland KSeF goes live 2 April 2026, what cross-border senders need to know

On 2 April 2026, Poland’s KSeF (Krajowy System e-Faktur, the National e-Invoicing System) becomes mandatory for the country’s largest taxpayers. Mid-sized taxpayers join on 1 July 2026, and the rest of the B2B base follows on 1 January 2027 after several previous postponements. KSeF is one of the more architecturally distinctive national systems in the EU 2026 mandate calendar, and the part that surprises most non-Polish exporters is how the cross-border edge is handled.

If you sell into Poland, this post is the version of the rules we wish someone had handed us when we started routing invoices there.

What KSeF is, in one paragraph

KSeF is a centralised, government-operated invoice clearing platform. Every domestic B2B invoice in Poland has to be uploaded to KSeF, where it is assigned a unique KSeF identifier (numer KSeF) at the moment of issuance. The KSeF identifier becomes the legally-binding reference for that invoice. The buyer reads the invoice from KSeF, not from email. The tax authority sees every transaction in real time.

This is a fundamentally different model from Peppol’s four-corner network. In Peppol, the network does not retain the invoice; it routes it from sender’s Access Point to receiver’s Access Point and the parties keep their own copies. In KSeF, the state is the central authoritative copy. Strip away the implementation detail and KSeF is closer to Italy’s SdI (Sistema di Interscambio) than to Peppol.

The format is FA(2) XML, a Polish-specific schema published by the Ministry of Finance. It is not UBL. It is not CII. Polish FA(2) is its own thing, and that is the integration cost.

The 2026/2027 timeline

• 2 April 2026: mandatory for taxpayers with turnover above PLN 200 million in 2024 (the “large taxpayer” cohort).
• 1 July 2026: mandatory for taxpayers with turnover above PLN 200 million in any earlier year, plus a defined mid-tier.
• 1 January 2027: mandatory for all remaining VAT-registered B2B taxpayers in Poland, including very small firms.
• From 2027: planned extensions cover B2C and certain cross-border cases.

The April 2026 date applies to the issuer side. From 2 April, large Polish taxpayers must issue all invoices via KSeF. The receiver side is automatically covered because everyone with a Polish VAT number can read invoices from KSeF whether or not they are obliged to issue through it.

Cross-border: where foreign suppliers fit in (and where they do not)

Here is the part that catches non-Polish suppliers off-guard.

KSeF, in the current legal framing, applies to invoices issued by entities established in Poland. A Dutch, German, or French supplier without a Polish establishment is not obliged to issue via KSeF for sales to a Polish buyer. The supplier issues a normal compliant invoice (Factur-X, UBL, or whatever their domestic stack uses), and the Polish buyer accepts it outside KSeF.

Three caveats turn that simple rule into a real-world checklist:

1. Polish VAT registration without establishment. If you are a foreign business with a Polish VAT number for distance sales or warehousing, the rules are stricter. The current draft regulations require KSeF issuance for invoices linked to that registration. Confirm with your Polish tax advisor whether your specific arrangement falls inside or outside.
2. Buyer preference. Polish buyers increasingly want invoices through KSeF, even from foreign suppliers, because their internal AP automation is being rebuilt around the KSeF identifier as the primary reference. A handful of large Polish buyers have already announced they will deprioritise paper or email PDFs from foreign suppliers.
3. Self-billing arrangements. If your Polish buyer self-bills (issues the invoice on your behalf), they will issue through KSeF, and the KSeF identifier becomes the legal reference even though you are the supplier.

So the practical cross-border calculus is: you are not legally forced to issue through KSeF, but you may want to anyway, and your Polish buyer’s accounting system may make life difficult if you do not.

The two cross-border integration paths

For a non-Polish supplier who decides to issue into KSeF (voluntarily or because of caveat 1), there are two technical routes.

Path A: direct KSeF integration. Build or buy a connector that authenticates with KSeF (token-based, with mTLS for production), submits FA(2) XML, and stores the returned KSeF identifier. This is the most controlled option but requires the FA(2) schema mapping. EN 16931 to FA(2) is a non-trivial transformation: there are FA(2)-specific fields with no EN 16931 equivalent, and a handful of EN 16931 fields without FA(2) equivalents.

Path B: Polish PDP-style intermediary. Several Polish service providers offer “we accept your EN 16931 invoice and map to FA(2)” as a service. Cheaper to start, locks you to a vendor for the long term, and the mapping can lose information either way. Worth it for low-volume Poland exposure; not worth it past a few thousand invoices per year.

For most exporters with material Polish revenue, Path A pays back inside the first year. For occasional Polish customers, Path B is the right call.

The archival problem KSeF does not solve

KSeF is the clearing platform. KSeF is not the archive. Polish tax law still requires the supplier to retain their own copy of every invoice for the statutory retention period (5 years from the end of the year of issuance). A KSeF identifier alone is not your archive: it is a reference into a database you do not control.

This is where Factur-X / PDF/A-3 stays relevant even on the Polish flow. The tax-compliant local copy you generate alongside the KSeF submission becomes your evidence record. PDF/A-3 with the FA(2) XML embedded is one practical pattern; PDF/A-3 with EN 16931 XML embedded plus a separate FA(2) reference is another. Both pass tax audit; the first is more compact, the second keeps your archive independent of any specific buyer’s national format.

You can validate either pattern at /check. The validator inspects the PDF/A-3 conformance and the embedded XML against EN 16931. It does not yet validate FA(2) directly, but it confirms the container is archive-grade, which is the half of the problem most pipelines silently get wrong.

What to do in the next 60 days if you sell into Poland

1. Identify Polish customers in your AR ledger. Note which ones cross PLN 200M turnover and will issue from 2 April.
2. Confirm with each buyer how they want to receive your invoices: outside KSeF (legitimate for most foreign suppliers), via their PDP-style intermediary, or directly into KSeF.
3. Decide your own posture. If Polish revenue is material and growing, plan a direct KSeF integration. If it is occasional, a Polish intermediary is fine.
4. Make sure your archival copy is PDF/A-3 with a structured XML attachment. Whether the XML is FA(2) or EN 16931, the container has to be archive-grade.

The takeaway

Poland’s mandate is the most architecturally aggressive of the 2026 cohort. The good news for foreign exporters is that the legal obligation to issue through KSeF is narrower than the headline suggests. The less-good news is that “voluntary” turns into “effectively required” once your buyer rebuilds AP around KSeF identifiers. April is closer than the calendar makes it feel.