Poland KSeF E-Invoicing 2026: The Mandate Is Live. Here's What Changed and What's Still Coming

Poland's Krajowy System e-Faktur (KSeF) stopped being a future problem on 1 February 2026. Mandatory B2B e-invoicing through the central platform went live for large taxpayers that day, and rolled out to everyone else with a Polish establishment on 1 April. Three months in, the picture is clearer than it has ever been: the system works, the FA(3) schema is stable, the penalty clock is paused until January 2027, and the rules for foreign sellers turned out to be narrower than many feared. This is what businesses operating into Poland actually need to know in May 2026.

The two waves that have already happened

The Polish Ministry of Finance split the mandate into staggered waves to avoid the kind of one-day cliff that broke other national platforms in their first weeks.

The threshold for the first wave is fixed: it looks at 2024 sales, not 2025. Around 4,200 large taxpayers fell into that group. Everyone else above the micro line had a two-month runway, then went live on 1 April.

What KSeF actually does

KSeF is a centralized clearance platform, not a federation. Every B2B invoice in scope must be uploaded as structured XML to the Ministry of Finance's servers. KSeF validates the XML against the FA(3) schema, assigns a unique KSeF reference number (KSeF ID), timestamps the invoice, and exposes it to both the issuer and the recipient through the platform. The KSeF ID, not the supplier's internal number, becomes the legal identifier of the invoice.

That model has three knock-on effects most ERPs were not built for:

• Real time, not batch. An invoice is not legally issued until KSeF accepts it and returns a KSeF ID. If the schema validation fails, you have an unissued invoice, not a draft.
• Two numbers per invoice. Your internal invoice number still exists, but the KSeF ID is what tax authorities, customers, and (from 2027) the payment system will use to match to the underlying transaction.
• No private exchange channel for in-scope invoices. You cannot agree with a Polish customer to skip KSeF. PDF copies of a KSeF invoice are fine for human reading but have no legal effect on their own.

FA(3): the schema you actually integrate against

FA(3) replaced FA(2) on 1 February 2026. It is a Polish CIUS (Core Invoice Usage Specification) loosely aligned with EN 16931, but with country-specific fields that European generic libraries do not cover. Notable changes from FA(2):

• Attachments are now supported. You can attach supplementary documents (delivery notes, photos, calculations) directly to the structured invoice. Each attachment counts toward a per-invoice size cap.
• New transport and excise fields for industries previously forced into workarounds (intra-EU goods movements, energy products, alcohol).
• Tighter validation on counterparties: a supplier or buyer NIP that does not match the central VAT register triggers a hard reject, not a warning.
• Code list expansions for invoice types, payment methods, and unit-of-measure codes. Several FA(2) free-text fields became enumerations.

If you integrated against FA(2) in a 2024 pilot, plan a real schema migration, not a copy-paste. The FA(3) XSD is published by the Ministry of Finance and any KSeF-certified middleware (BPM Software, Comarch, Sovos, Edicom, Avalara, Pagero, and others) bundles it.

The two offline modes you should understand

The legislators built escape hatches into KSeF after 2024 stress tests showed that mandating real-time clearance for every Polish invoice was operationally fragile. There are two named modes:

Offline24

If KSeF is unreachable for any reason on the supplier's side (your internet, your platform, your software), you can issue the invoice outside KSeF in FA(3) format with a QR code, and you have until the end of the next working day to upload it. The invoice's legal date remains the original issuance date. Offline24 is intended for everyday glitches and is part of the permanent regime.

Voluntary offline (transitional)

Through 31 December 2026, taxpayers may issue invoices outside KSeF on a voluntary basis (no system outage required), provided they upload them to KSeF the next working day. This is a transitional cushion for businesses still finalizing their integrations. From 1 January 2027 it goes away, and the only legitimate offline trigger is Offline24.

System outage mode

If the Ministry of Finance declares KSeF itself to be down, taxpayers can issue invoices outside the system without the next-day upload obligation, with the upload window extended until KSeF is back online. The Ministry communicates outages on a public status page; do not rely on third-party reporting.

B2C: optional, mostly off

KSeF 2.0 differs from the 2024 draft on B2C. Invoices to private consumers are optional in KSeF, not mandatory. Most retailers will continue to issue traditional invoices or fiscal receipts (printed or via fiscal cash register) and will not push B2C invoices through KSeF at all. The reason is practical: consumers have no KSeF account and no way to retrieve an invoice from the platform. Sellers who do choose to push B2C through KSeF must still hand the buyer a copy by another channel, typically email PDF or printed paper with a QR code.

For SaaS sellers who treat individual subscribers as B2C, this means KSeF does not change your B2C invoicing flow if your fixed establishment is in Poland. You can keep emailing PDFs. The compliance question for you is whether you are also generating B2B invoices to Polish business customers, which are in scope.

Nonresident sellers: the rule got narrower than people expected

For most of the 2024 to 2025 drafting period, the assumption among foreign sellers was: "I have a Polish VAT number, so I will be in KSeF". That assumption turned out to be wrong.

The Ministry of Finance clarified, and the final regulation confirmed, that a Polish VAT registration alone does not pull a nonresident into KSeF. The trigger is whether you have a Polish fixed establishment (stałe miejsce prowadzenia działalności, SMPD), and whether that establishment is involved in the specific supply. The fixed establishment test under EU VAT case law requires:

• Personnel and technical resources in Poland (not just a postal address or a passive warehouse).
• Sufficient permanence (not a one-off project office).
• Actual involvement of those resources in the underlying supply.

