When do KSeF penalties start in Poland?

Penalties under art. 106ni of the Polish VAT Act apply from 1 January 2027. Paragraphs 1 to 3 and 5 to 7 begin to be applied on that date; paragraph 4, which governs the relationship with criminal proceedings, has applied since 1 February 2026. The whole of 2026 is a transitional period in which no penalty is imposed for issuing outside KSeF or for errors, but the obligation itself has been in force since 1 February 2026 for the largest taxpayers and since 1 April 2026 for everyone else.

Is a foreign company with a Polish branch in scope of KSeF?

It depends on whether the Polish presence is a fixed establishment that participates in the supply. Art. 106ga ust. 2 of the Polish VAT Act excludes a taxpayer with neither a seat nor a fixed establishment in Poland, and also a taxpayer with a fixed establishment that does not participate in the supply for which the invoice is issued. A foreign-established company whose Polish fixed establishment does participate must issue through KSeF. The Ministry of Finance issued objasnienia podatkowe on 28 January 2026 setting out how to determine this.

How much is the penalty for issuing an invoice outside KSeF?

Up to 100% of the amount of tax shown on the invoice, or up to 18.7% of the total amount due where no tax is shown. Both figures are statutory ceilings, not fixed rates. The authority is obliged to calibrate the penalty under art. 189d of the Kodeks postepowania administracyjnego, taking into account the gravity and circumstances of the breach, how often it occurred and the party's previous conduct.

Do Polish micro-entrepreneurs have a KSeF deferral to 2027?

No. Micro-entrepreneurs came into the obligation on 1 April 2026 on the same terms as every other taxpayer. The private members bill that would have excluded them until 31 December 2027, Sejm druk nr 2321, stalled after its first reading on 13 March 2026 and was never enacted. It is nonetheless cited as binding law in advisory material, so a group relying on a Polish adviser should check which of the two it is being told about.

Can a structured invoice be deleted from KSeF?

No. Once KSeF accepts a faktura ustrukturyzowana it assigns a numer KSeF, and from that point the document can be corrected but never deleted. A duplicate created by an unguarded retry receives its own numer KSeF and can only be undone by issuing a correcting invoice. This is why controls in a KSeF integration have to run before submission rather than after it.

What evidence does a group need for an automated KSeF process?

At minimum: a complete log of every API call with a stable operation identifier, the numer KSeF and UPO bound to the source document, a register of offline-mode decisions with the basis for each, proof that idempotency controls prevented duplicate submissions on retry, and a record of who or what authorised the operation before it ran. The record must be reconstructable years later and resistant to retrospective modification, because its purpose is to support mitigation under art. 189d rather than to debug an incident.

KSeF penalties from 1 January 2027: up to 100% of tax

One point of standing before anything else. The binding text of the Polish VAT Act is the Polish one, published in the Dziennik Ustaw. This page is a working guide for a reader who does not read Polish; where it matters, check the instrument, and where the two diverge the Polish text governs.

What changes on 1 January 2027?

Four things end or begin on the same date, and a group planning a single change window should treat them as one release rather than four.

Penalties under art. 106ni. Paragraphs 1 to 3 and 5 to 7 begin to be applied. Only paragraph 4, which governs the relationship with criminal proceedings, has been in force to date, since 1 February 2026.
The PLN 10,000 transitional relief expires. Taxpayers whose monthly in-scope sales did not exceed PLN 10,000 gross have been able to invoice outside KSeF since 1 April 2026. The relief ends on 31 December 2026.
The numer KSeF becomes a payment field. Art. 108g requires the KSeF number to appear in the payment reference for a faktura ustrukturyzowana (structured invoice). This lands on the treasury and payments side of a group, not the invoicing side, and it is the change most often missed in a cross-border implementation plan.
Cash-register invoicing in B2B ends, and a receipt bearing a NIP up to PLN 450 stops counting as a simplified invoice.

