JPK CIT correction: how to fix errors from the first reporting cycle? It is not too late

A JPK CIT correction, i.e. amending a successfully submitted JPK_KR_PD file, is possible when the original file was accepted by the Ministry of Finance system

If the system rejected the file, no effective submission has yet taken place, so there is nothing to correct. In such a situation, a correct file must be prepared and sent as an original submission. If the deadline has already passed, the matter requires additional assessment in terms of late submission of the books and possible voluntary disclosure (czynny żal).

In this article, we explain when a JPK_CIT correction is justified, how to prepare it technically and substantively, when correcting the file alone is not enough, and in which cases a CIT-8 correction or voluntary disclosure must be considered separately.

First JPK CIT file sent in a hurry? Why it is worth verifying the data submitted

The first JPK CIT reporting is worth verifying because the JPK_KR_PD file is not an ordinary tax return, but an electronic representation of the accounting books submitted to the tax authority. The authority may compare data from JPK_KR_PD with the CIT-8 return, the financial statements, JPK_VAT files and, ultimately, other electronically reported data, including data from structured invoices. An error in JPK_CIT does not always mean an error in the tax settlement itself, but it may increase the risk of questions, requests for explanations or verification activities.

Time pressure during the first reporting is the main reason why it is worth reviewing the file again after submission. During implementation, taxpayers simultaneously map the chart of accounts to tax tags, adapt their finance and accounting systems, test data exports and set rules for possibly splitting the file into parts. The JPK_KR_PD file should cover all book entries for the reporting period. If the books are kept in more than one system, the data must be combined into a complete picture of the books, without gaps, duplicates or omitted accounts.

When should a JPK CIT correction be submitted? Different consequences of technical and substantive errors

A JPK CIT correction is submitted when the original file was successfully accepted by the Ministry of Finance system, and after submission formal errors, amount errors or other substantive irregularities were identified in it. A distinction must be made between an error in a file that has already been accepted and a technical error that prevented the file from being submitted. These are two different situations and require different actions.

Technical errors, i.e. non-compliance with the schema, are not a correction

If the file did not pass validation and the Ministry of Finance system did not accept it, there is no question of a correction yet, because nothing was effectively submitted. The file must be corrected and sent again as an original submission.

Such errors include, among others, missing mandatory fields, non-compliance with the XSD, i.e. the formal template of the XML structure, an incorrect electronic signature, or the absence of valid authorisation of the person signing the file on behalf of the taxpayer. The corrected file, provided that it was not originally accepted, should be marked as the first submission, i.e. with the value “1” in the CelZlozenia field. If the submission deadline has already passed, the problem is not a correction, but late submission of the books. In such a case, the risk of fiscal penal liability and the justification for filing a voluntary disclosure should be assessed separately.

Substantive errors, i.e. incorrect tags, an incomplete picture of the books or incorrect data

A substantive error is an irregularity in a file that has already been successfully accepted. It may concern, for example, an incorrect reporting period, an incorrect tax office code, incorrect taxpayer identification data, omission of part of the books, incorrect balances or turnover, inconsistency between synthetic and analytical accounts, or incorrect tax tags assigned to accounts. Errors of this kind may justify a correction, because the file already exists in electronic circulation as submitted, but its content does not correctly reflect the books.

One reservation is particularly important for the first reporting. The Regulation of the Minister of Finance of 16 August 2024 on additional data for accounting books (Journal of Laws 2024, item 1314), as amended by the Regulation of the Minister of Finance and Economy of 15 December 2025 (Journal of Laws 2025, item 1828), provides for transitional simplifications. For the tax year beginning after 31 December 2024 and before 1 January 2026, and in the case of companies without legal personality for the corresponding financial year, the books may omit some of the additional data, in particular the counterparty’s tax identification number (NIP), data on fixed assets and intangible assets, and data from the RPD node, i.e. information on differences between the accounting result and the tax result. The absence of this data for the first reporting year should therefore not in itself be treated as a typical error requiring a correction, provided that the taxpayer falls within the scope of the transitional provision.

Precision is needed, however. The simplification applies only to the specified additional data. It does not mean a general exemption from the obligation to reflect the books faithfully and completely to the extent required for a given year. As a rule, for the first reporting year, the correct presentation of the books and the proper assignment of account identification tags are of key importance. However, special rules must be taken into account for taxpayers preparing financial statements in accordance with IFRS/IAS, for whom the exemption from the obligation to supplement the books with additional data in the form of account identification tags has been extended until 1 January 2028.

It is also worth remembering that the optional status of a field in the logical structure does not always mean it may be left blank at will. If a given field is technically optional, but in a given situation a value resulting from the books or from the requirements of the structure should be assigned to it, failure to complete it may be a substantive error.

