A Warsaw-based technology company with 15 subsidiaries receives a notice from the National Tax Administration (Krajowa Administracja Skarbowa, KAS): its JPK_CIT files for the prior year contain structural inconsistencies. The finance director has 7 days to respond. The team has never mapped its chart of accounts to the required XML schema. Remediation will take weeks – and the exposure to interest and surcharges is already running.

JPK_CIT is Poland's mandatory Standard Audit File for corporate income tax, requiring companies to submit structured XML data covering their accounting books, fixed assets, and tax adjustments on an annual basis. The obligation was introduced under Polish tax legislation and applies in phases: large taxpayers from the 2024 tax year, tax capital groups and other CIT payers from 2025, and remaining entities from 2026. Failure to submit on time, or submission of a defective file, triggers financial penalties and – in aggravated cases – personal liability for board members and finance officers under the Kodeks karny skarbowy (Fiscal Penal Code, KKS).

This analysis covers the doctrinal foundation of JPK_CIT, the data architecture your finance team must build, the cross-border dimension for foreign-owned groups, strategic preparation steps, and the outlook as KAS enforcement ramps up. Each section contains a concrete figure and a direct action point.

What is JPK_CIT and who is already obligated?

JPK_CIT is not a new tax return. It is a structured data file – an XML schema defined by the Ministry of Finance (Ministerstwo Finansów, MF) – that mirrors a company's accounting books at a granular level. Think of it as a digital audit trail submitted proactively, before any inspection begins. The file covers three logical blocks: accounting ledger entries, fixed assets and depreciation registers, and CIT-specific adjustments such as non-deductible costs and related-party corrections.

The phased rollout creates an immediate compliance cliff. Large taxpayers – those whose annual revenue exceeded EUR 50m in the reference year, as defined under Polish tax legislation – were required to submit their first JPK_CIT file for the 2024 tax year by the end of the third month following year-end. That deadline has already passed for calendar-year taxpayers. Tax capital groups (podatkowe grupy kapitałowe) and remaining CIT payers entered scope from the 2025 tax year. All other CIT obligors follow from 2026.

Three Polish institutions are central to this regime. The National Tax Administration (KAS) receives and processes files, cross-references them against VAT JPK data, and initiates inquiries. The Ministry of Finance issues the binding XML schema specifications. The National Court Register (Krajowy Rejestr Sądowy, KRS) remains relevant because the registered representative of the company bears formal responsibility for submission accuracy. Finance teams that treat JPK_CIT as an IT project – rather than a compliance project with legal consequences – are already behind.

  • Large taxpayers: obligation from the 2024 tax year
  • Tax capital groups: obligation from the 2025 tax year
  • Remaining CIT payers: obligation from the 2026 tax year
  • Submission deadline: end of the third month after the tax year ends
  • Defective file treated as non-submission for penalty purposes

One common misconception deserves correction here. Some finance teams assume that if their ERP system can generate a JPK_VAT file, JPK_CIT follows automatically. It does not. The data granularity requirements differ substantially. JPK_CIT demands journal-entry-level mapping to CIT categories – a layer that most ERP configurations do not produce without custom development or middleware.

What data architecture does JPK_CIT actually require?

The XML schema for JPK_CIT specifies three separate logical structures – often called "parts" – that must be populated consistently and cross-referentially. Part one covers the accounting books: every journal entry, with account codes mapped to a standardised chart of accounts. Part two covers fixed assets: acquisition cost, depreciation method, annual charge, and tax-adjusted carrying value. Part three covers CIT adjustments: add-backs, deductions, and reconciliation between accounting profit and taxable income.

The critical technical challenge is account-code mapping. Polish tax legislation does not mandate a single chart of accounts for all companies. Each entity uses its own plan kont. JPK_CIT requires that entity-specific codes be cross-referenced to the MF's reference taxonomy. For a manufacturing group in Silesia that we advised in winter 2025, this mapping exercise alone took six weeks and required collaboration between the finance team, the external auditor, and the ERP vendor. The lesson: start the mapping process no later than the first quarter of the year preceding your first obligation year.

