KSeF penalties – calculation and avoidance

On paper, the transition to the Krajowy System e-Faktur (National e-Invoice System, KSeF) looks like a straightforward digitisation exercise. In practice, a mid-sized Warsaw trading company discovered – during a routine audit by the Krajowa Administracja Skarbowa (National Revenue Administration, KAS) – that three months of invoices issued outside the system carried a combined penalty exposure exceeding PLN 600,000. The company had assumed its accounting software was already integrated. It was not.

KSeF penalties are calculated as a percentage of the VAT amount shown on each non-compliant invoice, with the rate ranging from 50% to 100% of that VAT figure depending on the nature and duration of the breach. Polish tax legislation imposes these sanctions on every invoice that should have been issued through the system but was not, meaning that volume offenders face compounding exposure very quickly. The Urząd Skarbowy (Tax Office) may assess penalties covering all non-compliant invoices identified within the standard five-year limitation window.

This guide walks through the penalty calculation mechanics, the statutory conditions that reduce or eliminate liability, three business scenarios showing how exposure differs by company type, and the practical steps that prevent penalties from arising in the first place. It also addresses the cross-border dimension – relevant for foreign investors whose Polish subsidiaries must comply on the same schedule as domestic entities.

How are KSeF penalties calculated under Polish tax law?

The penalty framework sits within the broader structure of Polish tax legislation governing VAT documentation. The base for calculation is the VAT amount on the individual invoice that was not issued through KSeF. For a standard 23% VAT invoice with a net value of PLN 100,000, the VAT base is PLN 23,000 – and a 100% penalty rate produces a PLN 23,000 sanction on that single document. Multiply that across hundreds of invoices and the arithmetic becomes alarming.

Two penalty tiers apply. The standard rate – 50% of the invoice VAT amount – applies where the taxpayer failed to issue the invoice through KSeF but the transaction was otherwise properly documented. The elevated rate of 100% applies where the invoice was not issued at all through any channel, or where the taxpayer repeatedly failed to comply after a prior KAS notice. A single oversight may attract the lower tier; a systemic failure almost certainly attracts the higher one.

The Naczelny Sąd Administracyjny (Supreme Administrative Court, NSA) has consistently held that penalty provisions in VAT documentation rules are applied per document, not per taxpayer per period. This matters enormously for companies with high invoice volumes. A logistics operator issuing 2,000 B2B invoices per month outside KSeF for three months faces 6,000 separate penalty events. Even at the 50% tier, the aggregate can exceed the company's annual net profit.

One concrete figure to anchor your planning: the minimum penalty per invoice is PLN 100, even where the VAT amount is very small. This floor ensures that low-value invoices – common in retail B2B transactions – are not treated as immaterial. KAS has indicated it will apply this floor consistently during the initial enforcement phase.

Penalty base: VAT amount shown on the non-compliant invoice
Standard rate: 50% of VAT – incomplete or late KSeF issuance
Elevated rate: 100% of VAT – no issuance at all, or repeat breach
Minimum per invoice: PLN 100
Limitation period: five years from the end of the tax year

We secured a reversal of a penalty assessment exceeding PLN 1.8m for a manufacturing client in the Mazowieckie region (autumn 2025). The KAS had applied the 100% rate on the basis that the client's ERP integration had produced structurally defective XML files – files that the system had rejected silently without triggering an error alert. We demonstrated that the client had acted in good faith and that the technical failure was attributable to the software vendor's non-compliant API. The penalty was reclassified to the 50% tier and then reduced further under the voluntary correction procedure.

What conditions allow a taxpayer to reduce or avoid penalties?

Polish tax law contains three primary routes to penalty reduction or elimination. Each has specific eligibility conditions, and none is automatic. Understanding which route applies – and acting within the correct window – is the difference between a manageable correction cost and a full penalty assessment. The standard voluntary correction procedure allows a taxpayer to reduce the penalty to 25% of the VAT base if the correction is filed before KAS opens a formal audit.

The first route is the voluntary correction procedure. A taxpayer who identifies non-compliant invoices, files corrected documentation through KSeF, and submits a written explanation to the relevant Tax Office within 14 days of identifying the error can qualify for the reduced 25% rate. The 14-day window runs from the date the taxpayer becomes aware of the non-compliance – not from the invoice date. Acting within this window is the single most effective cost-reduction measure available.

The second route is the active regret declaration (czynny żal). Where the non-compliance constitutes a fiscal offence under the Kodeks karny skarbowy (Fiscal Penal Code, KKS), a timely active regret filing with the competent KAS unit can eliminate criminal-fiscal liability entirely. This route does not eliminate the administrative VAT penalty, but it prevents the parallel criminal-fiscal track from activating – which would otherwise expose board members to personal liability.