How to submit a JPK CIT file correction step by step?

A JPK_KR_PD correction involves resubmitting all data for the corrected period, not sending only the difference compared to the original file. Therefore, the first step is not to fix one field in the XML, but to determine what scope of data the new, complete file must cover.

Confirm whether the original submission was successful

Check the processing status of the file and download the official confirmation of receipt (UPO). If the file was rejected, the matter does not concern a correction, but a correct original submission.

Determine the scope of the correction

For an annual file, the correction covers the full scope of data of the original file for the given tax or financial year. For partial files, split into shorter periods, the correction should cover the same partial period to which the original file related. If the error affects subsequent partial periods, those later parts must also be corrected, maintaining full continuity without gaps or duplicates.

Correct the data at source

A correction should not be a manual modification of the final XML file detached from the books. It should result from correcting the data in the finance and accounting system or in the layer that transforms the data into JPK. This matters for evidential purposes, because JPK_KR_PD is an electronic representation of the books and should remain consistent with them.

Generate the file in the structure appropriate for the corrected period and mark the purpose of submission as a correction

In the JPK_KR_PD structure, the CelZlozenia field is used to indicate whether the file is being submitted for the first time or as a correction. For a correction, the value provided for corrections, i.e. “2”, must be used. Before submission, the current version of the schema, the information brochure and Ministry of Finance announcements should be checked, because if the structure changes, it must be verified which version MF allows for corrections of a given period.

Verify the file in two stages before submission

First, a technical validation should be carried out: compliance with the XSD, correctness of the signature, validity of the signatory’s authorisation, technical limits of the submission channel, and compliance with the requirements of the API or the Klient JPK WEB application. Next, a substantive validation should be carried out: consistency with the books, completeness of accounts, correctness of balances, mapping of tax tags, continuity of periods and the relationship to the CIT-8 return.

Send the correction and keep documentation of the decision

It is worth documenting internally why a given error required a correction, which source data confirm the correct version, and whether the error affected the CIT-8. There is currently no standard separate form for justifying a JPK_CIT correction, but an internal decision trail may be of significant importance if the authority raises questions later.

Whether a JPK_CIT correction entails a correction of the CIT-8 return requires a separate decision. If the error concerned only technical or formal data or the way data was presented in the file, and the CIT-8 return correctly reported income, loss, the tax base and the tax, a JPK_KR_PD correction may be sufficient. If, however, the error affects taxable revenue, tax-deductible costs, loss, income, the tax base or the tax due, a JPK correction alone does not remove the effect on the settlement. In that case, a correction of the return under Art. 81 of the Tax Ordinance Act, payment of the tax arrears and interest, and possibly a voluntary disclosure must be considered separately.

Under the current legal framework, a tax return is corrected by filing a corrective return, which follows from Art. 81 § 2 of the Tax Ordinance Act. However, the rules applicable to corrections of tax returns should not be automatically transferred to a JPK_KR_PD correction. JPK_KR_PD is a transfer of books in a logical structure, not a CIT-8 return. Therefore, in practice, two levels must be separated: the correction of the JPK_KR_PD file and a possible correction of the CIT-8 return if the error affects the tax settlement.

It is also worth monitoring planned changes. In 2026, a draft act amending the Tax Ordinance Act and certain other acts, numbered UDER111, was published in the List of Legislative and Programme Work of the Council of Ministers. The draft is intended to standardise the rules for correcting electronically submitted tax books and move them to the general provisions of the Tax Ordinance Act. Until the changes are enacted and enter into force, the currently applicable provisions and the MF explanations on JPK_KR_PD should be relied upon.

JPK CIT errors and sanctions: will a correction protect against a penalty?

A correction submitted on the taxpayer’s own initiative may reduce the risk of liability, but it is not an automatic “amnesty” and does not replace voluntary disclosure if an act has already been committed that may constitute a fiscal petty offence or a fiscal offence. A JPK_CIT correction and voluntary disclosure are two different legal instruments.

Legal basis

The basis for sanctions is Art. 61a of the Fiscal Penal Code. Under this provision, anyone who, contrary to their obligation, fails to submit books to the competent tax authority or submits unreliable books is subject to a fine of up to 240 daily rates. In a case of lesser significance, the act constitutes a fiscal petty offence. This milder sanction also applies to anyone who submits books late or submits defective books.

What are unreliable books?

Unreliable books are books that do not reflect the actual state of affairs, for example with incorrect amounts or omitted events. Defective books are books kept in breach of the regulations, even if their content need not be false in an economic sense. In the context of JPK_KR_PD, the risk may therefore concern both material amount errors and serious formal or technical breaches.

3 situations with potential sanctions