Transfer pricing adjustments create a specific data integrity risk. Where a company has made a transfer pricing correction under Polish tax law – either a primary correction or a compensating adjustment – that correction must appear in part three of the file in a way that is reconcilable with the contemporaneous transfer pricing documentation. Inconsistencies between the JPK_CIT file and the transfer pricing master file or local file are among the first red flags that KAS analysts look for during automated cross-referencing.

Fixed assets data is frequently underestimated. Finance teams that maintain their fixed asset register in a spreadsheet – rather than an integrated ERP module – face a significant data-cleansing task. Every asset must carry an acquisition date, a depreciation start date, a tax depreciation rate, and a cumulative depreciation figure. Assets that were fully depreciated for accounting purposes but not yet for tax purposes must appear separately. The MF schema tolerates no gaps in this register: a single missing mandatory field causes the entire file to fail validation.

We secured a successful remediation and resubmission for a retail group in Małopolska (spring 2025), after their initial file was rejected due to a mismatch between the fixed-asset register and the depreciation schedule in the accounting books. The correction required reconciling over 800 asset lines across three subsidiary entities. Had the group started its data-quality review six months earlier, the remediation cost – and the exposure to late-submission interest – would have been avoided entirely.

How does the cross-border dimension affect foreign-owned groups in Poland?

For foreign-owned groups operating in Poland, JPK_CIT introduces a data disclosure dimension that goes well beyond domestic compliance. The structured file effectively gives KAS a machine-readable view of the Polish subsidiary's books – including intercompany flows, management fees, royalty payments, and financing arrangements. Groups that operate under the double tax treaty between Poland and the Netherlands, or similar bilateral conventions, must now assume that KAS can identify treaty-benefit claims at the journal-entry level.

The intercompany dimension is particularly sharp. A Polish subsidiary paying a management fee to a Dutch parent will have that payment visible in part one of the JPK_CIT file as a specific journal entry, and the add-back or deduction treatment of that fee will appear in part three. If the treatment in the JPK_CIT file is inconsistent with the transfer pricing documentation or the treaty position, KAS will have grounds – and the data – to open a targeted inquiry within weeks of submission. The window between submission and potential inquiry is now measured in months, not years.

For groups using the double tax treaty between Poland and the Netherlands to structure dividend flows or royalty payments, the JPK_CIT file creates a new consistency requirement. The treaty position documented in the transfer pricing file must align with the accounting treatment visible in the JPK_CIT ledger entries. Groups that have not reviewed this alignment before their first submission are taking a meaningful risk.

KSeF – Poland's mandatory e-invoicing system – adds a further layer. For companies already in scope for KSeF, every purchase invoice processed through the system carries a KSeF identifier. That identifier should, in principle, be traceable through the accounting entry in JPK_CIT. KAS cross-referencing between KSeF invoice data and JPK_CIT ledger entries is a stated enforcement priority for 2026. Foreign investors who are tracking the KSeF deadline timeline for 2026 and 2027 should factor this cross-referencing risk into their Polish compliance architecture.

IP Box structures deserve specific attention. A Polish subsidiary claiming the 5% preferential rate on qualifying intellectual property income under the IP Box regime must demonstrate, through its accounting records, that qualifying income and qualifying expenditure were tracked in separate accounting cells throughout the year. JPK_CIT makes that tracking – or its absence – immediately visible to KAS. Groups that have relied on year-end adjustments rather than contemporaneous tracking face a recharacterisation risk.

What are the penalties and personal liability consequences of non-compliance?

Non-compliance with JPK_CIT is not a minor administrative matter. Polish tax legislation treats failure to submit, late submission, and submission of a materially defective file as distinct violations, each carrying its own penalty range. The Fiscal Penal Code imposes fines of up to 240 daily rates for non-submission, with the daily rate calculated on the basis of average monthly salary. In practical terms, this means fines can reach several hundred thousand PLN for a single filing period.

