If your firm has a Polish VAT number, you must treat VAT compliance as a core process.
A late or incorrect VAT declaration in Poland can quickly lead to penalties, audits and reputational issues.
This guide explains how VAT records, JPK_V7 files and KSeF work in practice.
Why VAT compliance in Poland matters
VAT is one of the main revenue sources for the Polish state budget, so it receives close scrutiny.
Because VAT is vulnerable to fraud, Poland has added many reporting layers and detailed data requirements.
Polish tax offices rely heavily on electronic data from JPK_V7 files to identify risks.
Incorrect coding or missing data can trigger audits even when the underlying business is sound.
Get clarity on your Polish VAT position
Not sure whether your current VAT declaration in Poland is fully compliant?
Share a short outline of your Polish flows and we will tell you where the real risks are.
VAT records and the VAT declaration in Poland
Active VAT payers must keep electronic sales and purchase records using accounting software.
These records must contain all data needed to calculate VAT, identify counterparties and prepare summary statements.
Each month, those electronic records are sent to the tax office together with the VAT declaration in Poland.
Both elements are combined into a single electronic file called JPK_VAT with a declaration (JPK_V7M or JPK_V7K).
JPK_V7M and JPK_V7K – one file instead of many forms
Since October 2020, the classic VAT‑7 and VAT‑7K forms were replaced by JPK_V7M and JPK_V7K.
The file has two logical parts: a records section and a declaration section.
Monthly payers submit JPK_V7M containing both parts for every month.
Quarterly payers submit the records part each month and the declaration part only after each quarter as JPK_V7K.
Deadlines for the monthly VAT declaration in Poland
The monthly VAT declaration in Poland is due by the 25th day of the month following the reporting month. This applies to both the records section and the declaration section.
If the 25th falls on a weekend or public holiday, the deadline moves to the next working day.
Any VAT payable is due on the same day as the file.
Both the payment and the full JPK_V7M file are therefore part of one monthly cycle.
Deadlines for the quarterly VAT declaration in Poland
The quarterly VAT declaration in Poland is due by the 25th day of the month following the reporting quarter. This applies only to the declaration section. The records section is still due by the 25th day of the month following each month.
If the 25th falls on a weekend or public holiday, the deadline moves to the next working day.
Any VAT payable is due on the same day as the file with the declaration (by the 25th day of the month following the reporting quarter).
Both the payment and the full JPK_V7K file are therefore part of one monthly cycle. However, the JPK_V7K file containing only the records section is still part of the monthly cycle.
VAT declaration in practice – content of sales and purchase records
Sales and purchase records must show tax base, VAT amounts and applied rates for each type of sale.
They must also identify contractors and contain numbers of underlying sales and purchase documents.
The records must be detailed enough to allow correct VAT settlement and to prepare EU recapitulative statements.
They must also support reconciliation with cash registers and with other tax forms.
Polish law now requires that these records are kept only in electronic form.
Paper registers are no longer sufficient for active VAT taxpayers.
Checklist – are your Polish VAT records complete?
Use this checklist as a quick sense‑check for your Polish VAT setup.
- Every Polish VAT invoice has a unique internal number and is posted in the correct period.
- Sales and purchases are split by VAT rate, exemptions and reverse charge rules.
- Each entry contains the contractor’s VAT number and country code where required.
- Each sale and purchase can be linked to an underlying invoice or other evidence.
- Cash register summaries are clearly labelled.
- GTU codes, procedure codes and document type codes are applied where required.
- KSeF numbers or OFF / BFK / DI markings are captured for all relevant invoices.
VAT declaration in Poland – filing JPK_V7 step by step
Here you will find a practical view of how to file JPK_V7 in Poland.
It walks you through the monthly or quarterly workflow step by step.
When you must submit JPK_V7M
You must submit JPK_V7M if your company is a monthly VAT payer in Poland.
Most foreign businesses choose monthly settlement to streamline processes.
The JPK_V7M file for a month includes all sales and purchase records for that month.
It also contains the VAT declaration in Poland for that month in the declaration section.
Quarterly scheme and JPK_V7K
Quarterly VAT payers send only the records part of JPK_V7K for the first two months of each quarter.
For the third month, they submit both the records and the declaration part, covering the entire quarter.
The deadline remains the 25th day of the month following each month or quarter.
In practice, quarterly payers still work in a monthly rhythm, just with a deferred declaration.
Important note: Not every VAT taxpayer can settle VAT on a quarterly basis. You cannot do so during the first 12 months after registration as a VAT taxpayer. Similarly, taxpayers who settle VAT on imports under the so-called simplified procedure must file VAT declarations monthly. The law provides for a few additional exceptions in this regard. So before you switch to quarterly VAT, you must carefully review your specific situation.
Timeline graphic: typical monthly VAT reporting cycle
This timeline shows how a typical Polish VAT reporting month unfolds, from data extraction to filing and follow-up.
- Days 1–10 – Data capture
Post all invoices for the previous month, including corrections and late documents. - Days 11–17 – Classification and reviews
Apply GTU codes, procedure codes and document types.
Reconcile ledgers and cross‑check VAT balances. - Days 18–22 – Draft JPK_V7 and internal sign‑off
Generate the draft file, review warnings from your software and fix errors, if necessary. - Days 23–25 – Filing and payment
Submit the JPK_V7M or JPK_V7K file electronically and pay any VAT due.
Recapitulative statements VAT‑UE – EC sales lists
Recapitulative statements VAT‑UE complement the VAT declaration in Poland for intra‑EU transactions.
They report values by customer VAT number, not by invoice or tax rate.
You must file VAT‑UE when you perform:
- intra‑Community supplies of goods,
- intra‑Community supplies of services,
- intra-Community acquisitions of goods,
- call‑off stock movements.
Only taxpayers registered as EU VAT taxpayers (VAT‑UE) file these statements.
VAT‑UE is submitted only electronically and only for monthly periods.
The deadline is the 25th day of the month following the month when the intra‑EU transaction occurred.
Corrections are made through a separate correcting statement VAT‑UEK, not by amending earlier periods inside JPK_V7.
The introduction of JPK_V7 did not remove the obligation to send VAT‑UE recapitulative statements.
Let a Polish advisor run your VAT filings
Managing JPK_V7 and VAT‑UE in‑house can drain time from your finance team.
We handle VAT declaration in Poland every month for foreign‑owned firms, so your team can focus on core work.
What GTU codes are and why they matter
GTU codes are thirteen classification codes that mark sales of sensitive goods and services in JPK_V7.
They cover items like fuels, alcohol, electronics, scrap, financial services and some intangible rights.
GTU codes are applied only in the JPK_V7 sales records, not on purchase records.
They normally do not appear on the invoice itself and exist only inside the electronic file.
The tax office can fine you up to PLN 500 for each incorrect or missing GTU classification.
Because one invoice can carry several GTU codes, poor coding can quickly become expensive.
Overview of GTU_01 to GTU_13
Below is a high‑level summary for orientation.
For binding interpretation, you must always refer to the legal annexes and guidance.
- GTU_01 – alcoholic beverages and similar products.
- GTU_02 – fuels and some petroleum products.
- GTU_03 – oils and lubricants.
- GTU_04 – tobacco products and substitutes.
- GTU_05 – waste and recyclable raw materials.
- GTU_06 – electronic equipment and selected parts.
- GTU_07 – vehicles and certain vehicle parts.
- GTU_08 – precious metals and jewellery.
- GTU_09 – medicines and some medical products.
- GTU_10 – buildings, structures and land.
- GTU_11 – greenhouse gas emission allowances and similar rights.
- GTU_12 – intangible services such as advisory, legal, accounting, management and marketing.
- GTU_13 – transport and storage related services.
Your team should classify sales at line level, because one invoice can involve multiple GTU categories.
Automation helps, but manual review is still required for edge cases.
Why procedure codes exist
JPK_V7 also uses procedure codes to flag transactions subject to special VAT regimes.
They apply both on the sales and purchase side, depending on the procedure type.
The codes help the tax office identify high‑risk patterns like split payment, margin schemes or triangulation.
They sit next to the standard VAT rates and GTU codes in your records.
Key sales‑side procedure codes
Polish guidance lists several procedure codes for output VAT:
- WSTO_EE – intra‑EU distance sales of goods and certain electronic services to consumers.
- TP – transactions with related parties, as defined in the VAT Act.
- TT_WNT / TT_D – simplified triangulation for intra‑EU chain transactions.
- MR_T / MR_UZ – margin schemes for tourism or second‑hand goods.
- I_42 / I_63 – import of goods with onward intra‑EU supply under specific customs procedures.
- B_SPV – transfer of a single‑purpose voucher.
- B_SPV_DOSTAWA – supply of goods or services covered by a single‑purpose voucher.
- B_MPV_PROWIZJA – commission for intermediation in multi‑purpose voucher transactions.
- IED – sales facilitated via an electronic interface for imported or intra‑EU goods, where the platform is deemed supplier.
The same invoice can be marked with several procedure codes if several regimes apply.
Your accounting software should therefore allow multiple flags per document.
Purchase‑side procedure code
On the purchase side, only one specific procedure code apply, which is IMP for import settlements.
Correct coding matters because some procedure codes affect additional disclosures.
Errors can distort your VAT declaration in Poland and can also delay refunds.
If you prefer to offload GTU and procedure coding to a Polish advisor, you can contact us via the form and we will design a clean setup together.
Classic document codes: RO, WEW, FP, VAT_RR, MK
JPK_V7 uses document type codes to identify documents other than standard sales invoices.
These codes clarify how a given value reached the VAT records.
Key document codes include:
- RO – internal daily or periodic summary of sales from a cash register.
- FP – invoice issued to document a sale already recorded on a cash register receipt.
- WEW – internal document, for example for free supplies or some self‑billing situations.
- VAT_RR – special invoices for purchases from flat‑rate farmers.
- MK – invoices under the cash accounting scheme.
These codes apply to both sales and purchases where relevant.
They remain in force under the newest JPK_V7 structure.
KSeF invoice numbers and new OFF / BFK / DI codes
Poland is rolling out mandatory e‑invoicing through the National e‑Invoice System called KSeF.
From settlements for February 2026, the JPK_V7M(3) and JPK_V7K(3) structures are linked to KSeF.
In the updated JPK_V7 records, every invoice entry must show either the KSeF invoice number or a special code.
If the invoice has no KSeF number at filing, you must use OFF, BFK or DI.
- OFF – invoice issued during a KSeF outage, not yet assigned a KSeF number.
- BFK – invoice issued outside KSeF where e‑invoicing is not mandatory, for example some B2C or exempt cases.
- DI – document other than an invoice, including customs documents and internal evidence, without a KSeF number.
The obligation to report the KSeF number or one of these codes applies to both sales and purchase records.
Existing codes like RO, WEW, FP, VAT_RR and MK continue to apply in parallel.
A key compliance point is timing.
You assess the KSeF status at the date you submit the JPK_V7 file, not on the invoice issue date.
Data, controls and reconciliations for a safe VAT declaration in Poland
A compliant VAT declaration in Poland depends on the quality of your underlying records.
This means clear data ownership, good system configuration and documented controls.
Best practice is to reconcile VAT records each month to the general ledger and to sub‑ledgers.
You should also reconcile to cash registers, KSeF invoice lists and, where relevant, Intrastat data.
Before filing, review reports from your ERP or compliance software.
Focus on missing VAT numbers, negative bases, inconsistent GTU codes and missing KSeF numbers.
Risk areas for foreign firms
Foreign firms often face higher risk because local specifics differ from group standards.
Common pressure points include cash registers, chain transactions and local reverse‑charge situations.
Errors in GTU or procedure codes can cause mismatches with counterparties’ files.
These mismatches are now a standard trigger for desk audits.
How a Polish VAT advisor can help
An experienced Polish VAT advisor can design your compliance process around your existing systems.
We understand both the legal rules and the practical requirements of JPK_V7 and KSeF.
Typical support includes mapping your transaction flows, setting up codes and testing JPK_V7 exports.
Advisors also handle contact with tax offices, especially during audits or when correcting past periods.
For cross‑border firms, a local advisor can translate Polish technical language into clear English.
That helps boards and CFOs assess exposure and approve remediation plans with confidence.
Get your VAT declaration in Poland off your agenda
If your firm trades in Poland, you cannot ignore JPK_V7 other VAT obligations.
At the same time, you want your teams focused on core business, not on decoding Polish regulations.
We work with foreign‑owned companies that need reliable VAT compliance in Poland.
Based on your flows and systems, we can design a complete setup for records and JPK_V7 files.
If you share a short outline of your transaction types and current tools, we can:
- Confirm which obligations apply, including monthly or quarterly VAT returns.
- Review your current JPK_V7 exports and identify risk areas.
- Propose a clear operating model with defined responsibilities and realistic timelines.
Use the contact form to request a short introductory call.
We can then agree on the scope, budget and next steps for your Polish VAT compliance.
Ready to hand over your Polish VAT?
If you send us a short summary of your Polish and intra‑EU transactions, we can come back with a concrete proposal.
We will agree the division of tasks, timeline and a transparent fee structure before we start.
FAQ – VAT declaration in Poland
Any business registered as an active VAT payer in Poland must file JPK_V7 files.
This also applies when supplies are VAT‑exempt but the entity holds an active VAT status.
Most businesses file monthly JPK_V7M returns.
Some may qualify for quarterly JPK_V7K, but records are still submitted every month.
You must submit the JPK_V7 file by the 25th day of the month following the reporting period.
If that day is a weekend or holiday, the deadline moves to the next business day.
No, separate VAT‑7 or VAT‑7K forms have been replaced by the combined JPK_V7 structure.
The JPK_V7 file acts as both VAT records and VAT declaration in Poland.
GTU codes are used only in JPK_V7 sales records, not on invoices.
They apply to specific categories of goods and services defined in legislation and guidance.
No, purchase documents are not marked with GTU codes in JPK_V7.
They may, however, require procedure codes such as WEW or IMP where special rules apply.
JPK_V7M(3) and JPK_V7K(3) must show a KSeF number or an OFF, BFK or DI code.
This rule applies to both sales and purchase records and links VAT reporting to e‑invoicing.
You can correct errors by submitting an amended JPK_V7 file.
However, repeated or significant errors can lead to penalties, including fines for incorrect GTU codes.
If you already see recurring errors in past periods, reach out via the contact form so we can plan a safe correction strategy.