Poland's KSeF mandate: what clearance invoicing changes

Clearance is a different animal from a network

Most European mandates use a network model: you send a structured document to your customer through an agreed transport, and the tax authority sees it later or in aggregate. Poland's KSeF is a clearance model. The invoice goes to the state platform, and it is the platform's acceptance that makes the document an invoice.

That inverts something businesses take for granted. Under a network model, an invoice exists when you issue it and transmission is a delivery problem. Under clearance, an invoice that the platform has not accepted is not an invoice yet, whatever your system shows.

The rollout runs through 2026, with large taxpayers moving first in February and the remainder following in April, which means many businesses will be dealing with counterparties on both sides of the line for part of the year.

What changes operationally

Invoice numbering stops being entirely yours. The platform assigns its own identifier, and reconciling that against your internal numbering is a real piece of work that surprises finance teams who assumed their sequence was authoritative.

Timing changes. There is a moment between submission and acceptance, and processes that assumed instant issuance need to accommodate it — particularly anything that triggers on invoice creation, like dispatch or service activation.

Failure changes. A rejected submission is not a delivery failure to retry quietly; it means no valid invoice exists. That needs to be visible to a person, with a defined path, rather than sitting in a queue.

The integration question

Most businesses will connect through their accounting or ERP vendor rather than directly. That is usually right, but it is worth asking the vendor specific questions: how are rejections surfaced, how is the platform identifier stored and reportable, what happens during a platform outage, and how are attachments or annexes handled.

Businesses with their own invoicing logic — utilities, subscription platforms, anything issuing at volume — face a genuine integration project rather than a configuration exercise, because the clearance step has to be woven into a flow that previously ended at "send".

For high-volume issuers, throughput and error handling matter more than format. A thousand invoices a day means a rejection rate of even one per cent is ten problems a day that someone has to work.

Cross-border and the practical edge cases

The mandate centres on domestic B2B transactions, and businesses trading across borders will run parallel processes for a while — clearance domestically, other arrangements elsewhere. Anyone treating this as "we have moved to e-invoicing" and switching everything is likely to break something.

Foreign entities registered for VAT in Poland need to establish their own position, and that is a question for a Polish tax adviser rather than a software decision.

The general lesson for anyone with Polish operations is that the invoice is no longer purely an internal artefact. It is a document the state has seen and acknowledged, and the internal system is no longer the only source of truth.

What to check before the deadline that applies to you

Which wave you are in, because large taxpayers and everyone else moved on different dates. Whether your software connects directly or through a provider, and what that provider does on rejection and on outage. Whether anything downstream triggers on invoice creation and would break if creation became a two-step event.

Whether your customer and product data will pass validation, which is the same underlying question every mandate in Europe asks.

And who owns the exceptions, daily. That is the role that does not exist in most finance teams before a clearance mandate and is obviously necessary the week after.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Complete Digital Transformation — The whole stack, sequenced — brand, web, marketing, CRM, automation, reporting and infrastructure — with benefits measured afterwards rather than projected and forgotten.
• The EU AI Act: what actually applies from 2 August 2026
• Belgium's B2B e-invoicing mandate: the January 2026 big bang
• AI for custom customer care: what it can answer and what it must not
• When to build software instead of buying it
• All insight articles