Personal liability is the dimension that finance directors and chief financial officers most underestimate. Under Polish corporate legislation, the person who signs the JPK_CIT submission – typically the management board member responsible for finance – bears personal responsibility for its accuracy. If a defective file results in an underpayment of tax being identified, interest accrues at 8% per annum (the standard rate for tax arrears as of early 2026). The combination of the underlying tax, interest, and KKS penalties can produce an exposure that exceeds the original tax liability by a factor of two or more.

Board members and finance officers facing KAS inquiries arising from JPK_CIT discrepancies should be aware that the inquiry can escalate to a fiscal-criminal procedure under the Fiscal Penal Code. The fiscal criminal defence strategy for board members in such scenarios differs materially from ordinary tax proceedings – and the window for voluntary disclosure, which can significantly reduce penalties, is typically no longer than 30 days from the date the authority notifies the taxpayer of an initiated proceeding.

There is an irreversible element here that finance teams must internalise. Once KAS has initiated a fiscal-criminal procedure, the voluntary disclosure route (czynny żal) is closed. Personal liability cannot be cured by a subsequent corrective filing. The consequence forecloses options that would have been available before the authority acted. This asymmetry – low cost of early preparation versus high cost of late remediation – is the central economic argument for treating JPK_CIT as a board-level priority rather than a back-office task.

  • Fines under the Fiscal Penal Code: up to 240 daily rates per violation
  • Tax arrears interest: 8% per annum (standard rate, early 2026)
  • Voluntary disclosure window: typically 30 days from authority notification
  • Once fiscal-criminal procedure initiated: voluntary disclosure route closes

A practical point on surcharges: where KAS identifies an understated tax liability through JPK_CIT cross-referencing, it may apply an additional tax liability surcharge of 30% on the identified shortfall. This surcharge stacks on top of the underlying tax and interest. The aggregate exposure – tax, interest, 30% surcharge, and potential KKS fine – makes prevention dramatically cheaper than cure.

How should your finance team structure the preparation programme?

Preparation for JPK_CIT is a project with four distinct workstreams: data architecture, process design, system configuration, and legal review. Each workstream has a different owner and a different timeline. Finance teams that conflate them – treating the whole exercise as an IT ticket – typically discover the gap too late to close it before the submission deadline.

The data architecture workstream starts with the chart-of-accounts mapping exercise described above. This requires a finance team member with deep knowledge of the entity's account structure, working alongside the tax advisor who understands the MF taxonomy. Allow a minimum of four weeks for a single-entity company, and 10 to 14 weeks for a multi-entity group. The output is a mapping table that becomes the reference document for ERP configuration.

Process design covers the month-end and year-end routines that will produce JPK_CIT-compliant data as a by-product of normal accounting operations. This is the sustainable approach. Ad-hoc year-end extractions, by contrast, create a data quality risk every year. For a technology group in Mazowieckie that we advised in autumn 2024, redesigning the month-end close to embed JPK_CIT data capture reduced the estimated annual compliance effort from 120 hours to under 30 hours per year.

System configuration is the ERP vendor's responsibility, but the finance team must specify the requirements precisely. The specification document should reference the MF schema version, the mapping table from the data architecture workstream, and the validation rules that the MF's test environment uses. Allow at least six weeks for development and testing, plus a parallel-run period of at least one reporting cycle before the live submission.

The legal review workstream is often omitted. It covers three areas: confirming that the planned treatment of specific items (management fees, depreciation, related-party transactions) is consistent between the accounting books and the JPK_CIT file; reviewing the transfer pricing documentation for consistency with the part-three adjustments; and confirming that the signatory to the submission has appropriate authority and understands the personal liability implications. A tax advisor in Warsaw with JPK_CIT experience should be engaged no later than six months before the first submission deadline.

What is the strategic outlook for JPK_CIT enforcement in 2026 and beyond?

KAS has been explicit about its enforcement priorities for 2026. JPK_CIT cross-referencing – matching ledger entries against JPK_VAT data, KSeF invoice records, and transfer pricing documentation – is a stated focus. The authority has invested in analytical tools that can process large volumes of structured data and flag statistical anomalies for human review. The era of low-probability audit selection is ending for CIT purposes.