In practice, the risk of sanctions may arise in three situations.

1. When JPK_CIT was not successfully submitted at all, for example because the MF system rejected the file and the taxpayer did not resubmit it before the deadline.
2. When the file was successfully submitted but is unreliable, because it does not correspond to the actual state of the books.
3. When the file is defective, i.e. it breaches formal or technical requirements.

Not every technical or formal error will automatically lead to liability, but every material error requires assessment under Art. 61a of the Fiscal Penal Code.

Voluntary disclosure in JPK CIT

Voluntary disclosure is a separate instrument under Art. 16 of the Fiscal Penal Code, not an automatic effect of the correction itself. It requires notifying the authority of the commission of a prohibited act, disclosing the material circumstances of the act and, if the act involved a depletion of a public-law receivable, paying the amount due. The notification can be filed electronically, among others via ePUAP or the e-Tax Office (e-Urząd Skarbowy). However, voluntary disclosure is ineffective if the authority already had clearly documented knowledge of the act or had begun an activity aimed at uncovering it, unless that activity did not provide grounds for initiating proceedings concerning the act.

A reasonable approach to the first reporting year is therefore as follows: the correction itself should be treated as a way to restore correct reporting and reduce risk, but in the case of materially significant amount errors, a late original submission, a rejected file sent after the deadline, or a file that may be considered defective or unreliable, the need to file a voluntary disclosure must be assessed separately.

Consequences of not submitting a correction

Leaving in the Ministry of Finance system a file whose error the taxpayer knows or should know about may increase evidential, analytical and fiscal penal risk. It does not mean an automatic audit, but it may worsen the taxpayer’s position if the authority later compares JPK_CIT with the books, the CIT-8 or other data.

The evidential consequence should be assessed in light of Art. 193 of the Tax Ordinance Act. Tax books kept reliably and without defects constitute evidence of what they show. The authority does not accept unreliable or defective books as such evidence, unless the defects are not material to the case. JPK_CIT is an electronic representation of the books submitted to the authority, so a material inconsistency between the file and the books, or an incomplete reflection of the books, may trigger a dispute not only about the file itself, but also about the evidential value of the data used for the CIT settlement.

The analytical consequence is that an uncorrected file may remain inconsistent with the CIT-8 return, the financial statements, JPK_VAT files, transfer pricing documentation or other resources of the tax administration. This does not mean automatic initiation of an audit, but it increases the likelihood of a request for explanations or verification activities, in which the authority checks the formal correctness of documents and the consistency of the data presented.

The fiscal penal consequence may arise when the error is material and the taxpayer takes no action despite having identified it. Awareness of the error alone does not determine liability, but the longer the taxpayer leaves a known irregularity unaddressed, the harder it is to demonstrate that the breach was incidental, unintentional or immaterial.

Finally, there is a cascading consequence: if the error in JPK_CIT results from an error in the tax settlement itself, correcting the JPK file alone without correcting the CIT-8 does not remove the tax arrears or the obligation to pay interest. Therefore, once an error is detected, it must be determined not only whether JPK_CIT needs to be corrected, but also whether a parallel correction of the return, payment of arrears or filing of a voluntary disclosure is needed.

How does the ALTOOL JPK CIT application make it easier to manage corrections and verify data?

With the first JPK_CIT, the biggest risk is rarely the click on “send” itself. What matters most is establishing beforehand whether the accounting data is complete, whether the chart of accounts has correct tax tags, whether partial files cover the entire reporting period without gaps or duplicates, and whether the data in JPK_KR_PD is consistent with the CIT-8 and the books. ALTOOL JPK CIT supports precisely this stage of the process.

The tool helps at three stages: when verifying data before submission, when identifying inconsistencies after submission, and when preparing an orderly correction path once an error has occurred. It makes it possible to compare the original file with the correction, generate a report of differences and gather the documentation needed in case of questions from the authority. As a result, the decision to correct has a documented internal justification, rather than being an ad hoc action taken after a problem is detected.

A JPK_CIT correction should not be a hasty reaction, but part of a controlled tax process. In such a process, the quality of source data is checked before an error becomes a topic of discussion with the tax office.

FAQ: frequently asked questions about JPK CIT corrections

Deadline for a JPK CIT correction: by when must it be submitted?

A correction can be submitted after the deadline for the original JPK_CIT submission. There is currently no separate statutory end date for a voluntary JPK_KR_PD correction, but it should not be delayed. The sooner the taxpayer corrects a known error, the easier it is to show that it acted proactively and limited the risk of unreliable or defective reporting. A JPK_CIT correction must also be distinguished from voluntary disclosure: voluntary disclosure may be ineffective if the authority already had clearly documented knowledge of the act or had begun activities aimed at uncovering it.

