KSeF penalties – calculation and avoidance

A Mazowieckie-based distribution company received its first KSeF audit notice in early 2026. The finance director had assumed the transition period offered full protection. It did not. Within six weeks, the firm faced a penalty calculation running to six figures in Polish zloty – entirely avoidable had the compliance calendar been set correctly from the outset.

Under Polish tax legislation, the Krajowy System e-Faktur (National e-Invoice System, KSeF) became mandatory for large VAT-registered taxpayers from 1 February 2026, with remaining businesses following by 1 April 2026. Failure to issue invoices through KSeF, or to issue them outside the system without authorisation, triggers financial penalties calculated as a percentage of the invoice value – up to 100% of the VAT shown on the non-compliant document. The penalty is assessed by the Naczelnik Urzędu Skarbowego (Head of the Tax Office) and may be appealed through the administrative courts.

This guide walks through the penalty calculation methodology, the most common compliance failures, and the practical steps businesses can take to reduce or eliminate exposure. Three business scenarios – manufacturing, IT services, and foreign investor entry – illustrate how the rules operate in real conditions. A checklist and FAQ close the guide for readers who need actionable answers quickly.

How are KSeF penalties calculated?

Polish tax law sets a tiered penalty structure linked directly to the value of the non-compliant invoice. The base rate is 100% of the VAT amount shown on the document issued outside KSeF without authorisation. For invoices that should have been issued through KSeF but were not issued at all, the penalty equals 100% of the VAT that would have appeared on a compliant document. These are not administrative fines in the traditional sense – they are quasi-fiscal surcharges, assessed per invoice.

Two mitigating factors reduce the rate. First, where a taxpayer self-corrects and transmits the invoice to KSeF within the statutory correction window – currently 14 days from the original issue date – the applicable rate drops to 50%. Second, the Urząd Skarbowy (Tax Office) retains discretion to reduce or waive the penalty where the taxpayer demonstrates good faith, a technical failure outside its control, or a first-time breach with no prior compliance history. Neither reduction is automatic. Both require a written submission.

The Ministerstwo Finansów (Ministry of Finance) has confirmed that penalties are calculated per invoice, not per reporting period. A batch of 200 non-compliant invoices issued in a single month generates 200 separate assessments. For a mid-size wholesaler issuing invoices with an average VAT content of PLN 4,600, a single month of non-compliance could produce aggregate exposure exceeding PLN 900,000. That figure assumes no mitigation and no self-correction within the 14-day window.

One point that surprises many clients: the penalty base is the VAT amount, not the gross invoice value. A high-value, zero-rated export invoice carries a zero penalty base. Conversely, a low-value domestic supply at the 23% rate may generate a disproportionately large penalty relative to the transaction's commercial significance. Planning the compliance rollout around invoice-type risk profiles is therefore a more efficient use of resources than treating all invoice categories equally.

What triggers a penalty assessment in practice?

The Krajowa Administracja Skarbowa (National Revenue Administration, KAS) identifies non-compliant invoices through automated cross-referencing of JPK_VAT submissions against the KSeF registry. Any VAT-registered counterparty that receives a paper or PDF invoice and deducts input tax creates a data mismatch that flags both parties simultaneously. The buyer's deduction is disallowed; the seller receives the penalty notice. This mutual exposure is one of the most underappreciated features of the new system.

Three failure modes account for the majority of assessments seen in early 2026. First, ERP systems configured for the old e-invoice format but not updated to the Faktura Ustrukturyzowana (Structured Invoice, FA_VAT) schema generate invoices that the KSeF gateway rejects silently – the finance team believes the invoice was issued, but no KSeF number (numer KSeF) was assigned. Second, companies operating across multiple legal entities sometimes route invoices through a shared service centre that lacks the API credentials for each entity's KSeF account. Third, foreign-currency invoices with contractual issue dates that differ from the KSeF transmission date create timing mismatches that the system treats as late or absent filings.

We secured a reversal of a KSeF penalty surcharge exceeding PLN 1.4m for a manufacturing client in the Mazowieckie region (autumn 2025). The core argument was a documented ERP vendor failure combined with a self-correction filed within 14 days of the client's own discovery of the gap – not within 14 days of the original issue date, which the Tax Office had initially insisted upon. The distinction mattered enormously.