The doctrinal direction of travel is also significant. Polish tax legislation has moved consistently toward real-time or near-real-time data disclosure over the past decade: JPK_VAT in 2016, KSeF in 2024, JPK_CIT in 2024 to 2026. Each step has reduced the information asymmetry between taxpayers and the authority. JPK_CIT is the most consequential step yet, because it covers the full accounting ledger rather than a single transaction type.

For groups with Polish operations, the strategic implication is that the Polish subsidiary's books are now effectively open to KAS on an annual basis. Tax planning that relied on opacity – structures that worked because KAS lacked the data to identify them – must be reassessed. This applies particularly to IP Box claims, family foundation-related flows (where a Polish fundacja rodzinna is part of the group structure), and financing arrangements between related parties.

The family foundation dimension is worth a specific note. Since the fundacja rodzinna (family foundation) regime became available in May 2023, a number of groups have restructured ownership and asset-holding arrangements around this vehicle. Where a family foundation holds shares in a Polish operating company, the intercompany flows – dividends, loans, service fees – will now be visible in the operating company's JPK_CIT file. Tax advisors in Warsaw and Krakow are already reviewing these structures for JPK_CIT consistency.

Looking ahead to 2027 and beyond, the MF has indicated that the JPK_CIT schema will evolve. Additional data fields, more granular transaction-level reporting, and potential real-time submission requirements are under discussion. Finance teams that have built a sustainable data architecture for JPK_CIT compliance will be well-positioned to absorb these changes. Those that have relied on annual manual extractions will face repeated remediation cycles – each one more expensive than the last.

The strategic message is straightforward. JPK_CIT is not a one-time compliance event. It is a permanent feature of the Polish tax environment. The finance teams that will navigate it most effectively are those that treat it as a data quality and process design challenge, not a filing obligation.

Every specific situation carries its own risks. The treatment of a particular item in your chart of accounts, the consistency of your transfer pricing documentation, the authority of your submission signatory – these are not generic questions. They require review by a tax advisor with direct knowledge of your structure.

If your company is approaching its first JPK_CIT submission, or if a KAS inquiry has already been initiated, contact info@kordeckipartners.com. Our tax practice will assess your data architecture, review your transfer pricing consistency, and advise on personal liability exposure for your finance officers.

Frequently asked questions

Q: Our company uses a non-standard chart of accounts inherited from a foreign parent. Does this create a problem for JPK_CIT?

A: Yes, and it is one of the most common technical problems we encounter. JPK_CIT requires that every account code in your books be mapped to the Ministry of Finance's reference taxonomy. A non-standard chart of accounts does not disqualify you from compliance, but it does require a bespoke mapping exercise. This exercise must be completed before ERP configuration begins. Allow a minimum of four to six weeks for a single-entity company. The mapping table becomes a permanent compliance document that must be updated whenever the chart of accounts changes.

Q: What is the timeline for completing JPK_CIT preparation, and what does it typically cost?

A: For a mid-sized company with a single legal entity and a standard ERP system, a realistic preparation timeline is four to six months from project start to first test submission. For a multi-entity group, allow six to nine months. Costs vary significantly depending on ERP complexity and the state of the existing data. In our experience, companies that start preparation at least six months before their first deadline avoid the most expensive remediation scenarios. Those that start within three months of the deadline typically face compressed timelines that increase both cost and risk.

Q: We have already submitted our first JPK_CIT file. Can we correct it if we find an error?

A: Polish tax legislation permits corrective submissions. A corrective JPK_CIT file replaces the original and, if submitted before KAS initiates a formal audit or fiscal-criminal procedure, eliminates or significantly reduces the penalty exposure. However, the corrective submission must be accompanied by a written explanation of the changes. If the correction also affects the CIT return, a corrective return must be filed simultaneously. The window for effective correction is typically narrower than companies assume – KAS automated cross-referencing can identify discrepancies within weeks of the original submission deadline.

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 corporate tax compliance, JPK_CIT preparation, KSeF onboarding, transfer pricing, and tax-court litigation. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.

Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.