SAF-T in Poland: the JPK explained
Poland operates one of the most extensive SAF-T implementations globally through JPK (Jednolity Plik Kontrolny). The system comprises multiple file types: JPK_VAT (monthly VAT records), JPK_FA (invoices), JPK_KR (accounting books), JPK_WB (bank statements), JPK_MAG (warehouse records), and JPK_PKPIR (revenue ledger). JPK_VAT is submitted monthly; other files are provided on request.
General information only, not tax advice. Rules change, so check the official sources at the bottom of this page before you act.
The mandate
JPK — Jednolity Plik Kontrolny (Uniform Control File)
Who must file
All VAT-registered taxpayers (JPK_V7M/V7K). All businesses for other JPK file types on request.
How it works
ERP generates JPK XML files → JPK_V7M/V7K submitted monthly to KAS → other JPK types provided on request during audits → KAS automated validation.
Key dates for Poland
- Jul 2016JPK mandatory for large enterprises
- Jan 2018JPK_VAT mandatory for all VAT-registered businesses
- Oct 2020JPK_V7M/V7K replaces JPK_VAT (merged with VAT return)
- Feb 2026JPK integration with KSeF e-invoicing system
What the file contains
JPK_V7M (monthly filers) and JPK_V7K (quarterly filers) have replaced both the old JPK_VAT and the traditional VAT return. This merged file contains both the VAT register data and the VAT return declaration. Other JPK file types (FA, KR, WB, MAG) must be generated on request during tax audits. The integration with KSeF means that JPK_FA data must be consistent with KSeF-registered invoices.
What your ERP has to deliver
ERP systems must support generation of all 7 JPK file types. The monthly JPK_V7M/V7K requires automated extraction and submission workflows. Integration with KSeF is essential — the KSeF reference number must appear in JPK files. Systems handling multiple JPK types need robust data consistency checks across all file types.
The data flow, step by step
Practical insights
- Poland's JPK system is among the most comprehensive SAF-T implementations because it covers not just accounting and invoicing but also bank statements, warehouse records, and revenue ledgers. Companies must treat JPK as a multi-file compliance program, not a single file requirement.
- The merger of JPK_VAT and the VAT return into JPK_V7M/V7K was a significant change. It means the 'audit file' and the 'tax return' are now the same document, increasing the stakes for data accuracy.
- KSeF integration with JPK is the next frontier. The KSeF reference number must appear in JPK files, creating a cross-reference chain from invoice issuance through to audit file submission. Companies must architect their systems for this end-to-end data flow.
- Polish tax authorities (KAS) use JPK data for aggressive automated risk assessment. Patterns in JPK data that suggest VAT fraud or errors trigger immediate automated inquiries.
Common pitfalls
- Focusing only on JPK_V7M/V7K and neglecting readiness for other JPK file types that may be requested during audits.
- Inconsistencies between JPK file types (e.g., JPK_FA invoice data not matching JPK_V7M VAT register data).
- Not updating JPK infrastructure for KSeF integration — the KSeF reference number is now a required field in relevant JPK submissions.