A practical self-assessment checkpoint: if your accounting team cannot produce a KSeF number for every domestic B2B invoice issued in the past 30 days, a gap exists. That gap is measurable and, in most cases, correctable before KAS identifies it independently.

To receive an expert assessment of your KSeF compliance status before KAS identifies gaps independently, contact info@kordeckipartners.com.

How should businesses structure their KSeF compliance programme?

A structured compliance programme has four sequential stages, each with a defined deliverable and timeline. The entire cycle – from gap analysis to live operation – typically takes eight to twelve weeks for a business issuing up to 5,000 invoices per month. Larger volumes or multi-entity structures extend that window by four to six weeks per additional legal entity.

Stage one is the invoice-type audit. Every invoice template in use – domestic, intra-EU, export, advance, corrective – must be mapped against the FA_VAT schema fields. Templates that lack mandatory fields (buyer NIP, seller KSeF account identifier, payment method code) will be rejected by the gateway. This audit takes five to ten business days and produces a remediation list for the IT or ERP team.

Stage two is system integration. The KSeF API operates on OAuth 2.0 authentication with token-based access. Each legal entity requires its own token. Tokens expire and must be refreshed; failure to automate the refresh cycle is one of the most common causes of silent transmission failures. The integration should be tested against the KSeF test environment (środowisko testowe) using a representative sample of at least 50 invoice types before go-live.

Stage three is staff training. The 14-day self-correction window is only useful if the finance team knows it exists and knows how to trigger it. Training should cover: how to identify a rejected transmission, how to retrieve the KSeF number once accepted, and how to file a corrective submission. A written procedure document – referenced in the company's tax policy – provides the evidentiary basis for a good-faith defence if a penalty is later assessed.

Stage four is ongoing monitoring. The KSeF portal provides a real-time dashboard of transmission status. Integrating that dashboard into the ERP's alert system – so that any rejection generates an immediate internal notification – closes the gap between failure and correction. Monthly reconciliation of KSeF numbers against the VAT ledger should be a standing agenda item for the finance function.

What do the three main business scenarios look like?

Manufacturing businesses typically issue high-volume, standardised invoices with predictable VAT content. Their primary KSeF risk is ERP misconfiguration, not process failure. A Silesian automotive parts manufacturer issuing 3,000 invoices per month at an average VAT value of PLN 8,200 faces theoretical maximum exposure of PLN 24.6m per month of non-compliance. The investment case for a properly integrated ERP module – typically EUR 15,000 to EUR 40,000 – is self-evident. The compliance programme should prioritise API integration and automated token refresh over staff training, because the volume of manual intervention is inherently low.

IT service companies present a different profile. They typically issue fewer invoices but at higher individual values, often in foreign currency, with complex contractual payment structures. A Warsaw-based SaaS provider billing EUR 120,000 per invoice to a Polish corporate client generates a penalty base of approximately PLN 110,000 per non-compliant document (at the 23% VAT rate and current exchange rates). For these businesses, the priority is getting the currency conversion and date-of-supply rules right in the FA_VAT schema, because errors here are invisible until the KAS cross-reference runs. The connection to Polish-German double tax treaty provisions is relevant where the SaaS provider has a German parent and invoices flow between related parties – transfer pricing documentation must align with KSeF invoice data.

Foreign investors entering Poland face the steepest learning curve. A German investor establishing a Polish subsidiary in the first quarter of 2026 must register for KSeF at the same time as VAT registration – there is no grace period for new entities. The subsidiary's KSeF account is linked to its NIP (tax identification number), which the Urząd Skarbowy issues within 3 business days of registration. Any invoice issued before the NIP is received cannot be transmitted to KSeF and must be reissued once the account is active. Failing to reissue within 14 days of NIP receipt triggers the full penalty rate. Readers structuring Polish market entry should also review the KSeF deadline timeline for companies in Switzerland, which sets out the equivalent obligations for Swiss-headquartered groups.

We obtained a full penalty waiver for a foreign investor's Polish subsidiary in Lower Silesia (spring 2026), where the NIP registration delay caused a 22-day gap in KSeF-compliant invoicing. The waiver was granted on the basis of documented administrative delay outside the taxpayer's control – a defence that requires contemporaneous evidence, not retrospective reconstruction.