There is a fifth date worth having on the same slide, and it is not Polish. Poland's mandate rested on Council Implementing Decision (EU) 2022/1003 of 17 June 2022, which authorised a derogation from Articles 218 and 232 of Directive 2006/112/EC and expires on 31 December 2026. From 1 January 2027, Council Directive (EU) 2025/516 of 11 March 2025 — the VAT in the Digital Age package — inserts a second paragraph into Article 218 permitting a Member State to require electronic invoices from taxable persons established within its territory without a Council authorisation, and amends Article 232 so that recipient acceptance need not be sought. The derogation does not lapse and leave a gap; the general power replaces it on the day after. The wording of that general power is also the reason the Polish scope rule looks the way it does.

Which entities in a group are actually in scope?

This is the question a group tax function has to answer first, and it is not answered by asking which entities hold a Polish VAT number.

Art. 106ga ust. 1 of the VAT Act imposes the obligation to issue structured invoices through KSeF. Art. 106ga ust. 2 carves out, among others, a taxpayer that has neither a seat nor a fixed establishment in Poland, and a taxpayer without a Polish seat whose fixed establishment in Poland does not participate in the supply for which the invoice is issued. Read the two together and the operative test for a foreign-established company is not registration but participation.

The Ministry of Finance consulted on draft objaśnienia podatkowe (official tax explanations) on this precise point between 31 December 2025 and 14 January 2026, and published the final version dated 28 January 2026. Three things in it matter to a group:

A Polish VAT registration is not a fixed establishment. Article 11(3) of Council Implementing Regulation (EU) No 282/2011 says so directly, and the Polish analysis follows it. Establishment requires a sufficient degree of permanence and a suitable structure of human and technical resources.
Participation is tested by whether those resources are used for the supply. The framework is Article 53 of Regulation 282/2011: a fixed establishment is not regarded as intervening unless its technical and human resources are used for transactions inherent in fulfilling the supply, before or during its completion.
Administrative support is expressly not participation. Article 53(2) states that where the resources of the fixed establishment are used only for administrative support tasks such as accounting, invoicing and the collection of debt-claims, they are not regarded as used for the fulfilment of the supply. A shared service centre in Kraków or Wrocław that books and bills for a group but does not perform the supply is, on that wording, doing administrative support. There is a counterweight in the same article: where an invoice is issued under the VAT identification number of the fixed establishment's Member State, that establishment is presumed to have intervened unless the contrary is shown.

The practical consequence is uncomfortable for a group that likes clean answers. Two entities with identical Polish VAT registrations can fall on opposite sides of art. 106ga ust. 2 depending on what their Polish people and equipment actually do. That determination is a documented judgement, not a checkbox, and it should be written down at the entity level, dated, and revisited when the operating model changes. The objaśnienia state that a taxpayer who complies with them in a given settlement period is protected under art. 14k to 14m of the Ordynacja podatkowa by virtue of art. 14n § 4 pkt 1 — which means the reasoning is worth recording in the form the explanations contemplate, not merely reaching.

How large is the penalty, and can it be reduced?

The two figures — 100% of the tax shown and 18.7% of the total amount due where no tax is shown — are ceilings. The Ministry of Finance has consistently declined to lower them, on the ground that a moderating mechanism already exists: art. 189d of the Kodeks postępowania administracyjnego obliges the authority to take into account, among other things, the gravity and circumstances of the breach, how often it occurred, and the party's previous conduct.

That is the sentence on which the whole documentation argument turns. A submission that the breach was isolated, arose from a system failure, was detected internally and was remedied within a day is worth precisely as much as your ability to prove it with a record that could not have been assembled afterwards. A group finance function that can produce that record in an hour is in a materially different position from one that can produce a narrative.

Separately, liability under the Kodeks karny skarbowy (art. 62 and following) for defective or unreliable invoicing is not covered by the transitional period and has applied throughout. A group should not read 2026 is penalty-free as 2026 carries no exposure.

What does a group finance function have to do differently?

A domestic Polish filer and a group finance function in London, New York or Frankfurt face the same statute and a different problem. Five differences are worth planning around.