Can a JPK CIT correction be submitted more than once?

Yes. Ministry of Finance explanations indicate that a correction may relate to the original file or to a previously submitted correction. In practice, this means that further corrections of the same period are possible if additional errors come to light after an earlier correction. Each subsequent correction should cover the full scope of data for the corrected period, not only the difference compared to the previous version.

Must a JPK CIT correction be signed by the same person who signed the original file? How can a correction be signed?

There is no such requirement. What matters is that the correction is signed by a person authorised at the time of submission. JPK_PD can be signed with a Trusted Profile (Profil Zaufany), a qualified electronic signature or, where the taxpayer is an individual, a signature based on authorisation data. From 16 June 2026, the UPL-1 power of attorney to sign returns submitted by electronic means also covers authorisation to sign JPK_PD files. However, UPL-1 should not be referred to as a general power of attorney, because a general power of attorney under the Tax Ordinance Act is a separate instrument.

Does the tax office report errors in JPK CIT before initiating an audit?

There is no guaranteed, automatic warning. After submission, the processing status of the file can be checked and the official confirmation of receipt downloaded, but this primarily confirms technical acceptance of the file, not substantive acceptance of the data. The authority’s doubts may only come to light during verification activities, a request for explanations, a tax audit or a customs and tax audit.

How much time does the authority have to review a JPK CIT correction?

There is no single statutory deadline for the substantive review of a JPK_KR_PD correction. The submission status and the UPO relate to technical acceptance of the file. If the correction becomes part of verification activities, an audit or tax proceedings, the deadlines applicable to that procedure apply, not a separate deadline for the JPK correction itself.

Does a JPK CIT correction affect other proceedings, such as a VAT audit?

There is no automatic effect here. A JPK_CIT correction does not in itself trigger a JPK_VAT correction, nor does it initiate or conclude other proceedings. It may, however, be of analytical or evidential significance if it reveals inconsistencies between the books, revenue, costs, invoices, JPK_VAT or other data available to the authority. The impact on other proceedings always requires a separate assessment.

Must an error be reported if it has not come to light and nobody has noticed it?

If the taxpayer has itself identified an error in a successfully submitted JPK_KR_PD, it should not assume that the authority’s lack of reaction solves the problem. The starting point should be an assessment of whether the error concerns data required for the given year and whether it affects the reliability or defectiveness of the books submitted. If the error concerns formal or amount data in the submitted file, the appropriate response may be a JPK_KR_PD correction. If the information was not mandatory for the given year, for example because it fell within the transitional simplification for counterparty data or the KSeF number, the basis for not submitting a correction should be documented.

Will the rules for JPK CIT corrections change?

Possibly. The draft act numbered UDER111 provides for standardising the rules for correcting electronically submitted tax books and placing these rules in the Tax Ordinance Act. However, this is a draft, not law in force. Until the new provisions are enacted and enter into force, the current regulations and the current Ministry of Finance explanations on JPK_KR_PD must be applied.

Sources

• Act of 15 February 1992 on corporate income tax, Art. 9(1c), (1d), (1e), (1g) and (1h) and Art. 27(1).
• Act of 29 August 1997, Tax Ordinance Act, Articles 80a and 80b, Art. 81, Art. 81b, Art. 193, Art. 193a.
• Act of 10 September 1999, Fiscal Penal Code, Art. 16, Art. 61a.
• Regulation of the Minister of Finance of 16 August 2024 on additional data to be added to accounting books subject to submission under the Corporate Income Tax Act, Journal of Laws 2024, item 1314.
• Regulation of the Minister of Finance and Economy of 15 December 2025 amending the regulation on additional data to be added to accounting books subject to submission under the Corporate Income Tax Act, Journal of Laws 2025, item 1828.
• Regulation of the Minister of Finance and Economy of 16 February 2026 on the extension of deadlines for submitting accounting books in respect of corporate income tax, Journal of Laws 2026, item 188.
• Act of 15 May 2026 amending the Personal Income Tax Act, the Corporate Income Tax Act and the Act on flat-rate income tax on certain revenue earned by individuals, Journal of Laws 2026, item 779.
• Draft act amending the Tax Ordinance Act and certain other acts, draft no. UDER111, List of Legislative and Programme Work of the Council of Ministers.
• Ministry of Finance, “Questions and answers on JPK_PD (JPK_KR_PD and JPK_ST_KR)”, podatki.gov.pl.
• Ministry of Finance, “JPK_PD: basic information, preparation and submission, signing JPK_PD”, podatki.gov.pl.
• Ministry of Finance, “Information brochure on the JPK_KR_PD(1) structure”, podatki.gov.pl.

Article updated: September 2026.