19 November 2026
JPK CIT in SAP, Oracle and Microsoft Dynamics: how to prepare your ERP system?
Posts
For an ERP system to prepare JPK CIT, it must supply complete data from the books and the fixed asset register, and the accounts must be assigned tags. How to achieve this depends on the system, its version and whether the company can change the chart of accounts: sometimes an update from the provider is enough, and sometimes it is better to transfer the data to an external tool. In this article, we show what to look out for in SAP, Oracle and Microsoft Dynamics.
- The ERP system must supply data for two structures: JPK_KR_PD (books of account) and JPK_ST_KR (register of fixed assets and intangible assets).
- Tags do not have to be entered directly in the ERP system. They can be assigned in an external tool that retrieves data from the books and generates the file.
- A group chart of accounts is usually the biggest obstacle to assigning tax tags.
- Regardless of the route chosen, the taxpayer, not the system provider, is responsible for the correctness of the data.
- Microsoft no longer issues updates for Dynamics AX 2009 and 2012, so the file has to be prepared by extending the system with a partner or in an external tool.
What does JPK CIT require of an ERP system?
The ERP system must supply data for two structures: JPK_KR_PD (books of account) and JPK_ST_KR (register of fixed assets and intangible assets). Some of the data is in every accounting system, but some has to be supplemented, e.g. account tags and tax data on fixed assets. Tags do not have to be entered directly in the ERP system. They can be assigned in an external tool that retrieves data from the books and generates the file. The exception concerns taxpayers that prepare financial statements under IFRS/IAS. Until 1 January 2028, they do not have to supplement their books with account tags, although they still file the JPK_KR_PD file.
| Structure | What data | Where it usually is in the ERP |
|---|---|---|
| JPK_KR_PD | counterparty data, including the NIP | counterparty records, sales and purchasing modules |
| JPK_KR_PD | KSeF numbers of sales invoices issued by the company, if they have been assigned | sales module, KSeF integration |
| JPK_KR_PD | trial balance with account tags | general ledger and chart of accounts; tags can be assigned in the ERP or in an external tool |
| JPK_KR_PD | journal with accounting entries | general ledger |
| JPK_KR_PD | the RPD part, i.e. the differences between the accounting result and the tax result | accounts with tax tags and the tax calculation; some differences do not result from the books at all |
| JPK_ST_KR | initial value for tax and accounting purposes, depreciation rates and methods | fixed asset module |
For fixed assets, the system must distinguish between the tax and accounting treatment. The Ministry of Finance explains that JPK_ST_KR shows, among other things, the basic rate from the list of depreciation rates and, if different, the rate set by the taxpayer. The file also has two separate fields for the initial value: the tax value, determined under the income tax regulations, and the accounting value, determined under the Accounting Act. These values may differ. If the fixed asset module keeps only one value, the tax data must be supplemented.
We describe assigning tags to accounts in the article on mapping the chart of accounts to JPK CIT.
Why does a group chart of accounts make it harder to prepare JPK CIT?
Companies that work on SAP, Oracle or Dynamics often have a chart of accounts imposed by the group. The local finance department cannot then add accounts or analytical accounts for JPK CIT purposes. This is usually the biggest obstacle to assigning tax tags.
Tags are assigned to accounts. If items of a different tax nature, e.g. tax-deductible and non-deductible costs, are recorded on one group account, a single tag will not reflect its content. The typical solution is to create separate accounts or analytical accounts. A group chart of accounts often does not allow this, because every change requires the group’s consent.
However, the chart of accounts in the ERP does not have to be rebuilt. Tags can be assigned outside the system, in a tool that retrieves data from the books. If the existing accounting dimensions, e.g. the cost centre (MPK) or project, make it possible to distinguish items on one account, an extended, virtual chart of accounts can be built on their basis. The group’s chart of accounts then remains unchanged. We describe an example of such a project in the section on older and unsupported systems.
What are the ways of preparing an ERP system for JPK CIT?
Companies most often prepare their ERP for JPK CIT in one of three ways: through the system provider’s solution, through an implementation partner’s add-on or through an independent tool to which the data from the system is transferred. The choice depends mainly on the system version, the number of data sources and the time left until the submission deadline.
| Method | When it works | What to watch out for |
|---|---|---|
| ERP provider’s solution | a current, supported system version with Polish localisation | dependence on the provider’s update schedule; tags still have to be assigned |
| Implementation partner’s add-on | a supported system, but without a ready-made function or heavily customised | implementation cost and time; maintaining the add-on when structures change |
| Independent tool | an older system, several systems, a closed chart of accounts, little time | quality of the data export from the ERP; a clear division of responsibilities |
Regardless of the route chosen, the taxpayer, not the system provider, is responsible for the correctness of the data. A tool will generate the file from what is in the books, but it will not decide which tag matches the content of an account.
Example: a group has three companies. Two work on the current version of Dynamics 365 Finance, and the third on Dynamics AX 2012, from which it is to move to a new system in a year. For the first two companies, the provider’s function is the natural choice. For the third, extending the system just before the migration does not pay off, so it is better to transfer the data from AX to an external tool. The mapping should then be based on common rules for the whole group, so that tags are assigned in the same way in all companies.
How to prepare an SAP system for JPK CIT?
In SAP, first check which system version and which Polish localisation the company has, and whether the provider or partner confirms support for JPK_KR_PD and JPK_ST_KR. Only then is it worth planning the mapping and testing.
What to check in SAP ECC and SAP S/4HANA?
SAP ECC 6.0 is part of SAP Business Suite 7. SAP has announced mainstream maintenance for this line until the end of 2027, and optional extended maintenance until the end of 2030. For companies planning to move to SAP S/4HANA, this matters when choosing a solution for JPK CIT. Extending the old system just before the migration may not pay off.
Before deciding, establish with the provider or partner:
- whether your version and localisation support the current versions of the JPK_KR_PD and JPK_ST_KR structures,
- how tags are assigned to accounts in the system,
- whether the fixed asset module keeps tax and accounting values separately,
- how the system takes into account structure changes published by the Ministry of Finance.
There are also SAP add-ons on the market prepared by implementation partners. Before choosing, it is worth comparing them with an independent tool in terms of implementation cost and time.
What challenges arise most often in SAP?
Large SAP installations often handle several companies in one system. The JPK CIT obligation applies to each taxpayer, so the data must be separated for each company. This requires entries to be correctly assigned to companies and consistent counterparty records.
The second challenge is fixed assets, for which tax values are not always kept in the fixed asset module. Parallel treatments, e.g. under the Accounting Act and under group standards, are usually not a problem. The companies then simply keep two separate ledgers, so it is enough to indicate from which ledger the system should retrieve data for JPK_KR_PD. A bigger challenge is the group chart of accounts, which we describe above.
How to prepare an Oracle system for JPK CIT?
In Oracle systems, the principle is the same: first establish whether your solution and its Polish localisation support JPK_KR_PD and JPK_ST_KR. Oracle offers several different financial systems, including Oracle E-Business Suite, Oracle Fusion Cloud ERP and NetSuite. Each of them has a different update model and different extension options.
For Oracle Fusion Cloud Financials, the manufacturer describes in its documentation the generation of an accounting file in the JPK_CIT format for transactions from 2025. It also describes the part concerning the fixed asset register, based on accounting and tax asset books. For other Oracle systems, support for JPK CIT must be confirmed with the provider or partner.
In practice, check three things with the provider or partner:
- whether the regulatory updates for Poland cover the JPK CIT structures,
- how to export the full journal together with the analytical dimensions,
- where the tax data on fixed assets is stored.
If the answer to any of these questions is uncertain, it is worth preparing a test export of the data to an external tool straight away. This makes it possible to check the completeness of the data without waiting for the provider’s decisions.
How to prepare Microsoft Dynamics for JPK CIT?
In the Microsoft Dynamics family, the situation depends on the product. Dynamics AX 2009 and 2012 no longer receive updates, Dynamics 365 Finance has a JPK_KR_PD reporting function described by Microsoft, and Business Central operates in Poland on partners’ localisations.
Can JPK CIT be reported from Dynamics AX 2009 and AX 2012?
Data from AX can be used to prepare the file, but not thanks to an update from Microsoft. Extended support for Dynamics AX 2009 SP1, AX 2012 and AX 2012 R2 ended on 12 April 2022, and for AX 2012 R3 on 10 January 2023. Even during the extended support period, Microsoft issued only security fixes, without regulatory updates.
A company with AX therefore has two routes in practice. The first is extending the system through a partner that still maintains the installation. The second is exporting the data from AX to an external tool that will assign the tags and generate the file. If a migration to a newer system is planned, the second route is usually quicker and cheaper.
What does Dynamics 365 Finance offer?
Microsoft publishes in the Dynamics 365 Finance documentation a separate description of preparing the system and generating the JPK_KR_PD file as part of the Polish localisation. The documentation was updated in 2026.
Before the first file, check whether your environment has the current version of the functions and reporting formats for Poland. Simply running the report will not replace mapping. A partner can configure the tags, but the company is responsible for whether they match the content of the accounts.
What does it look like in Business Central?
Microsoft does not provide its own localisation of Business Central for Poland. The Polish localisation consists of partners’ applications, built on the international version of the system and available in Microsoft Marketplace. Each partner may approach JPK CIT differently.
If you use Business Central, ask your partner whether its localisation supports JPK_KR_PD and JPK_ST_KR and how tags are assigned in it. If the company has several companies or additional systems, also check how the localisation combines data from different sources.
What to do if the system is old or unsupported?
If the system does not receive updates or does not allow the chart of accounts to be changed, the safest option is to move the preparation of JPK CIT outside the source system. The data from the ERP is then fed into a tool that builds a tag layer and generates the file.
This is how we worked with a client whose system had a completely closed chart of accounts. We used the existing accounting dimensions to build an extended, virtual chart of accounts and assign tags. In another project, some of the data was kept outside the ERP, and we imported it from external files. In both cases, the client did not have to rebuild its system. You can find a description in the case study ALTOOL JPK CIT – Support for reporting despite system limitations.
If the data for JPK CIT comes from several systems, remember that, according to the Ministry of Finance’s explanations, it must be combined into one complete JPK_KR_PD file for the whole year. The file can be prepared in parts for different periods, but together they must reflect the books without gaps or duplicates. We describe how to do this in the article on JPK CIT with several accounting systems.
What to check before generating a test file?
Before the first test file, go through a short checklist. It helps catch ERP problems before they surface in the final weeks before the deadline.
- Do you know which version of the system and localisation generates the data, and who is responsible for keeping it up to date?
- Can the data of each company be separated?
- Have all accounts with turnover or balances been assigned tags?
- Does the group allow the chart of accounts to be changed, and if not, where will you assign the tags?
- Does the fixed asset module keep tax and accounting values and depreciation rates?
- Does the export include the full journal together with the counterparty records?
- Do you know where the data for the RPD part comes from?
- Does the test file pass validation for compliance with the Ministry of Finance schema?
FAQ
Does SAP generate JPK_KR_PD as standard?+
What to do if the group does not allow the chart of accounts to be changed?+
Can JPK CIT be submitted from Dynamics AX 2012?+
How long does it take to prepare an ERP system for JPK CIT?+
What if the data is in several systems?+
What ERP data is needed for JPK_ST_KR?+
How ALTO can help
We help companies prepare JPK CIT regardless of their ERP system, including when the system is older or does not allow the chart of accounts to be changed. We analyse data from the ERP, map accounts, assign tags and test files. We use our ALTOOL JPK CIT application, which retrieves data from financial systems and generates files without rebuilding the ERP.
- Penalties for JPK CIT errors – KKS liability of the management board and accountants
- How to prepare data for JPK CIT? Data Cleansing for companies before the first reporting cycle
- JPK CIT audit: how does the tax authority select companies for review in 2026?
- JPK CIT correction: how to fix errors from the first reporting cycle? It is not too late
- JPK_CIT in 2026: deadlines, JPK_KR_PD structure and new obligations (April 2026)
Sources
- Ministry of Finance, JPK_PD questions and answers (Pytania i odpowiedzi JPK_PD), updated 17 July 2026: https://www.podatki.gov.pl/podatki-firmowe/jednolity-plik-kontrolny/jpk_pd/pytania-i-odpowiedzi-jpk_pd
- Ministry of Finance, JPK structures in income taxes (Struktury JPK w podatkach dochodowych): https://www.gov.pl/web/kas/struktury-jpk-w-podatkach-dochodowych
- Corporate Income Tax Act of 15 February 1992 (Ustawa z dnia 15 lutego 1992 r. o podatku dochodowym od osób prawnych), Article 9(1c)
- Regulation of the Minister of Finance and Economy of 15 December 2025 amending the regulation on additional data (Rozporządzenie Ministra Finansów i Gospodarki z dnia 15 grudnia 2025 r. zmieniające rozporządzenie w sprawie dodatkowych danych), Journal of Laws 2025, item 1828
- SAP, SAP S/4HANA Maintenance 2040: Clarity and Choice on SAP Business Suite 7, 4 February 2020: https://news.sap.com/2020/02/sap-s4hana-maintenance-2040-clarity-choice-sap-business-suite-7/
- Oracle, JPK Accounting File Format Update for Poland (Oracle Fusion Cloud Financials 25D): https://docs.oracle.com/en/cloud/saas/financials/25d/faugf/jpk-accounting-file-format-update-for-poland.html
- Oracle, JPK Audit File for Poland Asset Register (Oracle Fusion Cloud Financials 26C): https://docs.oracle.com/en/cloud/saas/financials/26c/faugf/jpk-audit-file-for-poland-asset-register.html
- Microsoft, End of mainstream support for Dynamics AX 2009, AX 2012, AX 2012 R2 and AX 2012 R3: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/mainstream-support-ax-2009-2012
- Microsoft, SAF Accounting Books Income Tax – JPK_KR_PD (Dynamics 365 Finance): https://learn.microsoft.com/en-us/dynamics365/finance/localizations/poland/emea-pol-standard-audit-file-saf-pd
- Microsoft, Country/Regional Availability and Supported Languages (Business Central): https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/compliance/apptest-countries-and-translations
Check how we can help your company!
Contact19 November 2026
You may be interested:
JPK CIT and the year-end closing: what to check before closing the books?
This article was translated from Polish by artificial intelligence (AI) and has not been reviewed by a human. The original Polish ...
Read more
When to start implementing JPK CIT? 5 signs that the time has come
This article was translated from Polish by artificial intelligence (AI) and has not been reviewed by a human. The original Polish ...
Read more