Poland's Krajowy System e-Faktur (KSeF) became mandatory for large businesses (revenue above PLN 200M) on February 1, 2026, and for all remaining businesses on April 1, 2026. Now that both phases are live, the penalty framework is fully active. This article provides a comprehensive overview of what non-compliance looks like, what the financial and operational consequences are, and how to protect your business.
The stakes are high: penalties can reach up to 100% of the VAT amount on non-compliant invoices, and the downstream effects — including VAT deduction denial for invoice recipients — create supply-chain-wide compliance pressure.
Penalty Overview
The Polish penalty framework for KSeF non-compliance operates on a severity scale. Consequences range from informational notices for minor technical issues to VAT deduction denial for serious violations. Understanding this scale helps businesses prioritise their compliance efforts.
The severity of penalties depends on several factors: the nature of the violation (technical error vs. deliberate avoidance), the frequency (isolated incident vs. systematic non-compliance), the financial impact (VAT amount involved), and whether the taxpayer has taken steps to self-correct.
Types of Violations
KSeF non-compliance can take several forms, each carrying different consequences. Here are the primary violation categories that Polish tax authorities will enforce:
Failure to Issue Through KSeF
Issuing an invoice outside of KSeF when the mandate applies. This includes sending PDF or paper invoices instead of structured FA(3) XML through the national system. The invoice may be treated as not issued.
Incorrect FA(3) Schema
Submitting an invoice to KSeF that does not conform to the FA(3) XML schema. Schema violations include missing mandatory elements, incorrect data types, invalid tax category codes, or malformed XML structure.
Missing JPK_VDEK Reference Fields
Filing a JPK_VDEK VAT return without the required KSeF identification numbers or reference codes (OFF, BFK, DI). The return will be rejected by the schema validation and treated as not filed.
Fraudulent Use of Exception Codes
Using OFF, BFK, or DI reference codes without legitimate justification, or systematically avoiding KSeF by claiming exemptions. The tax authority will audit exception code usage patterns.
It's important to note that these violation categories are not mutually exclusive. A single transaction can trigger multiple violations — for example, an invoice issued outside KSeF (violation 1) will also result in a missing KSeF ID in the JPK_VDEK return (violation 3), compounding the penalties.
Financial Penalties
The financial penalties under the Polish Tax Ordinance (Ordynacja podatkowa) and the amended VAT Act are structured to be proportional to the severity of the violation:
100%
Maximum VAT Penalty
For deliberate issuance of invoices outside KSeF, penalties can reach up to 100% of the VAT amount shown on the non-compliant invoices.
PLN 56K
Late Filing Maximum
Late JPK_VDEK filing penalties under the Fiscal Penal Code (Kodeks karny skarbowy) can reach up to PLN 56,000 depending on the minimum wage reference.
Cascading
Supply Chain Impact
Recipients of non-KSeF invoices may lose VAT deduction rights, creating financial liability for the buyer that the seller caused.
No Grace Period Announced
Unlike some EU countries that introduced transitional tolerance periods for new e-invoicing mandates, the Polish Ministry of Finance has not announced any grace period for KSeF compliance. The penalty framework is active from the mandate date. Businesses should assume full enforcement from day one.
Operational Consequences
Beyond financial penalties, KSeF non-compliance creates significant operational disruptions that can be even more damaging than the fines themselves:
An invoice not issued through KSeF when the mandate applies may be treated as an invalid document. The seller may need to void it and reissue through KSeF, creating accounting complications and payment delays.
If a buyer receives an invoice that was not processed through KSeF, they may be denied the right to deduct input VAT. This creates pressure from customers on their suppliers to comply, as the buyer bears the financial cost of the seller's non-compliance.
JPK_VDEK returns missing KSeF references will be rejected at the schema level. This creates a filing backlog and risks late filing penalties if not resolved before the deadline.
Systematic non-compliance flags businesses for enhanced audit scrutiny. The tax authority's automated risk scoring considers KSeF compliance history, and repeated violations increase the probability of a full tax audit.
Business partners, especially large enterprises that were compliant from February 2026, may refuse to accept invoices not issued through KSeF. This can disrupt supply chains and delay payments.
Impact on SMEs
The April 1, 2026 phase brought all remaining Polish businesses into KSeF scope, including small and medium-sized enterprises (SMEs). This phase presents unique challenges:
Limited IT Resources
Many SMEs lack dedicated IT teams to implement KSeF integrations. They often rely on accounting software providers for compliance, and not all providers have updated their systems with KSeF capabilities.
Proportionally Higher Costs
While penalties are proportional to VAT amounts, the cost of implementing KSeF compliance is disproportionately high for smaller businesses. A PLN 10,000 fine may be trivial for a large enterprise but devastating for a micro-business.
Awareness Gaps
Despite government communications, many smaller businesses are still unaware of the full scope of KSeF requirements, particularly the JPK_VDEK reference field changes and the implication for VAT return filing.
Manual Process Disruption
SMEs that previously relied on manual or semi-automated invoicing workflows face the biggest operational disruption. They must transition to structured FA(3) XML generation and KSeF API connectivity.
Legitimate Exemption Scenarios
The KSeF legislation does recognise specific scenarios where invoices may be issued outside the system without penalty. Understanding these exemptions is critical to avoiding unnecessary risk:
When KSeF itself is unavailable due to scheduled maintenance or unscheduled outages, businesses may issue invoices in offline mode. The invoice must still be in FA(3) format and must be submitted to KSeF retroactively within the prescribed timeframe once the system is restored. The "OFF" reference code is used in JPK_VDEK.
Invoices issued on the basis of fiscal cash register receipts have their own tracking through the fiscal system and fall outside KSeF scope. The "BFK" code is used in the JPK_VDEK return to reference these documents.
Simplified invoices (faktury uproszczone) for transactions under PLN 450 have a reduced reporting obligation. The "DI" code may apply, but businesses should verify with their tax adviser as the rules are nuanced.
Invoices from foreign entities that are not registered for Polish VAT are outside KSeF scope. However, the Polish buyer must still reference these documents correctly in their JPK_VDEK filings using the appropriate code.
Document Your Exemptions
Every use of an exception code should be documented internally. If audited, you must be able to demonstrate why a KSeF ID was not used for a specific invoice. Keep records of KSeF downtime notifications, cash register receipts, and any other supporting evidence.
Common Mistakes That Trigger Penalties
Based on early enforcement data from the February 2026 phase and common patterns observed across EU e-invoicing mandates, these are the most frequent mistakes that lead to penalties:
Some businesses submitted to KSeF but continued sending PDF copies directly to customers. This creates confusion about which document is the legal invoice and may trigger duplicate invoice penalties.
Invoices are submitted to KSeF but the returned KSeF identification number is not captured or linked to the original record. When generating JPK_VDEK, the KSeF reference is missing.
Applying the wrong exception code (e.g., using "DI" when "OFF" should be used) or defaulting all non-KSeF invoices to a single code without proper justification.
Issuing invoices during KSeF downtime but forgetting to submit them retroactively when the system comes back online. These invoices remain as offline exceptions permanently.
Focusing only on outbound invoices and neglecting to capture KSeF IDs from received purchase invoices, which are also required in the buyer's JPK_VDEK filing.
How InvoStaq Prevents Penalties
InvoStaq's KSeF compliance platform is specifically designed to eliminate the risk of penalty-triggering errors at every stage of the invoice lifecycle:
Pre-Submission Validation
Every invoice is validated against the FA(3) schema before submission to KSeF. Schema errors, missing fields, and data type mismatches are caught and flagged before they can cause rejection.
Automatic KSeF ID Capture
When KSeF returns the identification number, InvoStaq automatically captures and links it to the original invoice record. No manual step, no risk of losing the reference.
JPK_VDEK Reference Population
InvoStaq automatically populates the correct KSeF reference (ID or exception code) in your JPK_VDEK data. The system determines the correct code based on the invoice's processing history.
Offline Mode Management
When KSeF is unavailable, InvoStaq queues invoices securely and automatically resubmits them when the system is restored. Offline invoices are tracked and the "OFF" code is applied automatically in JPK_VDEK.
With InvoStaq, the entire KSeF compliance chain — from invoice creation through submission, ID capture, and VAT return reference population — is fully automated. This eliminates the manual touchpoints where errors occur and penalties are triggered.
Eliminate KSeF Compliance Risk
InvoStaq's AI-powered validation prevents every common KSeF error — so you never face penalties, rejections, or VAT deduction challenges.