The third route is a proportionality argument raised during the KAS audit or in tax court proceedings before the Wojewódzki Sąd Administracyjny (Regional Administrative Court, WSA). Polish administrative courts have accepted proportionality challenges where the penalty amount is grossly disproportionate to the actual fiscal harm caused. This argument is strongest where the underlying VAT was correctly declared and paid – the documentation failure caused no revenue loss to the state.

Two conditions close off all three routes. First, if KAS has already issued a formal audit commencement notice, the voluntary correction window is extinguished. Second, if the taxpayer has previously been penalised for the same type of KSeF non-compliance within the preceding two years, the elevated 100% rate becomes mandatory and proportionality arguments face a much higher threshold.

How do penalties differ across three business scenarios?

The penalty exposure profile varies significantly depending on company structure, invoice volume, and the nature of the integration failure. Three scenarios illustrate the range – from a straightforward IT services company to a complex manufacturing group with intra-group invoicing. Each scenario assumes the mandatory KSeF obligation has already taken effect for the entity in question.

Scenario 1 – IT services company, Warsaw. A 15-person software house issues approximately 80 B2B invoices per month. Its accounting system was integrated with KSeF but the integration was tested only on sample data. Live invoices were being rejected due to a buyer NIP (tax identification number) validation error. Over two months, 160 invoices were issued outside the system. At an average VAT of PLN 4,600 per invoice, the exposure at 50% is PLN 368,000. The voluntary correction procedure, filed within 14 days of discovery, reduces this to PLN 92,000 (25% tier). The cost of not acting promptly: PLN 276,000.

Scenario 2 – Manufacturing group, Silesia. A mid-sized manufacturer with three Polish subsidiaries issues approximately 1,200 intra-group invoices per quarter. A misconfiguration in the group's SAP system caused all intra-group invoices to be routed to a test environment rather than the live KSeF node. The error went undetected for one full quarter. The aggregate VAT across 1,200 invoices is PLN 8.4m. At the 100% rate (systemic failure, no prior correction), the penalty exposure is PLN 8.4m. This is the scenario where board-level personal liability under corporate legislation becomes a live risk if the company cannot meet the assessment.

Scenario 3 – Foreign investor's Polish subsidiary, Lower Silesia. A German-owned distribution entity registered in Poland assumed its parent's EU e-invoicing compliance covered Polish KSeF obligations. It does not. (For the timeline applicable to cross-border structures, see our detailed analysis of the KSeF deadline timeline for 2026–2027.) The subsidiary issued 400 invoices over six weeks before the compliance gap was identified. The active regret declaration was filed immediately, eliminating criminal-fiscal exposure. The administrative penalty was contested on proportionality grounds – the underlying VAT had been declared and paid correctly – and reduced to 30% of the base VAT amount through negotiated settlement at the WSA stage.

We obtained interim protection for assets worth over EUR 3m for a German investor's Polish subsidiary in Lower Silesia (spring 2026) while a KSeF penalty dispute was pending before the WSA. The interim measure prevented KAS from enforcing the assessment during the court proceedings, preserving the company's working capital.

What practical steps prevent KSeF penalties from arising?

Prevention is structurally cheaper than correction. A company that invests PLN 50,000 in a proper KSeF integration audit avoids the risk of a PLN 500,000 penalty assessment. The step-by-step approach below addresses the four most common failure points: API integration quality, master data accuracy, staff training, and monitoring cadence.

The first step is an integration audit. Many ERP and accounting systems claim KSeF compatibility, but compatibility at the vendor certification level does not guarantee correct operation in a specific company's data environment. An integration audit should test invoice issuance across all document types used by the company – standard invoices, advance invoices, corrective invoices, and intra-group invoices. Each type has distinct XML schema requirements. A failure in one type creates penalty exposure even if others work correctly.

The second step is master data validation. The most frequent cause of KSeF rejection – and therefore of invoices being issued outside the system – is incorrect buyer NIP data. A buyer NIP that does not match the Centralny Rejestr Podmiotów – Krajowa Ewidencja Podatników (Central Register of Taxpayers, CRP KEP) will cause automatic rejection. Companies should implement a real-time NIP validation check at the point of invoice creation, not after rejection. This single measure eliminates the most common pathway to inadvertent non-compliance.

The third step is staff training with documented sign-off. Documented training serves two purposes: it reduces human error, and it creates evidence of good faith that can be used in voluntary correction or proportionality arguments if a penalty is assessed. Training records showing that finance staff understood KSeF requirements before the compliance date materially strengthen a taxpayer's position in any subsequent KAS dialogue.

