New KSeF Invoice Designations Mandatory in SAF‑T Files – Errors May Trigger PLN 500 Penalties

Poland has taken another step in tightening its digital VAT control framework by introducing new invoice designation requirements in the SAF‑T (JPK_VAT) file, closely linked to the National e‑Invoicing System (KSeF). While the changes are intended to improve data consistency and audit efficiency, they have already raised serious concerns among entrepreneurs and tax practitioners.

What has changed?

Under the new rules, taxpayers submitting JPK_VAT files must now provide additional information for each invoice, depending on how it was issued:

• If an invoice was issued via KSeF, the taxpayer must report the unique KSeF identification number.
• If the invoice was not issued in KSeF, a special marking/designation must be included in the SAF‑T file instead.

These requirements apply to both sales and purchase invoices, significantly increasing the level of transactional detail expected by the tax authorities.

The deadline for compliance is 25 March, leaving businesses limited time to adjust their accounting systems, internal processes, and data validation controls.

Why are there problems?

In practice, many taxpayers are struggling with implementation, for several reasons:

1. Late clarification of rules
   Detailed technical and practical guidance has been issued very close to the deadline, leaving insufficient time for testing and adjustments.
2. Complex system dependencies
   Correct reporting depends on seamless integration between ERP systems, invoicing tools, KSeF, and SAF‑T reporting modules. Any mismatch can lead to incorrect or missing data.
3. Unclear edge cases
   Businesses report uncertainty around specific scenarios, such as:
   • Corrections and credit notes
   • Invoices issued during system outages
   • Imports of invoices from foreign suppliers
   • Historical invoices and mixed reporting periods
4. Manual interventions increase risk
   Where automated system changes could not be implemented in time, companies may rely on manual mappings or workarounds—substantially increasing the probability of errors.

Penalties: PLN 500 per error

The stakes are high. Polish VAT regulations provide that each error in the JPK_VAT file related to required invoice data can result in a penalty of PLN 500. Importantly:

• The penalty applies per individual mistake, not per file.
• Multiple incorrectly marked invoices in a single JPK_VAT submission can therefore result in cumulative penalties.
• Corrections may not always prevent sanctions if errors are identified by the tax authorities first.

Given the volume of invoices reported by many businesses, this represents a material compliance and financial risk, even for otherwise compliant taxpayers.

What should businesses do now?

With the deadline imminent, companies operating in or with Poland should urgently:

• Review SAF‑T reporting logic to ensure KSeF numbers and special designations are correctly populated.
• Reconcile invoicing data between KSeF, accounting systems, and JPK_VAT outputs.
• Document assumptions and interpretations, especially where guidance is unclear.
• Prepare correction processes to quickly address any issues identified after submission.

Taxpayers may also wish to engage proactively with advisors or industry groups to share interpretations and practical solutions, particularly given the risk of inconsistent application across businesses.

Broader context: advancing digital VAT enforcement

These changes underline Poland’s continued push toward real‑time and data‑driven VAT control, with KSeF at the core of the### Poland: KSeF and New SAF‑T Invoice Designations Published – Errors May Trigger Penalties

Summary – Key Points

• New reporting obligation: Taxpayers filing the VAT SAF‑T (JPK_V7) must now include either the KSeF invoice number or a special designation for invoices not issued via KSeF.
• Tight deadline: The new requirements apply from 25 March, leaving businesses limited time to update systems and processes.
• Financial risk: Errors or missing data may result in penalties of PLN 500 per mistake, significantly increasing compliance exposure.

Article

Poland has taken another step in tightening VAT digital reporting, publishing new requirements that directly link the National e‑Invoicing System (KSeF) with the VAT Uniform Control File (SAF‑T / JPK_V7). While the changes were expected as part of Poland’s broader e‑invoicing roadmap, their practical implementation is already raising concerns among taxpayers and advisors.

New data fields in JPK_V7

Entrepreneurs submitting the VAT SAF‑T are now required to provide additional invoice‑level information. Specifically, for each invoice reported, taxpayers must indicate:

• the KSeF identification number, if the invoice was issued through the national e‑invoicing platform, or
• a special symbol in cases where the invoice was issued outside KSeF (e.g. temporary exclusions, specific standardised invoices).

This obligation applies irrespective of whether the invoice was issued voluntarily via KSeF or under transitional rules. The objective is clear: tax authorities want a direct and automated reconciliation between VAT returns, SAF‑T data, and the invoices flowing through KSeF.

Deadline: 25 March

The new reporting responsibilities enter into force on 25 March, giving taxpayers very limited time to:

• adapt ERP and billing systems,
• ensure correct mapping between invoice data and SAF‑T structures, and
• train tax and finance teams on the revised rules.

This compressed timeline is particularly challenging for large businesses with complex invoicing flows or decentralised systems.

High penalties for mistakes

One of the most controversial elements is the sanction regime. Under the rules, each individual error in the SAF‑T file relating to the new invoice designations may result in a PLN 500 penalty.

Given the high volume of invoices typically reported in JPK_V7, even minor technical mistakes can quickly translate into significant financial exposure. Importantly, penalties may apply not only to missing KSeF numbers, but also to:

• incorrect symbols,
• inconsistencies between KSeF and SAF‑T data, or
• formal errors caused by system limitations.

Practical problems for taxpayers

In practice, businesses are already identifying several problem areas:

• System readiness: Not all ERP systems are yet fully aligned with the new fields, especially where KSeF integration is partial or manual.
• Data consistency: Matching KSeF invoice numbers with SAF‑T transaction lines requires precise data governance and reconciliation processes.
• Operational complexity: Mixed scenarios (KSeF and non‑KSeF invoices in the same reporting period) increase the risk of errors.

Tax advisors warn that the combination of technical complexity, short implementation time and strict penalties could lead to widespread non‑compliance, particularly in the early months.

A signal of what is coming

Beyond the immediate compliance burden, the changes clearly signal the direction of travel: KSeF is becoming the central reference point for VAT control in Poland. The requirement to reflect KSeF data directly in SAF‑T filings reinforces the expectation that businesses treat e‑invoicing not as a standalone project, but as an integral part of VAT reporting and audit defence.

Taxpayers are therefore advised to:

• urgently review their JPK_V7 reporting processes,
• test KSeF–SAF‑T data flows end‑to‑end, and
• document controls to demonstrate due diligence in case of errors.