JPK_CIT 2026 — A Complete Guide for Companies
JPK_CIT (Jednolity Plik Kontrolny — Standard Audit File for corporate income tax) is a new reporting obligation for CIT (Corporate Income Tax) taxpayers effective from 2026. It requires the submission of detailed accounting records in XML format — in parallel with the CIT-8 annual return. This guide covers the scope of the obligation, file structure, deadlines, penalties, and practical implementation tips.
Legal basis
The obligation to submit JPK_CIT derives from Article 9(1c)–(1e) of the Act of 15 February 1992 on Corporate Income Tax (PDOP), as amended by the Act of 29 October 2021 (Journal of Laws 2021, item 2105), and transitional provisions set out in Article 66 of the Polish Deal 3.0 Act. The detailed logical structure of the file (XSD schema) is published by the Minister Finansów (MF — Minister of Finance) in the Public Information Bulletin pursuant to Article 193a § 2 of the Tax Ordinance (Ordynacja podatkowa). In 2026, the applicable schema version is JPK_KR_CIT(2) — this structure differs from the previous JPK_KR files (accounting books) as it contains additional nodes dedicated to CIT.
Who must file
The obligation applies to CIT taxpayers maintaining full accounting books: Sp. z o.o. (limited liability companies), joint-stock companies (S.A.), sp. komandytowa (limited partnerships), limited joint-stock partnerships, PSA (simple joint-stock companies — Prosta Spółka Akcyjna), branches of foreign companies registered in KRS (National Court Register), and tax capital groups (PGK). Small taxpayers (up to EUR 2 million in revenue) were exempt until 2025 — from 1 January 2026, they too must file JPK_CIT, albeit using a simplified structure (without the related-party transactions node, provided they do not exceed the documentation thresholds under Article 11k PDOP).
Who is NOT required to file
The following entities are exempt from the obligation:
- CIT taxpayers benefiting from subject-matter tax exemptions under Article 17(1) PDOP (e.g., public benefit organisations in respect of their statutory activities), provided their business activity revenue does not exceed PLN 100,000 per year;
- budgetary units and local government budgetary establishments whose records are maintained in TREZOR/BESTIA systems;
- taxpayers using Ryczałt od dochodów spółek (Estonian CIT — a lump-sum tax on distributed profits) — these entities file a separate JPK_EST file pursuant to Article 28r PDOP;
- companies in liquidation that completed their tax year before 1 January 2026.
What the file must contain — JPK_KR_CIT(2) structure
JPK_CIT comprises five main data nodes, submitted in XML format compliant with the MF schema:
| XML node | Content | Notes |
|---|---|---|
| Kontrahenci (Counterparties) | List of counterparties with NIP (tax identification number) or foreign identification number, name, registered address, and country code | Covers both domestic and foreign counterparties with transactions ≥ PLN 500 net |
| KontoZapis (Account Entries) | Records of entries in the general ledger — each entry with date, document number, debit/credit account, amount, and description | Synthetic and analytical accounts required down to level 3 |
| ObrSal (Trial Balance) | Statement of turnover and balances at the end of the reporting period | Must balance — discrepancies result in automatic file rejection |
| SrodkiTrwale (Fixed Assets) | Register of fixed assets and intangible assets with initial value, depreciation method and rate, and annual write-offs | Covers assets with a value > PLN 10,000 (threshold per Article 16a PDOP) |
| TransakcjePowiazane (Related-Party Transactions) | List of transactions with related parties (Article 11a PDOP) — parties, transaction type, value, transfer pricing method | Applies to transactions exceeding Article 11k PDOP thresholds: PLN 10 million (goods/services) or PLN 2 million (intangible services, financial transactions) |
The file is transmitted via the ePUAP (Electronic Platform of Public Administration Services) gateway or directly from the accounting system using the API provided by MF (JPK 2.0 gateway). The file must be signed with a qualified electronic signature, Profil Zaufany (Trusted Profile) on ePUAP, or authorisation data (revenue amount from the tax return for year n-2).
Practical example — Sp. z o.o. "Kowalski IT"
Kowalski IT Sp. z o.o. (tax year = calendar year) generated PLN 4.2 million in revenue and PLN 3.1 million in deductible costs in 2026. The company has 12 fixed assets (servers, vehicles, licences) and 87 domestic counterparties plus 3 foreign ones. It conducts transactions with a related party — its parent company in Germany — totalling PLN 1.8 million annually (management services).
Step by step — generating JPK_CIT:
- Year-end closing: The company closes its accounting books for 2026 no later than 31 March 2027 (Article 12(2) of the Accounting Act).
- Chart of accounts review: The accounting department verifies that the analytical structure of accounts allows data export at the level required by the schema — e.g., whether account 201 (Trade receivables) has per-counterparty analytics with correct NIP.
- System export: From the Comarch Optima software, the company generates the JPK_KR_CIT(2) file — the option is available under "Declarations → JPK → JPK_CIT". The system automatically populates the KontoZapis, ObrSal, and SrodkiTrwale nodes.
- Related-party transactions supplement: Since the transaction with the German entity (PLN 1.8 million) exceeds the PLN 2 million threshold for intangible services — no, in this case it is below the PLN 2 million threshold, so the TransakcjePowiazane node is not required. If the value were, for example, PLN 2.5 million, the company would need to populate the transfer pricing method data.
- Validation: The file is validated using the MF tool (JPK Validator) — it checks schema compliance, balance reconciliation, and NIP correctness.
- Submission: The file, signed with a qualified electronic signature of a management board member, is sent via the JPK 2.0 gateway by 31 March 2027.
Deadline and penalties
The first JPK_CIT for 2026 must be filed by 31 March 2027 — this deadline coincides with the CIT-8 return filing deadline (Article 27(1) PDOP). If the company's tax year differs from the calendar year, the file must be submitted by the end of the third month after the tax year ends.
| Violation | Penalty | Legal basis |
|---|---|---|
| Failure to file JPK_CIT on time | Fine from PLN 1,200 to PLN 33,600 (fiscal misdemeanour) or up to 720 daily rates (fiscal crime where the tax shortfall exceeds 5× the minimum wage) | Article 80 § 1 and § 3 of the Fiscal Penal Code (KKS) |
| Formal errors in the file structure | Request to correct within 14 days — failure to correct results in a fine of up to PLN 4,500 | Article 80 § 4 KKS in conjunction with Article 193a § 3 of the Tax Ordinance |
| Concealing related-party transactions | Additional tax liability of 10% of overstated loss or 10% of understated income (minimum PLN 5,000), and in case of non-cooperation — double rate (20%) | Article 11o(1)–(3) PDOP |
| Unreliable fixed asset records | Depreciation write-offs challenged + interest on tax arrears (currently 14.5% per annum) | Articles 16a–16m PDOP, Article 53 § 1 of the Tax Ordinance |
Note: In the case of voluntary disclosure (czynny żal — Article 16 § 1 KKS) submitted before proceedings are initiated, the taxpayer may avoid the fine — provided the overdue JPK_CIT is filed simultaneously and any tax due is paid with interest.
Most common implementation errors
- No per-counterparty analytics: If the chart of accounts does not provide for receivables/payables broken down by counterparty, the generated file will lack the required NIP numbers. Solution: adjust the chart of accounts no later than 1 January of the tax year.
- Debit/credit discrepancies: Even a 1-grosz difference in turnover and balances causes the MF validator to reject the file. Regular reconciliation of turnover during the year eliminates this problem.
- Incorrect country codes: For foreign counterparties, the ISO 3166-1 alpha-2 code is required (e.g., "DE", "GB"). Common error: entering "D" instead of "DE" for Germany.
- Omitting intangible assets: Intangible assets (licences, trademarks) must also be included in the SrodkiTrwale node — not only tangible fixed assets.
- Outdated software: XSD schemas change — the accounting system must support the current JPK_KR_CIT(2) version. Check with your software provider for updates.
- Signature by an unauthorised person: JPK_CIT must be signed by a person authorised to represent the company (management board member, proxy holder) or an attorney-in-fact with a UPL-1 power of attorney filed with the tax office.
JPK_CIT vs. other reporting obligations — comparison
| Obligation | Who files | Frequency | Deadline | Format |
|---|---|---|---|---|
| JPK_VAT (JPK_V7M/K) | Active VAT taxpayers | Monthly / quarterly | 25th day of the following month | XML |
| JPK_CIT (JPK_KR_CIT) | CIT taxpayers (full accounting) | Annually | End of 3rd month after tax year-end | XML |
| CIT-8 (annual return) | CIT taxpayers | Annually | End of 3rd month after tax year-end | Electronic form |
| Financial statements | Entities maintaining full accounting books | Annually | 3 months after balance sheet date (preparation); 15 days from approval (filing with KRS) | XML (e-sprawozdanie) |
| TP-R (transfer pricing information) | Taxpayers conducting related-party transactions above thresholds | Annually | End of 11th month after tax year-end | XML form |
It is worth noting that JPK_CIT does not replace the CIT-8 return or financial statements — it is an additional record-keeping obligation. However, much of the data overlaps, meaning consistency between these documents will be verified automatically by KAS (Krajowa Administracja Skarbowa — National Revenue Administration) analytical systems.
Step by step — how to prepare
- Q3 2026 — accounting system audit: Check whether your software (Symphonia, Optima, Comarch ERP XL, Sage, enova365, Insert) has a JPK_KR_CIT(2) export module. If not — contact your provider or consider switching software.
- Q3 2026 — chart of accounts review: Ensure that the account analytics allow assigning a counterparty's NIP to every receivable/payable entry. Expand the chart of accounts if necessary.
- Q4 2026 — test export: Generate a trial JPK_CIT file using current data and validate it with the MF tool. Identify and fix errors before the tax year ends.
- January 2027 — year-end closing: Conduct inventory, calculate December depreciation, reconcile balances with counterparties (balance confirmations).
- February 2027 — final file generation: Export the JPK_CIT file from closed books. Compare the data with the draft CIT-8 — revenue and cost figures must be consistent.
- March 2027 — submission: Sign the file and send it via the JPK 2.0 gateway. Retain the UPO (Official Acknowledgement of Receipt) — it serves as proof of timely filing.
FAQ — Frequently Asked Questions
Does a company on Estonian CIT have to file JPK_CIT?
No. Taxpayers subject to Ryczałt od dochodów spółek (Estonian CIT, Articles 28c–28t PDOP) file a separate JPK_EST structure. The JPK_CIT obligation applies exclusively to taxpayers using the standard rules (19% CIT or 9% CIT for small taxpayers).
Does a foundation or association have to file JPK_CIT?
Yes, if it is a CIT taxpayer maintaining full accounting books and generates revenue from business activity. Foundations benefiting from the exemption under Article 17(1)(4) PDOP (income allocated to statutory purposes) do file JPK_CIT but may use the simplified structure — without the TransakcjePowiazane node.
What if the company has no related-party transactions?
The TransakcjePowiazane node in the XML file remains empty (but must exist in the structure). This does not trigger any additional documentation obligations.
Can I file a corrected JPK_CIT?
Yes. A correction is filed under the same rules as a CIT-8 correction — within the statute of limitations for the tax liability (Article 81 § 1 of the Tax Ordinance), i.e., generally 5 years from the end of the year in which the tax payment deadline fell. The correction requires an attached justification (ORD-ZU form).
What are the file size limits?
The JPK 2.0 gateway accepts files up to 300 MB after compression (ZIP). For larger files — e.g., large capital groups — MF provides a file-splitting mode (segments), but this requires a specific XML header.
Does JPK_CIT apply to civil law partnerships?
Not directly. A civil law partnership (spółka cywilna) is not a CIT taxpayer — the taxpayers are the individual partners (natural persons filing PIT). However, if the civil law partnership maintains full accounting books (mandatory when revenue exceeds EUR 2 million), the partners may be required to file JPK_PIT (a separate structure, planned from 2027).
Summary
JPK_CIT represents a significant change in tax reporting for companies from 2026. Begin preparations in Q3 2026 — verify that your accounting system has a JPK_CIT export module. Most software (Symphonia, Optima, Comarch) provides it automatically after an update. The key is ensuring data consistency between JPK_CIT, the CIT-8 return, and the financial statements — inconsistencies will be verified automatically by KAS algorithms. Do not wait until the last moment: test the export on trial data, validate the file, and reconcile the chart of accounts before the 31 March 2027 deadline arrives.