The obligation and the penalty attach to the Polish taxpayer, not to the group. There is no group filing and no consolidated discharge. If three entities in the structure are in scope, three sets of evidence exist, and a group process that treats Poland as one integration will produce evidence that cannot be attributed to a single taxpayer when the tax office asks.
Scope has to be re-determined, not inherited. The fixed-establishment test in art. 106ga ust. 2 is sensitive to changes in the operating model — a warehouse taken on, staff moved into a local entity, a supply chain re-routed. Whoever owns transfer pricing or permanent-establishment analysis in the group is usually closer to this than the e-invoicing project team.
The evidence has to survive translation. An inspection is conducted in Polish. An audit trail whose field names, decision reasons and approval records exist only in English is usable, but it will be read by someone reconstructing your process from a schema they have never seen. Bilingual field definitions and a written control description in Polish cost little now and a great deal in the middle of an inspection.
The person who approves has to be identifiable. A group approval workflow that records a role, a queue or a service account satisfies nobody. Record the individual.
Payment operations change on the same date as the penalties. The art. 108g requirement to carry the numer KSeF in the payment reference reaches banking and treasury systems that are usually outside the KSeF project's scope and often outside Poland. Sequencing this after the invoicing work is the most common planning error.

Do Polish micro-entrepreneurs have a deferral to 2027?

No. Micro-entrepreneurs within the meaning of art. 7(1)(1) of the Prawo przedsiębiorców came into the obligation on 1 April 2026, on the same terms as everyone else. A private members bill that would have excluded them until 31 December 2027 — Sejm druk nr 2321, introduced on 13 February 2026 — stalled after its first reading on 13 March 2026 and was never enacted.

The distinction matters for a group because the bill is still cited as binding law, including in advisory material. If a Polish subsidiary or its local accountant has told you that its smaller entities are outside the mandate until 2027, ask which instrument that comes from. See the library's register of corrections.

Can a structured invoice be withdrawn once it is accepted?

No. When KSeF accepts a faktura ustrukturyzowana it assigns a numer KSeF, and from that moment the document can be corrected but never deleted. A duplicate produced by an unguarded retry after a timeout is not a technical artefact that can be cleaned up; it is a second invoice with its own numer KSeF, and unwinding it means issuing a correcting invoice and explaining why.

This is the single fact that determines where controls belong. Monitoring will tell you that a process issued three hundred defective documents. A control that runs before submission means it issues none. That is the argument for approval thresholds ahead of submission rather than reconciliation afterwards, and it is the same argument the library makes for approving AI actions before execution.

What evidence proves an automated process was compliant?

Five layers. None of them is purely technical, and each answers a question an inspection actually asks.

Pre-execution control. Before the operation runs, the system checks whether it is permitted: value, counterparty, document type, and whether the operation crosses a threshold requiring a human decision. See approval checkpoints.
Idempotency. Every operation carries an identifier, and a retry bearing the same identifier does not create a second document.
A tamper-evident audit trail. Who or what initiated the operation, with which parameters, at what time, with what result — bound to the numer KSeF and the UPO, and not alterable after the fact. The library's audit trail requirements for AI agents apply unchanged here.
A register of offline-mode decisions. The basis, the moment, the deadline that applies to that mode, and confirmation that transmission happened. The three states are not interchangeable — see offline24, awaria and niedostępność.
Reconstructability. The ability to rebuild the full history of a single invoice months later without reaching for application logs that have already rotated.

The fastest test of whether you have this

Pick a random invoice issued by a Polish entity three months ago and reconstruct the whole chain: what triggered it, with which parameters, who or what authorised it, what the result was, which numer KSeF and which UPO. If that takes more than a few minutes, or requires a developer, you have a working integration and no evidence. The cost of closing that gap is small next to a single penalty computed on a six-figure tax amount — the arithmetic is set out in what KSeF automation actually costs.

Where the operation is initiated by an AI agent rather than a deterministic job, two further fields belong in the record: which model and policy version were in force, and what the agent was shown before it acted. An agent's behaviour cannot be reproduced by re-running it later, which makes the contemporaneous record the only evidence there will ever be. AI governance covers that ground in general terms.

A 30-day preparation sequence

