A Warsaw-based IT services company with a dozen subsidiaries receives a notice from the National Tax Administration (Krajowa Administracja Skarbowa, KAS): its JPK_CIT file for the prior fiscal year contains mapping errors across three cost categories. The correction window is tight. The finance director realises the team had been preparing data in spreadsheets, not in the structured XML schema that Polish tax law now requires. The cost of that gap – in penalties, rework, and auditor time – quickly exceeds the cost of proper preparation.

JPK_CIT is the structured electronic accounting file that Polish corporate income tax payers must submit to the KAS alongside their annual CIT return. The obligation entered into force in phases: large taxpayers (annual revenue above EUR 50m) were first in scope, with smaller entities following on a rolling schedule. Finance teams must map their general ledger accounts to a prescribed XML schema, reconcile the output with the CIT-8 return, and submit both files by the statutory deadline – typically the end of the third month after the fiscal year closes.

This guide walks through the four practical stages your finance team must complete: understanding the scope and timeline, building the data architecture, avoiding the most common mapping mistakes, and stress-testing the output before submission. Each stage includes a concrete checkpoint so you can track readiness without guessing.

Who is in scope and when does the obligation apply?

The JPK_CIT obligation under Polish tax law applies to all entities subject to corporate income tax (CIT) that keep accounting books in Poland. The phased rollout is the key scheduling tool. Large taxpayers – those whose annual revenues exceed EUR 50m – submitted their first JPK_CIT files for fiscal years beginning on or after 1 January 2025. Mid-size and smaller CIT payers follow in subsequent years, with the obligation extending to virtually all CIT entities by fiscal year 2026.

Three categories of entities deserve special attention. First, tax capital groups registered with the National Court Register (Krajowy Rejestr Sądowy, KRS) must submit a consolidated JPK_CIT covering all group members. Second, companies that hold an IP Box ruling from the KAS must ensure their qualifying IP income streams are mapped separately within the schema – a requirement that catches many IP-intensive businesses off guard. Third, entities with transfer pricing documentation obligations face an additional layer: the JPK_CIT data must be consistent with the local file submitted to the Head of the National Revenue Administration (Szef Krajowej Administracji Skarbowej).

Foreign investors running a Polish subsidiary often underestimate the reach of this obligation. Even a single-purpose holding vehicle registered in Poland and subject to CIT falls within scope. If your Polish entity generates passive income – dividends, royalties, interest – those streams must appear in the JPK_CIT with their correct account codes. Missing a revenue stream is treated as an error, not an omission, and triggers a correction request from KAS.

  • Large taxpayers (revenue above EUR 50m): JPK_CIT from fiscal year starting 1 January 2025
  • Mid-size taxpayers: fiscal years starting 1 January 2026
  • Remaining CIT payers: fiscal years starting 1 January 2027
  • Tax capital groups: consolidated submission required from day one of group obligation

The practical implication: if your fiscal year runs from January to December, the first large-taxpayer submission is due by the end of March 2026. That deadline is already inside the planning horizon of most finance teams reading this guide.

How should your finance team build the data architecture?

Correct JPK_CIT preparation begins not with the XML file but with the chart of accounts. Polish accounting legislation requires that every general ledger account used during the fiscal year be mapped to a corresponding code in the JPK_CIT schema. That mapping must be documented, approved by the chief accountant, and retained for at least five years – the standard tax inspection window under Polish tax law.

Start with a gap analysis. Export your current chart of accounts and compare it against the official JPK_CIT schema published by the Ministry of Finance (Ministerstwo Finansów). The schema distinguishes between balance sheet accounts, profit-and-loss accounts, and off-balance-sheet items. Each category uses a separate XML node. A manufacturing company in the Mazowieckie region discovered during our readiness review (autumn 2025) that roughly 18% of its cost accounts had no direct equivalent in the schema – requiring either account consolidation or the creation of new sub-accounts before the fiscal year closed.

The next step is system configuration. Most ERP platforms – SAP, Oracle, Comarch ERP XL – support JPK_CIT export natively, but the mapping table must be configured manually. Do not rely on vendor defaults. Default mappings are generic; your chart of accounts reflects your specific business model. Allocate at least four to six weeks for configuration, test exports, and reconciliation against the trial balance. That timeline assumes a single legal entity. Groups with multiple Polish entities should double it.

Two integration points require particular care. First, the opening balance must match the prior year's closing balance exactly – down to the last grosz. Any rounding difference generates a schema validation error. Second, intercompany transactions must be eliminated at the account level before the JPK_CIT is generated, not as a post-processing adjustment. KAS cross-references JPK_CIT files submitted by related parties and flags asymmetries automatically.

What are the most common mapping mistakes to avoid?

Experience across multiple KAS audits points to three recurring errors. Each carries a direct financial consequence: a penalty of up to PLN 240 per day for late or incorrect submission, with no upper cap specified in current regulations. The risk compounds when KAS opens a full CIT audit on the back of JPK_CIT discrepancies.