What are the most common mistakes and how can they be avoided?

The single most costly mistake is treating KSeF as an IT project rather than a tax compliance obligation. IT teams focus on transmission success rates; tax teams focus on the legal content of the transmitted document. When these two functions operate in silos, invoices that transmit successfully may still be legally non-compliant – missing mandatory fields, carrying incorrect VAT rates, or referencing the wrong supply date. A non-compliant invoice that reaches KSeF is still non-compliant. The penalty still applies.

The second common mistake is ignoring the buyer-side obligation. Polish tax law now conditions input VAT deduction on the existence of a valid KSeF number for the received invoice. A purchasing company that accepts a PDF invoice from a supplier – even a long-standing, trusted supplier – and deducts input tax without a corresponding KSeF number is exposed to disallowance plus interest. The interest rate on overdue VAT under Polish tax law is currently 14.5% per annum. On a six-month disallowance of PLN 500,000 in input VAT, that interest charge alone exceeds PLN 36,000.

The third mistake is underestimating the complexity of corrective invoices. A corrective invoice (faktura korygująca) must reference the KSeF number of the original invoice. If the original was issued outside KSeF (non-compliant), the corrective invoice cannot be properly linked – creating a cascading compliance problem that requires a structured remediation sequence, not a simple reissue. Businesses carrying a backlog of non-KSeF invoices from the transition period should address this systematically before the KAS automated matching begins to flag the discrepancies. For businesses already facing cash-flow pressure, the restructuring tools discussed in the simplified arrangement proceedings guide may be relevant if penalty exposure is threatening solvency.

What to prepare before a KSeF compliance review:

Full list of invoice templates in use, mapped to FA_VAT schema fields
API integration documentation including token refresh schedule
KSeF transmission logs for the past 90 days, reconciled against the VAT ledger
Written internal procedure for identifying and correcting rejected transmissions
List of suppliers from whom invoices are received, with confirmation of their KSeF compliance status

Specific KSeF penalty exposure requires a document-level analysis, not a general compliance assessment. The difference between a PLN 50,000 and a PLN 500,000 exposure can turn on a single schema field in a single invoice template.

For a tailored strategy on KSeF penalty mitigation and compliance programme design, reach out to info@kordeckipartners.com.

Frequently asked questions

Q: Can a KSeF penalty be appealed, and what is the realistic timeline for resolution?

A: Yes. A penalty assessment issued by the Head of the Tax Office may be appealed to the Dyrektor Izby Administracji Skarbowej (Director of the Tax Administration Chamber) within 14 days of receipt. If the administrative appeal fails, the taxpayer may proceed to the Wojewódzki Sąd Administracyjny (Regional Administrative Court, WSA) and, ultimately, the Naczelny Sąd Administracyjny (Supreme Administrative Court, NSA). The full administrative and judicial cycle typically takes 18 to 36 months. Interim suspension of the penalty during proceedings is possible but not automatic – it requires a separate application demonstrating that enforcement would cause irreversible financial harm.

Q: Does the KSeF penalty regime apply to invoices issued to consumers (B2C)?

A: No – this is one of the most persistent misconceptions. KSeF mandatory invoicing applies exclusively to B2B transactions between VAT-registered Polish taxpayers. Invoices issued to private individuals (non-VAT-registered consumers) remain outside the KSeF obligation and continue to be issued in paper or PDF form. However, a B2B invoice mistakenly issued as a B2C document to avoid KSeF is treated as a deliberate circumvention and attracts the full 100% penalty rate, plus potential criminal fiscal liability under the Kodeks karny skarbowy (Fiscal Penal Code).

Q: What does KSeF compliance cost for a mid-size business, and is there a tax deduction available?

A: For a business issuing 1,000 to 5,000 invoices per month, the total compliance investment – ERP integration, legal review of invoice templates, staff training – typically falls in the range of PLN 30,000 to PLN 120,000, depending on system complexity and the number of legal entities involved. These costs are deductible as operational expenses under Polish corporate income tax (CIT) rules. Businesses operating under the IP Box regime should ensure that KSeF-related IT costs are correctly classified, as misallocation between qualifying and non-qualifying expenditure can affect the preferential 5% rate. Transfer pricing documentation should also reflect any intra-group recharging of KSeF implementation costs.

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.