JPK CIT – the second pillar of accounting digitalisation
Amid the multitude of changes related to the implementation of KSeF, it is important not to lose sight of the broader context of digitalisation. Already today, upon request from tax authorities, businesses are required to submit various JPK structures, including accounting books, inventory records, invoices, and bank statements. This means that records must be kept in a manner that allows for quick and consistent data generation.
JPK CIT is another breakthrough stage in this process. This obligation covers two key files: those containing full accounting books and the fixed asset register. Thanks to their structured format, the tax administration gains the ability to conduct advanced data analysis, particularly in the following areas:
- links between invoices in KSeF and VAT returns with accounting books – through the KSeF identification number,
- relationships between the CIT return and the financial result – based on tax adjustments,
- links between the financial statements and the details of each transaction,
- transactions between business entities based on their tax ID number (NIP),
- depreciation of fixed assets and intangible assets.
Thus, the new obligations related to JPK CIT are not limited to submitting the tax amount or the tax result. It is about providing data from the accounting books in such a way that enables detailed analysis of tax declarations from multiple angles. As a result, tax authorities can compare full accounting data with the calculation of the tax result without initiating a tax audit.
Important
Such a broad reporting scope requires proper preparation, which is why the largest entities, those first included in the JPK CIT requirement, welcomed the extension of the submission deadline to the end of the 7th month after the end of the tax year. In most cases, this will therefore be 31 July 2026.
Preparing this obligation already in March, in parallel with the CIT‑8 return, financial statements, and other reports, would be a major organisational challenge for many companies. However, it is worth remembering that this solution is temporary and applies only to the first reporting period. In subsequent years, the JPK CIT obligation will also cover other taxpayers – most likely without any additional postponement.
What are XML files and why do they matter in JPK CIT?
The foundation of reporting under JPK CIT is XML files, a structured data format that enables unambiguous interpretation by IT systems. Unlike traditional documents (e.g., PDFs or Excel spreadsheets), XML files are not intended for human presentation but for automatic processing and analysis.
Each piece of information contained in an XML file is described using defined tags and schemas, ensuring consistency and comparability of data across different entities. In the context of JPK CIT, this means that accounting data must be not only substantively correct but also saved in accordance with a specific logical and technical structure.
What tools should be used to work with XML files?
JPK files, financial statements, and an increasing number of tax declarations are currently prepared in the form of structured XML files, which requires the use of specialised IT tools. They cannot be prepared using commonly available applications such as Excel or Word. Therefore, accounting systems must be adapted to generate the required files, especially if they were not originally designed for structured data exchange. An additional challenge is that XML files are not easily readable for non‑technical users, which means their implementation requires close cooperation between IT and finance teams. This challenge is particularly visible in foreign companies that need to adapt their ERP systems to Polish requirements.
Data consistency – a key element of digital reporting
It is becoming increasingly clear that digital reporting cannot be treated as a set of separate obligations. It requires attention at the stage of ongoing data entry, not only when preparing declarations at the end of the month or year. Tax data must be consistent with the accounting books and cannot be treated as separate files prepared for different purposes. They are, after all, the same information – just viewed from different perspectives. The same document appears in several places within the data system: in KSeF, in the accounting books, in JPK VAT and JPK CIT, and in the financial statements, so it must be presented consistently.
Of course, not every difference automatically indicates an error. In accounting and taxation, many discrepancies have legitimate reasons: different timing of recognition, different exchange rates, different valuation methods. The Accounting Act (UoR) is not identical to CIT regulations, and CIT rules differ from VAT regulations. Additionally, identical transactions may be reported differently by different taxpayers due to errors or varying interpretations of unclear tax laws. However, tax authorities now have access to advanced analytical tools that, based on large datasets, can detect statistically significant inconsistencies. Problems arise when a company is unable to monitor, explain, or correct discrepancies in a timely manner.
Another digital obligation, JPK CIT, means that companies must ensure proper organisational and technological preparation and change their approach to reporting. Above all, the better organised and more consistent the data, the lower the risk of irregularities being identified by the tax administration’s systems.
More about the challenges related to accounting digitalisation can be found in the article series “New digital obligations for businesses” on the Grant Thornton website: New digital obligations for businesses: KSeF, JPK CIT and emerging compliance challenges – Grant Thornton
Important
Companies therefore need to implement clear invoice verification procedures. Every received invoice must be reviewed and approved by an authorised employee before being posted in the accounts and processed for payment.
Hopefully, in the initial period of KSeF implementation, tax authorities will take a flexible and pragmatic approach to irregularities. The scale of the reform is significant, and both businesses and the tax administration are facing new operational challenges and increasing volumes of questions and uncertainties.
The implementation of KSeF demonstrates that digitalising accounting is not just about changing how invoices are issued. It represents a broader redesign of everyday tax and financial processes. A company’s readiness for KSeF therefore requires attention to numerous details—from correct and timely transaction posting, through robust document verification procedures, to a well‑defined system of user permissions and efficient internal information flow. It is the sum of these seemingly minor elements that determines whether an organisation can operate smoothly in the new environment.
More insights into the challenges of accounting digitalisation can be found in the “New Digital Obligations in the Company” article series on the Grant Thornton website.
- New digital obligations for businesses: KSeF, JPK CIT and emerging compliance challenges
- New digital obligations for businesses: The National e Invoicing System (KSeF)
- New digital obligations for businesses: JPK CIT
- New digital obligations for businesses: the biggest challenges related to digital accounting
JPK CIT – frequently asked questions
What is JPK CIT?
JPK CIT is a new reporting requirement that obliges companies to submit full accounting books and the fixed asset register in a structured form, enabling detailed tax data analysis by the authorities.
What tools are needed to prepare JPK CIT?
Specialised accounting and reporting systems capable of generating XML files. JPK CIT cannot be prepared in Excel spreadsheets or Word documents – dedicated tools meeting the technical requirements are necessary.
How should companies prepare for JPK CIT?
They should streamline accounting processes, ensure IT system compliance, maintain data consistency, train teams, and start adapting systems early to generate structured files.