The first mistake is misclassifying non-deductible costs. Polish tax law contains a long list of costs that are recognised in the accounting books but excluded from the CIT base – entertainment expenses, certain penalties, and thin-capitalisation interest, to name three. In the JPK_CIT schema, these items must be coded as non-deductible. Finance teams that import them under a generic cost code effectively overstate the deductible cost base. KAS reconciles this against the CIT-8 return and raises a discrepancy notice within weeks of submission.

The second mistake involves family foundation distributions. Since May 2023, Polish law recognises the fundacja rodzinna (family foundation) as a separate legal entity subject to a 15% CIT on distributions to beneficiaries. If your group structure includes a family foundation that holds shares in an operating company, the dividend flow between the foundation and the company must be coded correctly in both entities' JPK_CIT files. Coding it as an intra-group loan repayment – a common error – triggers a reclassification and potential penalty interest.

The third mistake is the treatment of KSeF-issued invoices. Poland's Krajowy System e-Faktur (National e-Invoice System, KSeF) assigns a unique identifier to each invoice. Under current guidance from the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) and the Ministry of Finance, JPK_CIT entries for costs supported by KSeF invoices should reference the KSeF identifier in the relevant XML field. Finance teams that omit this reference create a reconciliation gap between the JPK_CIT and the JPK_VAT file – a mismatch KAS detects automatically. For more on KSeF timelines, see our KSeF deadline and timeline guide for 2026–2027.

How do you stress-test the file before submission?

Submitting an untested JPK_CIT file is the single largest avoidable risk in the process. The Ministry of Finance provides a free validation tool that checks schema compliance – but schema compliance is not the same as substantive correctness. A file can pass schema validation and still contain classification errors that trigger a KAS audit. Your stress-test must go further than the official validator.

Run four reconciliation checks. First, total revenues in the JPK_CIT must equal total revenues declared in the CIT-8 return. Second, total deductible costs in the JPK_CIT must equal the cost figure in the CIT-8 return. Third, the opening balance of each account must match the prior year's closing balance as reported in the prior year's JPK_CIT. Fourth, intercompany balances must net to zero across all Polish entities in the group. Any discrepancy in checks one through four is a submission-blocking error.

We secured a correction of a JPK_CIT mapping error worth over PLN 1.5m in disallowed costs for a logistics client in Lower Silesia (spring 2026). The error arose because the client's ERP system had been updated mid-year and the mapping table was not refreshed. The lesson: run a test export after every ERP update, not just at year-end.

For foreign-owned Polish subsidiaries, an additional check is essential. Polish corporate governance rules – discussed in detail in our corporate governance guide for Poland subsidiaries – require the management board to approve the annual financial statements before the CIT return is filed. The JPK_CIT must reflect the approved financial statements, not the draft. Submitting a JPK_CIT based on draft figures and later amending it after board approval is a correctable but time-consuming error.

  • Run the Ministry of Finance schema validator at least 30 days before the deadline
  • Complete all four reconciliation checks against the CIT-8 return
  • Confirm management board approval of financial statements before submission
  • Retain the mapping documentation and test-export logs for at least five years
  • Check KSeF identifier fields for all cost entries supported by e-invoices

The bridge between preparation and submission is a signed sign-off checklist. Assign a named individual – not a team – accountability for each of the four reconciliation checks. KAS increasingly treats unsigned or undocumented preparation processes as evidence of inadequate internal controls, which escalates a routine correction request into a full audit.

Specific JPK_CIT questions often arise in the context of broader Polish tax treaty obligations. Our overview of key Polish tax treaty provisions addresses how double-taxation relief interacts with the CIT base your team is reporting.

Every finance team that has not yet completed a gap analysis between its chart of accounts and the JPK_CIT schema is already behind the preparation curve. Closing that gap after the fiscal year ends – rather than before – forfeits the opportunity to correct account structures without a formal amendment procedure, an outcome that is both more expensive and more visible to KAS.

To receive an expert assessment of your JPK_CIT readiness, contact info@kordeckipartners.com.

Frequently asked questions

Q: Can a Polish branch of a foreign company be required to submit JPK_CIT?

A: A registered branch (oddział) of a foreign company that is subject to Polish CIT on income attributable to the branch falls within the JPK_CIT obligation. The branch must maintain a separate Polish accounting record and map that record to the JPK_CIT schema. The parent company's foreign accounts are not included, but any intercompany charges allocated to the branch must appear in the branch's JPK_CIT with the correct deductibility code.

Q: How much does JPK_CIT preparation typically cost for a mid-size company?

A: For a single Polish entity with a standard chart of accounts and one ERP system, the one-off setup cost – covering gap analysis, mapping configuration, and test submissions – typically runs between PLN 15,000 and PLN 40,000 depending on system complexity. Ongoing annual costs are lower, usually PLN 5,000 to PLN 15,000, assuming no major changes to the account structure. Groups with multiple Polish entities should budget per entity, not per group.

Q: Is it true that JPK_CIT replaces the obligation to file the CIT-8 return?

A: This is a common misconception. JPK_CIT does not replace the CIT-8 return. Both files must be submitted. The JPK_CIT provides the granular account-level data that supports the aggregate figures in the CIT-8. KAS uses the two files together to verify the accuracy of the declared tax base. Submitting only one of the two – even if it is technically correct – constitutes non-compliance and triggers a penalty.

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 readiness, KSeF onboarding, 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.