JPK_CIT is the market shorthand for the new annual electronic reporting of accounting books for income-tax purposes. It is not the name of a single statutory file. A company keeping accounting books normally works with two official structures: JPK_KR_PD for the books and tax reconciliation, and JPK_ST_KR for fixed assets and intangible assets. The change is therefore not a final-year export exercise: it affects the chart of accounts, contractor data, KSeF identifiers, tax adjustments and the audit trail throughout the year.
1. JPK_CIT is a shorthand, not an official file name
The Ministry of Finance uses the umbrella term JPK_PD for structured income-tax books. For entities keeping full accounting books, the relevant files are JPK_KR_PD and JPK_ST_KR. JPK_KR_PD reports the accounting-book data and the reconciliation between the accounting result and taxable result. JPK_ST_KR reports the tax and accounting records of fixed assets and intangible assets. CIT-8 remains a separate return and is not replaced by either file.
| Common expression | JPK_CIT — practical label used by the market |
|---|---|
| Official umbrella | JPK_PD — structured books for income taxes |
| Accounting books | JPK_KR_PD(1), current scheme version v1-1 |
| Fixed assets and intangibles | JPK_ST_KR(1), current scheme version v1-0 |
| Annual tax return | CIT-8 — submitted separately under its own rules |
2. Who enters the reporting duty and when?
| Years beginning after 31 December 2024 | tax capital groups and CIT taxpayers whose preceding-year revenue exceeded EUR 50 million; each PGK company files its own books |
|---|---|
| Years beginning after 31 December 2025 | the next group, including taxpayers and entities covered by the statutory monthly JPK_V7M stage and PIT taxpayers keeping accounting books within that stage |
| Years beginning after 31 December 2026 | the remaining taxpayers and entities, including the final quarterly JPK_V7K stage |
The threshold is tested under the statutory rule and converted using the NBP rate specified in the transitional provisions. A non-calendar tax year can move the first report into a different filing cycle. Entities exempt from CIT under Article 6(1) are outside the Article 9(1c) duty. Status must therefore be checked for the reporting entity itself; the nationality of its shareholders does not determine the obligation.
3. Which files must a company prepare?
A company keeping accounting books should plan for both structures. JPK_KR_PD is the core file. JPK_ST_KR is the related fixed-asset register. The special exemption made JPK_ST_KR optional for the first group only for a tax or financial year beginning in 2025. It does not create a permanent exemption. For a year beginning after 31 December 2025, the ordinary implementation design should assume both files are required unless a specific legal exclusion applies.
| JPK_KR_PD | taxpayer and period data, contractor dictionary, trial balance, journal records, ledger postings and the RPD tax reconciliation |
|---|---|
| JPK_ST_KR | fixed assets and intangibles, source documents, initial values, depreciation/amortisation, changes and disposal data |
| Supporting evidence | chart-of-accounts mapping, tax-adjustment register, KSeF links, validation reports, filing status and UPO |
4. Filing deadline after the 2026 amendment
Since 1 July 2026, CIT taxpayers subject to Article 9(1c) file the accounting books by the end of the seventh month after the tax year. Partnerships without legal personality covered by Article 9(1e) use the seventh month after the financial year. This permanent rule replaced the earlier link to the CIT-8 deadline. The 2026 extension regulation had already moved specified first filings to the seventh month; the later Act made that timing part of the statute.
| Calendar tax year 2025 — first large-taxpayer group | statutory extended period ended 31 July 2026 |
|---|---|
| Calendar tax year 2026 — monthly-stage group | seventh-month period ends 31 July 2027; general Saturday rule indicates 2 August 2027 |
| Non-calendar year | count seven months from the actual tax/financial year end and then apply general deadline rules |
| CIT-8 | remains a separate filing with a different legal deadline |
5. What JPK_KR_PD contains
JPK_KR_PD is designed to reconstruct how transactions move from the journal into ledger accounts and into the tax reconciliation. The file combines identifiers and reporting-period data with contractor references, the trial balance, journal entries, account-level postings and control totals. The last reported period also contains the RPD node. Referential consistency matters: contractor codes, account codes, document numbers and amounts must connect across sections without gaps or duplicates.
| Master data | NIP and taxpayer/contractor identifiers appropriate to the reported event |
|---|---|
| Accounting structure | chart of accounts, opening/closing balances and turnovers |
| Transaction path | journal event, document reference, account entry and amount |
| Tax layer | account tags and RPD reconciliation |
| Control layer | sequence, continuity, totals, XML validation, submission status and UPO |
6. Account tags require a documented mapping
The chart of accounts must be mapped to the Ministry’s accounting tags derived from the balance sheet and profit-and-loss presentation. Where accounts are used for income-tax reconciliation, the appropriate PD tax tags are also relevant, including off-balance-sheet PD tags when the tax calculation is maintained there. The mapping should be approved by accounting and tax owners, versioned and tested against the current schema; software default tags are not a substitute for the entity’s accounting judgement.
| Step 1 | inventory all synthetic and analytical accounts used in the reporting year |
|---|---|
| Step 2 | identify the financial-statement presentation and required accounting tag |
| Step 3 | identify accounts used for permanent or temporary tax differences and assign PD tags |
| Step 4 | record the rationale, effective date and owner of each mapping |
| Step 5 | test unused, new, closed, foreign-currency and off-balance-sheet accounts |
| Step 6 | repeat the mapping review after chart, schema or business changes |
7. RPD must reconcile accounting and tax results
The RPD node explains the difference between the accounting result and the income-tax result through eight consolidated categories of income and cost differences. It is not a copy of CIT-8 and does not divide the figures into capital gains and other income. Ministry guidance states that RPD values are entered manually in the structure but should reconcile to result and off-balance-sheet accounts carrying the corresponding PD tags. Only the file closing the reported year contains final RPD values; partial files show zero.
| Permanent income differences | exempt or otherwise excluded income |
|---|---|
| Timing income differences | income taxed in another period or outside current books |
| Permanent cost differences | non-deductible costs |
| Timing cost differences | costs deductible in another period or not posted in current books |
| Reconciliation control | RPD totals versus tagged accounts and the tax computation |
8. JPK_ST_KR is more than a list of assets
JPK_ST_KR combines accounting and tax information on each fixed asset or intangible: identification, source evidence, acquisition or production, acceptance for use, initial values, depreciation or amortisation, changes and removal from the register. The source-document and KSeF fields depend on the underlying event. Historic assets may benefit from limited transitional simplifications, but additions, disposals and changes in the reporting year still require reliable evidence and dates.
| Asset master | inventory number, description, classification and status |
|---|---|
| Source evidence | document number/type, acquisition or production dates and KSeF number where applicable |
| Valuation | accounting and tax initial values plus changes |
| Depreciation | methods, rates, charges and accumulated amounts |
| Lifecycle | acceptance for use, improvement, partial liquidation, sale or other removal |
| Control | agreement with the general ledger, tax depreciation and financial statements |
9. Contractor and KSeF data link the files to source documents
Contractor codes reported in JPK_KR_PD must match the entity’s own master-data key and refer to contractors with transactions in the reporting period. The D_12 field is required for an operation documented by an invoice or correction issued in KSeF by the reporting entity when a KSeF number was assigned. The 2025 first-group relief for NIP, KSeF number and RPD data does not apply as a general relief to years beginning after 31 December 2025.
| Customer/vendor master | unique internal code, NIP/foreign identifier and change history |
|---|---|
| Sales invoice | business document, KSeF number, journal entry and ledger posting linked |
| Purchase evidence | correct supplier identifier and accounting reference |
| Corrections | original document, corrected document and resulting accounting/tax entry linked |
| Exceptions | documented reason where a field is not applicable under the schema |
10. A reliable preparation and validation process
- Determine the first reporting year separately for every legal entity and partnership.
- Freeze a controlled chart-of-accounts and PD-tag mapping.
- Clean contractor, document, KSeF and asset master data before year-end.
- Generate test JPK_KR_PD and JPK_ST_KR files during the year.
- Validate XML against the current XSD and current MF technical specification.
- Reconcile trial balance, journal, postings, RPD, fixed assets and CIT calculation.
- Investigate gaps, duplicates, rejected records and unmapped accounts.
- Approve the final version, sign, submit and retain UPO and the audit trail.
The Ministry provides the schemes, brochures, a technical interface specification and Klient JPK WEB. An accounting system may also generate and transmit the files if it supports the current format. Acceptance by the gateway confirms delivery, not the substantive correctness of accounting or tax classification. The company should retain the exact submitted file, validation report, signatory, transmission status and UPO.
11. Responsibility, authorisation and common errors
Management remains responsible for reliable books and tax data even when an accounting office or software provider prepares the export. From June 2026, an electronic-declaration power of attorney filed on UPL-1 also authorises signature of the relevant income-tax books; no separate JPK_PD power is required. The engagement should still allocate who maps accounts, resolves data errors, approves RPD, signs the file, monitors status and stores UPO.
- treating JPK_CIT as one file and omitting JPK_ST_KR;
- using the old CIT-8 deadline after the July 2026 amendment;
- assigning tags only during the final export without accounting approval;
- forcing RPD to equal CIT-8 without a documented bridge;
- missing KSeF numbers or inconsistent contractor codes;
- failing to reconcile the asset register to the ledger and tax depreciation;
- accepting a technically valid XML as proof of tax correctness;
- sharing signing credentials or failing to archive the exact file and UPO.
12. JPK_CIT implementation checklist
- Confirm the entity, tax year and implementation group.
- Confirm whether both JPK_KR_PD and JPK_ST_KR are required.
- Update the chart-of-accounts and PD-tag mapping.
- Prepare contractor, KSeF and document identifiers.
- Reconcile the fixed-asset register and lifecycle evidence.
- Build a repeatable RPD bridge from accounting result to tax result.
- Test current XSD, file size, signature, transmission and UPO.
- Define corrections, access, approval and retention.
- Run a dry filing before the year-end close.
- Recheck the law, MF materials and calendar immediately before submission.
inPL can coordinate accounting in Poland, accounting and tax audit and IT services for JPK_CIT readiness, including data mapping, reconciliations, process design and technical requirements.
Information verified on 20 August 2026. The reporting duty depends on the taxpayer, legal form, tax or financial year and transitional group. Before implementation or filing, recheck the CIT Act, the Tax Ordinance, current regulations, MF schemes, brochures and technical specifications.