Poland KSeF from 1 April 2026, what cross-border senders need to know
Poland’s KSeF (Krajowy System e-Faktur, the National e-Invoicing System) became mandatory on 1 February 2026 for taxpayers whose 2024 sales exceeded PLN 200 million and on 1 April 2026 for all others; taxpayers invoicing at most PLN 10,000 a month may stay outside KSeF until the end of 2026. 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.
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.
Invoices use the FA(3) XML structure, a Polish-specific schema published by the Ministry of Finance. It is not UBL. It is not CII. Polish FA(3) is its own thing, and that is the integration cost.
The 2026 timeline
- 1 February 2026: mandatory for taxpayers whose 2024 sales exceeded PLN 200 million (the “large taxpayer” cohort).
- 1 April 2026: mandatory for all other taxpayers.
- Until the end of 2026: taxpayers invoicing at most PLN 10,000 a month may stay outside KSeF.
These dates apply to the issuer side. 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:
- Polish VAT registration without establishment. If you are a foreign business with a Polish VAT number for distance sales or warehousing, that registration alone does not bring you into KSeF: KSeF does not apply to suppliers with neither a seat nor a fixed establishment in Poland, even if they are VAT-registered there. Confirm with your Polish tax advisor whether your specific arrangement amounts to a fixed establishment.
- 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.
- Self-billing arrangements. If your Polish buyer self-bills (issues the invoice in your name and on your behalf), the same exemption applies: that invoice does not have to go through KSeF. Without a Polish NIP it cannot, because the FA(3) structure requires the seller’s NIP. If you use a Polish NIP for that sale, your buyer can issue it in KSeF once you grant them the self-billing permission there, and the KSeF identifier then becomes the reference for your invoice too.
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 it has a fixed establishment in Poland), 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(3) XML, and stores the returned KSeF identifier. This is the most controlled option but requires the FA(3) schema mapping. EN 16931 to FA(3) is a non-trivial transformation: there are FA(3)-specific fields with no EN 16931 equivalent, and a handful of EN 16931 fields without FA(3) equivalents.
Path B: Polish KSeF intermediary. Several Polish service providers offer “we accept your EN 16931 invoice and map to FA(3)” 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.
Where the KSeF archive ends
For invoices issued through it, KSeF is also the archive. Polish VAT law keeps every structured invoice in KSeF for ten years from the end of the year in which it was issued, and for those invoices the taxpayer’s own duty to keep a copy does not apply (VAT Act, art. 112aa). Your own archive starts where KSeF stops. An invoice issued outside KSeF, the normal route for a supplier without a Polish establishment, stays with you and with your buyer. Polish VAT law has taxpayers keep the invoices they issue and receive until the tax liability is time-barred: five years from the end of the year in which the VAT fell due (VAT Act, art. 112 and 112a; Tax Ordinance, art. 70 § 1). The same goes for a KSeF invoice when its ten years in KSeF end before the tax liability is time-barred: from then on, you keep it outside KSeF.
This is where Factur-X / PDF/A-3 stays relevant on the Polish flow. Polish VAT law sets no archive format. For an invoice outside KSeF, the taxpayer decides how its authenticity of origin, integrity of content and legibility are secured (art. 106m), and keeps it per tax period, easy to find and, on request, available to the tax authority without delay (art. 112a). A PDF/A-3 with the EN 16931 XML embedded holds the readable invoice and its structured data in one archive-grade file. For an invoice issued in KSeF, the FA(3) XML in KSeF is the invoice, and a PDF of it used outside KSeF must carry the KSeF QR code (art. 106gb).
A Factur-X PDF for that flow you can validate at /check: the validator inspects the PDF/A-3 conformance and the embedded XML against EN 16931. 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
- Identify Polish customers in your AR ledger. Note which ones had 2024 sales above PLN 200 million and have issued through KSeF since 1 February.
- Confirm with each buyer how they want to receive your invoices: outside KSeF (legitimate for most foreign suppliers), via their KSeF intermediary, or directly into KSeF.
- 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.
- Keep every invoice that does not go through KSeF in an archive-grade form, such as PDF/A-3 with the EN 16931 XML embedded. Invoices issued in KSeF are archived there for ten years.
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.