A Warsaw-based technology company receives a letter from the National Revenue Administration (Krajowa Administracja Skarbowa, KAS) requesting its accounting records in the new structured format. The finance team stares at the request. Nobody prepared for this. The deadline is 30 days away.

JPK_CIT is Poland's mandatory structured accounting file for corporate income tax purposes. Under Polish tax legislation, large taxpayers were required to submit the first JPK_CIT files for the fiscal year 2024, with the deadline falling on 31 March 2026. Medium and smaller companies follow in subsequent years – medium-sized entities from fiscal year 2025, and remaining taxpayers from fiscal year 2026. The file transmits chart-of-accounts data, journal entries, and fixed-asset registers directly to KAS in XML format.

This guide walks your finance team through the preparation steps, the most common technical pitfalls, and three business scenarios that illustrate how different company types should approach the process. The goal is to arrive at the submission deadline with clean data – not a last-minute scramble.

What exactly is JPK_CIT and who is affected?

JPK_CIT stands for Jednolity Plik Kontrolny dla podatku dochodowego od osób prawnych (Standard Audit File for Corporate Income Tax). It is part of the broader JPK framework that the Ministry of Finance (Ministerstwo Finansów, MF) introduced to digitise tax oversight across Polish tax law. The file does not replace the CIT annual return. It supplements it with granular transactional data drawn directly from accounting systems.

The rollout follows a three-wave schedule. The first wave covered taxpayers whose revenue exceeded EUR 50 million in the previous year – these entities filed for fiscal year 2024 by 31 March 2026. The second wave captures remaining CIT taxpayers (except micro-enterprises) for fiscal year 2025. The third wave brings in all remaining companies for fiscal year 2026. If your company consolidates under a tax capital group registered with the National Court Register (Krajowy Rejestr Sądowy, KRS), the group files as a single entity.

Two structures of the file exist. JPK_KR_PD covers the general ledger and profit-and-loss data. JPK_ST_KR covers fixed assets and their depreciation schedules. Both must be submitted together. A company with a non-calendar fiscal year submits within three months of its year-end – not by the calendar 31 March date. That distinction catches many finance teams off guard.

  • Revenue threshold for wave one: EUR 50 million (fiscal year 2024)
  • Wave two: all remaining CIT payers except micro-enterprises (fiscal year 2025)
  • Wave three: all remaining entities (fiscal year 2026)
  • Submission deadline: three months after fiscal year-end
  • Format: XML schema published by MF, transmitted via the MF e-Deklaracje gateway

How should your finance team prepare step by step?

Preparation falls into four distinct phases. Start at least six months before your submission deadline. Companies that begin in the final quarter before filing typically discover data gaps too late to correct them cleanly. The Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) has separately signalled that financial institutions will face heightened scrutiny of their JPK_CIT data quality in 2026.

Phase one is a data audit. Map every account in your chart of accounts against the MF's mandatory account-type taxonomy. Polish tax law requires each ledger account to carry a specific tag linking it to the correct CIT category. Accounts that exist in your system but carry no tag will generate a validation error on submission. Budget at least four weeks for this mapping exercise if your chart of accounts has more than 200 accounts.

Phase two is system configuration. Work with your ERP or accounting-software vendor to activate JPK_CIT export modules. SAP, Comarch ERP Optima, and Symfonia all released dedicated JPK_CIT modules by late 2025 – but activation is not automatic. Your IT and finance teams must configure account mappings, test the XML output against the MF schema validator, and correct any structural errors before live submission.

Phase three is a test submission. The MF provides a sandbox environment. Use it. A test run typically reveals three to five categories of structural error that would cause a live submission to be rejected. Fix those errors in your system configuration, not manually in the XML file. Manual edits break the audit trail and create reconciliation problems during a KAS inspection.

Phase four is the live submission and archiving. Submit through the e-Deklaracje gateway using a qualified electronic signature (podpis kwalifikowany) authorised by the company's management board. Archive the official receipt (UPO) together with the submitted XML file. Retention period under Polish tax law is five years from the end of the calendar year in which the tax obligation arose.

Your company's specific data situation may reveal gaps that require legal and tax-advisory input before submission. Leaving structural errors unaddressed precludes a clean audit trail and creates irreversible exposure to KAS penalties.

To receive an expert assessment of your JPK_CIT readiness, contact info@kordeckipartners.com. Our tax practice – led by a former Big Four senior manager – conducts structured readiness reviews covering account mapping, ERP configuration, and submission testing.

What are the three most common preparation mistakes?

Finance teams across Poland have now been through at least one JPK_VAT cycle. That experience helps – but JPK_CIT is structurally more demanding. VAT files capture transaction-level invoice data. JPK_CIT captures the entire general ledger. The volume and the mapping complexity are an order of magnitude higher. Three mistakes appear repeatedly in early-wave submissions.

Mistake one: treating JPK_CIT as an IT project rather than a tax project. The XML schema is technical. But the underlying question – whether your account structure correctly reflects CIT-relevant categories – is a tax question. Finance teams that delegate the entire preparation to IT without involving a tax advisor Warsaw-side often discover in the test phase that entire expense categories are incorrectly tagged. Retagging 12 months of historical entries takes weeks.

Mistake two: ignoring transfer pricing adjustments. Companies with related-party transactions frequently book transfer pricing corrections in a single clearing account. That account structure does not satisfy the JPK_CIT tagging requirement. Polish tax law requires each transfer pricing adjustment to carry an account tag that identifies it as an adjustment and links it to the relevant related party. We secured a correction of a transfer pricing tagging error for a manufacturing client in the Mazowieckie region (autumn 2025) – the correction required re-booking 47 journal entries across three quarters.

