Poland Defers KSeF E-Invoicing Fines Until 2028

Poland's Ministry of Finance announced on September 16, 2026 that it will delay financial penalties for KSeF e-invoicing errors a second time, with a formal draft act (UD477) published on September 22 confirming the new enforcement start date. If you're running EDI or B2B integration for a company that trades with Polish suppliers or customers, here's the part that matters: Draft Bill UD477 would postpone the application of specified KSeF financial penalties from 1 January 2027 to 1 January 2028. That's a deferral of fines, not a deferral of the mandate. The obligation to issue and receive invoices through KSeF hasn't moved an inch.

What the Ministry actually changed

Before this announcement, penalties for incorrectly issuing invoices, for example in a non-structured format or outside of KSeF, were due to take effect on January 1, 2027, and the draft act postpones their introduction until January 1, 2028. Those fines aren't trivial when they do land: penalties may reach up to 100% of the tax shown on the invoice, or for invoices without tax, up to 18.7% of the total amount due. This is the second time Warsaw has pushed the penalty clock back, and the Ministry has been explicit that it's responding to pressure. The additional transition period responds to requests from businesses, industry organizations and tax experts following the phased introduction of mandatory KSeF.

Don't read "no fines" as "no enforcement." Where a taxpayer does not use KSeF despite being required to do so, the National Revenue Administration would first individually inform the taxpayer, and if the taxpayer fails to react, authorities could then verify whether the failure is connected with incorrect or unreliable tax settlements. KAS keeps its teeth for 2027. It just isn't reaching for fines first.

What hasn't changed: the mandate dates still stand

This is the point most finance-department summaries bury. After a postponement in 2024, the implementation follows a phased approach based on taxpayer size: large businesses with annual turnover exceeding PLN 200 million in 2024 must comply starting 1 February 2026, all other businesses by 1 April 2026, and businesses with monthly sales under PLN 10,000 have until 1 January 2027. Those dates for large and mid-size taxpayers have already passed. If your Polish trading partners fall into either bucket, they should already be live.

Two transitional reliefs also expire on their original schedule, deferral or no deferral:

• Small-business paper/e-invoice relief: small businesses may keep issuing paper or other electronic invoices until 30 Sep 2026 — already closed by the time you read this.
• Offline24 mode: offline mode is permitted until 31 Dec 2026 where KSeF is unreachable, after which issuers lose that fallback entirely.
• Token authentication: originally set to sunset, but token authentication was made permanent, with its 31 Dec 2026 sunset removed — one rare piece of good news for integration teams that built on tokens rather than qualified certificates.
• Micro-entrepreneurs: the smallest taxpayers join KSeF from 1 January 2027, with monthly turnover under PLN 10,000 — this date did not move at all.

Key KSeF dates at a glance

Why an EDI team should care about a tax deferral

Because KSeF isn't a tax form, it's a mandatory clearance channel sitting on top of (or replacing) whatever INVOIC or 810-equivalent flow you already run with Polish partners. It's a clearance model: an invoice does not legally exist until KSeF has accepted it. That changes your error-handling logic, not just your compliance checklist. A rejected FA(3) submission isn't a warning to clean up later, it's a blocked transaction.

The FA(3) schema itself has been through several rounds of hardening since publication. FA3 schema enhancements introduced expanded fields for VAT groups, government units, employee expenses, and a new optional attachment element for structured XML attachments on complex invoices. If your mapping was built against early draft documentation, re-validate it against the current XSD before you trust production output. Vendors including Comarch, Sovos, and EDICOM have published detailed KSeF integration guidance as this has moved from a niche Polish requirement to a mainstream line item on EU compliance roadmaps, alongside France's and Belgium's own structured-invoicing pushes.

The freight and procurement angle

This isn't only an AP problem. Any freight, logistics, or procurement invoice from a Polish carrier or supplier now has to clear KSeF before it's legally valid for VAT purposes, which touches carrier invoice reconciliation and freight audit workflows directly. If you run a TMS or a multi-carrier platform like Cargoson, check whether your Polish carrier invoice ingestion path still assumes a legacy PDF or EDI feed instead of KSeF-cleared data with its own reference number and status lifecycle.

What to do before January 2027

• Confirm FA(3) schema mapping is validated against the current XSD in production, not just tested against last year's draft.
• If you're still issuing on authentication tokens, you can stay there — the planned certificate-only cutover didn't happen.
• Check that your offline-mode fallback logic gets retired cleanly after December 31, 2026, so it doesn't silently swallow failed transmissions in January.
• Don't deprioritize onboarding your smallest Polish partners just because penalties are deferred — their mandate date is January 1, 2027, unchanged.

Treat 2027 as a grace year for mistakes, not for missed integration work. The clearance obligation was never delayed, only the cost of getting it wrong.