For every entity with a Polish VAT registration, determine whether it has a seat or a participating fixed establishment in Poland, and record the reasoning against the objaśnienia podatkowe of 28 January 2026.
Inventory every path by which an invoice can be created for an in-scope entity — batch processes, partner integrations, AI agents.
For each path, confirm it writes a durable link: source document, numer KSeF, UPO.
Test timeout behaviour in a pre-production environment. Confirm the retry produces one document, not two.
Confirm the migration to KSeF API 2.0 covered mandatory encryption in interactive mode as well as batch — it was optional in interactive mode under 1.0, and is the most common migration trap.
Set a hard stop for the PLN 10,000 threshold and test the behaviour on the invoice that crosses it. The right to the relief is lost from that invoice, and lost permanently.
Define approval thresholds: which automated operations require a human decision before execution.
Document the tryb offline24 procedure — who decides, on what basis, who monitors the transmission deadline.
Run the reconstruction test above on a random invoice.

In practice

BarzelVault applies policy and approval thresholds ahead of execution and issues signed audit receipts, which is the evidence layer an art. 189d submission depends on. BarzelOps runs the cross-system workflow with durable state, approval checkpoints and tenant isolation, so each Polish entity's operations stay attributable to that entity.

How Barzel applies here

Frequently asked questions

When do KSeF penalties start?

1 January 2027. Paragraphs 1 to 3 and 5 to 7 of art. 106ni begin to be applied then; paragraph 4, on criminal proceedings, has applied since 1 February 2026. 2026 remains free of penalties for issuing outside KSeF and for errors.

Is a foreign-established company in scope?

Only if it has a seat in Poland, or a fixed establishment in Poland that participates in the supply. Art. 106ga ust. 2 excludes a taxpayer with neither, and a taxpayer whose Polish fixed establishment does not participate. A Polish VAT registration alone is not a fixed establishment.

How much is the penalty?

Up to 100% of the tax shown on the invoice, or up to 18.7% of the total amount due where no tax is shown. These are ceilings; the authority must calibrate under art. 189d of the Kodeks postępowania administracyjnego.

Does the PLN 10,000 relief continue into 2027?

No. It ran only from 1 April to 31 December 2026. The right is lost from the invoice that crosses the threshold, and it is lost permanently — it does not return in a later month with lower sales.

Do micro-entrepreneurs have a deferral?

No. They came into scope on 1 April 2026. Sejm druk nr 2321 was not enacted.

Can an accepted invoice be deleted?

No. It receives a numer KSeF and can only be corrected. That is why controls have to sit before submission.

Where this leads

Until 31 December 2026 a defect in a KSeF integration is an operational problem. From 1 January 2027 it becomes a financial one, and its size depends on whether the organisation can demonstrate what happened. For a group, the additional work is not technical: it is deciding which entities are caught, recording why, and making sure the evidence produced by a shared platform can still be attributed to the individual Polish taxpayer that owes the duty.

In practice

The control has to run before the invoice becomes irreversible.

An accepted structured invoice can be corrected but never deleted, and from the penalty date every defect has a price. Barzel puts the approval threshold, the duplicate check and the signed record in front of submission, so the process can be defended on the day an auditor or the tax authority asks.

95 days leftKSeF penalties apply from 1 January 2027

BarzelVault

The AI action firewall: decide what an agent may do before it does it.

Approval thresholds and policy checks enforced before execution; human approvals that expire and escalate.
Cryptographically signed audit receipts: trigger, inputs, policy version, approver, outcome.
Credential isolation, spend and action limits, and an emergency kill switch.

Free tier: 10,000 calls a monthPaid plans from $199 a monthLive on MCPize

Start free Ask by email Product page Documentation

BarzelOps

Governed workflow automation across the systems that run the business.

Durable, idempotent execution: a timeout is retried once, never filed twice.
Human approval checkpoints that pause the workflow and resume it.
Isolation per entity or client, signed evidence receipts and a portable manifest; HubSpot, Xero, Gmail, Google Drive and Slack.

Free tier: 100 calls a dayPaid plans from $19 a monthLive on MCPize