Mistake three: overlooking IP Box and R&D relief carve-outs. Companies claiming IP Box (preferential 5% CIT rate on qualifying IP income) or R&D relief must maintain a separate accounting record of qualifying revenues and costs. JPK_CIT requires those records to be reflected in dedicated ledger accounts. If your company has been running IP Box calculations in a spreadsheet outside the accounting system, you face a retroactive data-migration challenge before the submission deadline.

How do three business scenarios play out in practice?

Different company types face different JPK_CIT challenges. Three scenarios illustrate the range. Each scenario maps the primary risk, the recommended instrument, and a realistic preparation timeline. This decision matrix helps finance teams calibrate their own situation before engaging external advisors.

Scenario one: Polish manufacturing company, calendar fiscal year, revenue above EUR 50 million. This entity fell into wave one and faced the 31 March 2026 deadline. Its primary risk was a large chart of accounts (typically 400 to 600 accounts) with complex depreciation structures under JPK_ST_KR. Recommended instrument: a dedicated account-mapping project run jointly by the finance controller and a tax advisor, starting no later than September 2025. Timeline: four months for mapping, two months for ERP configuration and testing.

Scenario two: IT company, non-calendar fiscal year ending 30 September, claiming IP Box. This entity's deadline falls 31 December 2026 – not 31 March. The extra time is valuable. But the IP Box carve-out creates a structural challenge: qualifying and non-qualifying revenues must be segregated at account level, not just in a tax worksheet. Recommended instrument: a ledger restructuring project in the first quarter of the fiscal year, before transactions accumulate. We obtained a clean test-submission result for a software client in Małopolska (winter 2025–2026) after a six-week account-restructuring engagement.

Scenario three: foreign investor's Polish subsidiary, part of a multinational group. The subsidiary uses a group-wide ERP configured for IFRS reporting. JPK_CIT requires Polish statutory accounts under the Accounting Act (ustawa o rachunkowości). The gap between IFRS and Polish GAAP account structures can be significant. Recommended instrument: a parallel Polish statutory ledger maintained alongside the IFRS consolidation ledger, with a reconciliation layer that maps to the MF taxonomy. Timeline: allow at least three months for the parallel-ledger setup before the fiscal year begins. For context on how Polish tax reporting intersects with cross-border structures, see our analysis of the double tax treaty between Poland and Poland: key provisions.

What does the checklist for finance teams look like?

A practical checklist gives your team a concrete starting point. The items below reflect the most frequent gaps identified during JPK_CIT readiness reviews. Work through each item at least three months before your submission deadline. If any item is incomplete at the two-month mark, escalate immediately – some gaps require external specialist input that cannot be compressed into a few weeks.

  • Map every ledger account to the MF's mandatory account-type taxonomy and assign CIT tags
  • Activate and configure the JPK_CIT export module in your ERP or accounting software
  • Run a test submission in the MF sandbox and resolve all structural validation errors
  • Verify that transfer pricing adjustments, IP Box carve-outs, and R&D costs appear in dedicated accounts
  • Confirm that a qualified electronic signature authorised by the management board is available for live submission

Companies with a family foundation (fundacja rodzinna) holding CIT-exempt assets should verify whether the foundation's accounting records require a separate JPK_CIT submission. The rules differ from those applicable to standard operating companies. For entities active in real estate, note that property-related fixed assets require particularly precise depreciation tagging in JPK_ST_KR. More on structuring Polish real estate investments is available in our real estate practice overview.

Finance teams preparing for KSeF onboarding simultaneously should note that the two systems share the same e-Deklaracje submission gateway but have entirely separate XML schemas and validation rules. Parallel preparation is feasible but requires clear workstream separation. Our dedicated overview of the KSeF deadline timeline for 2026–2027 covers the intersection of both obligations for companies operating across borders.

Every company's ledger structure is specific. Errors embedded in your account mapping today will surface during a KAS audit – and correcting them post-submission forfeits the ability to present a clean, unaltered file as evidence of compliance.

For a tailored strategy on JPK_CIT preparation for your company – covering account mapping, ERP configuration, and test-submission support – reach out to info@kordeckipartners.com.

Frequently asked questions

Q: Can a company submit JPK_CIT using the same XML file it uses for JPK_VAT?

A: No. JPK_CIT and JPK_VAT are entirely separate schemas published by the Ministry of Finance. JPK_VAT captures invoice-level VAT transaction data. JPK_CIT captures general-ledger entries, profit-and-loss structure, and fixed-asset registers. The two files are submitted through the same e-Deklaracje gateway but require different authorisations and carry different validation rules. Attempting to repurpose a VAT-file structure for CIT purposes will result in an immediate schema-validation rejection.

Q: How long does a JPK_CIT readiness review typically take, and what does it cost?

A: For a company with a chart of accounts of up to 300 accounts and a standard ERP setup, a readiness review typically takes four to six weeks. The review covers account-taxonomy mapping, ERP export-module verification, and a test-submission run. Costs vary depending on ledger complexity and the volume of transfer pricing or IP Box adjustments. A preliminary scoping call with a tax advisor Warsaw-side – typically 60 minutes – is usually sufficient to estimate the engagement scope before any fee commitment.

Q: Is it a common misconception that JPK_CIT only applies to the annual CIT return period?

A: Yes, and it is an important one to correct. JPK_CIT is not submitted at the same time as the CIT annual return (CIT-8). The submission deadline is three months after the fiscal year-end – which for calendar-year companies means 31 March. However, the data preparation must cover the entire fiscal year in real time. Companies that wait until January to begin mapping their December ledger entries typically discover that entries booked throughout the year carry incorrect tags. Retroactive correction of a full year's journal entries is significantly more costly than maintaining correct tagging from the first month of the fiscal year.

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 tax compliance, JPK_CIT preparation, and CIT advisory. 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.