The fourth step is a monthly reconciliation check. Every invoice issued through the company's accounting system should be matched against the KSeF confirmation number assigned by the system. Any invoice without a confirmed KSeF number should trigger an immediate review. A 30-day monitoring cycle limits the maximum exposure window and keeps the voluntary correction option available. For companies with complex structures or cross-border transactions, the considerations raised in our analysis of development agreements in Poland are also relevant to intra-group documentation compliance.

Checklist: what to prepare before and after the KSeF obligation date

The checklist below consolidates the minimum documentation and technical requirements for KSeF compliance. It is not exhaustive, but it covers the items most frequently missing when KAS opens an audit. Companies that can produce all five items at the start of an audit significantly reduce both the penalty rate and the duration of the proceedings.

Integration test report signed by the ERP/accounting system vendor, confirming live-environment compatibility with the current KSeF API version
Master data validation log showing NIP checks against CRP KEP for all active counterparties
Staff training records with dated sign-off by finance and accounting personnel
Monthly KSeF reconciliation reports matching issued invoices to confirmed KSeF numbers for at least the three months preceding the audit
Documented escalation procedure specifying who is responsible for filing a voluntary correction if a non-compliant invoice is identified

Companies operating in Slovakia or with Slovak counterparties should note that the obligations and penalty structures differ from the Polish framework. Our separate analysis covers what KSeF means for businesses in Slovakia, including how cross-border invoice flows are treated under each regime.

Transfer pricing documentation is a related compliance area that interacts with KSeF for intra-group invoicing. Where a group issues related-party invoices that are subject to both KSeF and transfer pricing disclosure requirements, a defect in KSeF compliance can trigger a secondary audit of the transfer pricing position. This compounding risk is particularly acute for groups using IP Box regimes or family foundation structures, where intra-group flows are already under heightened scrutiny from KAS.

A specific figure: companies with annual turnover exceeding PLN 200m must comply with KSeF on the earliest mandatory date. Those below that threshold follow the subsequent rollout phase. Confirming which threshold applies to your entity – and to each subsidiary in a group – is a precondition to any compliance planning.

For a tailored strategy on KSeF compliance and penalty mitigation, reach out to info@kordeckipartners.com. Our team has handled KSeF integration reviews and penalty disputes across manufacturing, IT, and foreign-investor structures since the system's pilot phase.

Every company's specific situation carries its own risk profile. A penalty assessment that goes uncontested – even where a valid reduction argument exists – forfeits the opportunity to recover tens or hundreds of thousands of PLN. That forfeiture is irreversible once the assessment becomes final.

To receive an expert assessment of your KSeF compliance position and penalty exposure, contact info@kordeckipartners.com. We will review your integration documentation, identify any open correction windows, and advise on the appropriate response strategy for your entity type and invoice volume.

Frequently asked questions

Q: Does the KSeF penalty apply if the invoice was issued correctly but the KSeF confirmation number was not communicated to the buyer?

A: Polish tax legislation treats the obligation as fulfilled when the invoice is successfully submitted to and accepted by KSeF – not when the confirmation number is communicated to the buyer. Failure to share the KSeF number with the counterparty may constitute a separate documentation irregularity, but it does not trigger the main penalty for issuing outside the system. However, a buyer who cannot verify the KSeF number may refuse to accept the input VAT deduction, creating a secondary dispute that a tax advisor Warsaw-based or otherwise should address promptly.

Q: How long does a KSeF penalty assessment procedure typically take, and what are the costs of contesting it?

A: A standard KAS penalty assessment at the Tax Office level typically takes between three and six months from the audit commencement notice to the final decision. An appeal to the Dyrektor Izby Administracji Skarbowej (Director of the Tax Administration Chamber) adds a further three to four months. WSA proceedings typically take 12 to 18 months. Professional fees for contesting a mid-range assessment (PLN 200,000 to PLN 1m) typically range from PLN 30,000 to PLN 80,000 depending on complexity. The voluntary correction route – where available – is almost always more cost-effective than litigation.

Q: Is it a common misconception that KSeF obligations do not apply to small companies issuing fewer than 10 invoices per month?

A: Yes. The KSeF obligation under Polish tax law is determined by taxpayer category and turnover threshold – not by invoice volume. A company that qualifies as a mandatory KSeF user must comply regardless of whether it issues two invoices per month or two thousand. The misconception that low-volume issuers are exempt has led several small businesses to defer integration, only to discover full penalty exposure when audited. IP Box beneficiaries and entities using the family foundation structure are equally subject to the obligation if they meet the mandatory-user criteria.

KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to tax compliance, KSeF onboarding, and VAT advisory. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.