If your only Polish footprint is a VAT number for distance sales or a stock of goods stored by a Polish 3PL on your behalf, you are out of scope. You can keep issuing PDF invoices to Polish customers in any format you and they agree on. If you have a Polish subsidiary, a Polish branch, or staff in a Polish office that participates in the sale, you are in scope, the same as any Polish-established taxpayer.

Penalties: paused, but not forever

Poland left the legal obligation in place from 1 February 2026 but suspended fines through 31 December 2026. Specifically:

• From 1 Feb 2026 to 31 Dec 2026: no penalties for issuing outside KSeF, missing KSeF IDs, or late uploads from Offline24. The obligation stands; the enforcement does not.
• From 1 Jan 2027: penalties of up to 100% of the VAT shown on a non-compliant invoice (or 18.7% of the gross value on an invoice without VAT) apply per invoice, capped at PLN 27,000.
• From 1 Jan 2027: payment titles (the description on a bank transfer) for invoices in scope must include the KSeF ID. Banks will progressively reject non-compliant transfers above defined thresholds.

The grace period is not a delay of the mandate. If you are issuing PDF invoices to Polish business customers today and waiting for January, you have less than eight months to be live, tested, and stable.

What the rollout has actually felt like

Three months in, the practical issues we are seeing in the market cluster around four areas:

1. NIP validation rejections. The strict counterparty validation in FA(3) catches buyer NIPs that are technically valid but inactive, or formatted with country prefix where the schema expects bare digits. Build a pre-flight check in your invoicing pipeline rather than discovering rejections after the fact.
2. Credit notes (faktury korygujące). Corrections must reference the original invoice's KSeF ID, not the supplier's internal number. Legacy systems that cancelled an invoice and reissued from scratch need a rework: the corrective invoice flow is different.
3. Currency and exchange rate. FA(3) requires invoices in foreign currency to declare the exchange rate source and date. The default is the National Bank of Poland (NBP) average rate from the working day preceding the invoice date. Other rates require justification fields.
4. Authentication for software. KSeF supports several authentication methods: qualified electronic signature, qualified electronic seal (the right answer for most ERP-to-KSeF integrations), trusted profile, and token-based authentication for software. Provisioning the right credentials for each operating environment (production, test, disaster recovery) takes longer than teams expect.

How KSeF intersects with ViDA and EU cross-border

KSeF is a Polish domestic system. It does not, by itself, generate the structured EU cross-border invoices that ViDA will require from 1 July 2030. The two regimes will coexist:

• Poland to Poland B2B: KSeF in FA(3).
• Poland to other EU member state B2B (intra-Community): KSeF for the Polish leg, plus an EN 16931 invoice and 5-day digital reporting under ViDA from July 2030.
• Other EU member state to Poland B2B (intra-Community acquisitions): the Polish recipient does not push the supplier's invoice into KSeF; the EU supplier complies with its own national mandate.

By 1 January 2035, ViDA requires national systems including KSeF to accept EN 16931 inbound, so the FA(3) schema will get another revision before the decade is out. None of that is in 2026 scope.

Action checklist: what to do this quarter

1. Confirm whether you are in scope. Polish establishment? Polish staff involved in the sale? If yes for either, you are in. If your only Polish footprint is a VAT registration for remote sales, document the analysis and keep a PDF flow.
2. Migrate any FA(2) integration to FA(3). Treat it as a schema upgrade, not a flag flip. Re-test invoice templates, credit notes, and corrections end to end.
3. Decide on a KSeF authentication model. Most ERP integrations use a qualified electronic seal. Provision separate credentials for production and test, and document the credential renewal schedule. Qualified seals expire.
4. Build the KSeF ID into your AR ledger. Store it next to your invoice number. From January 2027, your bank transfers will need it.
5. Train AP. Inbound invoices arrive through KSeF, not by email. Your AP team needs to fetch them, match to POs, and not double-pay if a vendor sends a courtesy PDF as well.
6. Use the grace period. Eight months without fines is enough to fix issues you find in production. It is not enough to start the project from scratch.

Frequently asked questions

When did KSeF become mandatory in Poland?

1 February 2026 for large taxpayers (2024 sales above PLN 200 million), 1 April 2026 for all other Polish-established taxpayers above the micro threshold, and 1 January 2027 for micro-enterprises. Receiving KSeF invoices has been mandatory for every Polish VAT-registered business since 1 February 2026.

Do nonresident foreign sellers have to use KSeF?

Only if they have a Polish fixed establishment that participates in the specific supply. A Polish VAT registration alone does not trigger KSeF. Foreign companies operating into Poland purely from abroad continue to issue invoices in any agreed format.

What is the FA(3) schema?

The structured XML schema that replaced FA(2) on 1 February 2026. It is Poland's national CIUS based loosely on EN 16931, with country-specific fields, attachment support, expanded code lists, and tighter counterparty validation.

What happens if I issue a non-KSeF invoice during 2026?

Penalties are paused until 1 January 2027. The legal obligation still exists. From 2027, fines reach 100% of the VAT shown on a non-compliant invoice (18.7% of gross if no VAT), capped at PLN 27,000 per invoice.

Can I keep issuing PDF invoices to Polish business customers?

If you have a Polish fixed establishment that is involved in the supply, no, those invoices must go through KSeF. If you are a pure nonresident with no Polish establishment, yes, PDF (or any other agreed format) remains valid.

What about B2C?

Optional. Most B2C continues on traditional invoices or fiscal receipts. KSeF supports B2C if you choose to use it, but you still have to deliver a copy to the consumer by another channel.

Related reading

• E-Invoicing Requirements by Country: A 2026 Global Tracker
• ViDA in 2026: A Practical Compliance Roadmap
• VAT Invoice Requirements for SaaS by Country
• How to Fix a Mistake on a VAT Invoice (Credit Notes Explained)