What is complicating JPK CIT in your company today?
An obligation that arrives in stages
A tag for every account
Tax status changes the data scope
Errors caught in a rush
Export to an external tool
Requirements that keep shifting

JPK CIT straight from the general ledger
A file straight from the general ledger
ANEGIS JPK CIT generates the JPK_KR_PD and JPK_ST_KR files directly from the standard Dynamics 365 general-ledger tables. No export to a separate program and no manual data entry.
Account tags in the Dynamics 365 interface
The module adds an interface to Dynamics 365 for assigning accounts the tags required by the regulation on the additional data scope. You do the mapping once, in the system where you post, and it's at hand whenever the chart of accounts changes.
Company parameters set once
Parameters such as Estonian CIT or the IFRS flag are defined once, at the module's configuration level. Every subsequent file takes them into account automatically, with no exceptions to remember.
A two-step process with verification
The data first goes to a preparation stage, where the accounting team reviews and corrects it in the Dynamics 365 interface. Only approved data moves on to generating the XML file.
Built into the system, not beside it
The solution runs as an integral part of Dynamics 365, not a separate app alongside it. JPK CIT stops being a separate project and becomes part of the period close.
Updated in step with Ministry of Finance guidance
The ANEGIS team updates the module in line with the current Ministry of Finance guidance, as with the February deadline change. A change in the rules reaches you as a module update, not a task for IT.
Are you already using Dynamics 365?
The value ANEGIS JPK CIT delivers
Readiness whatever the stage
The module handles the requirements of every stage of the obligation, from the largest taxpayers to companies entering in 2027. Whenever your deadline comes, compliance is ready ahead of it.
Tags where you post
You assign the tags in the same system where you keep the books. One working environment instead of juggling a mapping spreadsheet alongside the system.
A file that matches your tax situation
Estonian CIT, IFRS and the company's other parameters are part of the configuration, so the file matches your tax situation from the start. No manual corrections before each submission.
Verification before the tax office, not after
The accounting team reviews and corrects the data before the file reaches the tax office. An error costs a few minutes at the preparation stage, not a correction and explanations after submission.
One source for the data and the file
The accounting data and the JPK file come from the same system tables. What's in the books and what reaches the tax office are, by definition, the same numbers.
Compliance without monitoring the rules yourself
ANEGIS keeps up with the changes to schemas and deadlines, not your team. Accounting's time goes back to the close and analysis, not to reading regulations.
Automatic generation of JPK_KR_PD and JPK_ST_KR
The module generates the JPK_KR_PD and JPK_ST_KR files directly from the data in the standard Dynamics 365 general-ledger tables. You do not export data to a separate program or retype it by hand.

Account tags and company parameters in one place
An interface in Dynamics 365 lets you assign tags to ledger accounts as required by the regulation on the additional scope of data. At the company level, you define extra parameters, such as Estonian CIT or the IFRS tag, which affect the content of the generated file.

A two-step process: data preparation, then file generation
First the data goes to a preparation stage, where trained users verify it and, if needed, correct it in the Dynamics 365 interface. Only approved data then moves on to the actual generation of the JPK file.

Built into Dynamics 365, compliant with Ministry of Finance guidance
The solution works as an integral part of Dynamics 365, not as a separate application alongside the system. This lets you avoid costly changes made on your own and shortens the implementation time. The module's design is based on the current Ministry of Finance guidance on the structures of the standard audit files.

Products that help us drive change
We don't just deploy standalone applications; we implement a cohesive suite of Microsoft solutions—from Dynamics 365 and the Power Platform to advanced analytics and AI—tailored to your specific goals. Everything runs on a unified data foundation, meaning information entered once works across your entire organization, while AI supports your processes exactly where the work happens.

A clear, structured path for change in your company
Switching systems doesn't have to mean chaos. We guide you through four simple steps, ensuring that at every stage, you know exactly what is happening, why it’s happening, and what comes next.
Needs analysis
We get to know your situation, processes, and goals. Together, we determine what needs to change and how we will measure the success of that change.
Choosing the right solutions
We recommend the scope, path, and variant, always starting with standard options. You make your decisions based on facts, not assumptions.
Roadmap
Schedule, budget, roles, and decision gates. Everyone knows who is responsible for what and when decisions are made.
Implementation and monitoring
We implement in stages, incorporating testing and risk management, and once live, we stabilize the system and transition to ongoing support.
Wondering whether this would work for you?
Let's see how Dynamics 365 can transform your business
We implement, develop, and maintain Microsoft systems: from finance and operations to data and AI. Let’s start with a free consultation about your current situation.


See other proprietary solutions
FAQs
How do JPK_KR_PD and JPK_ST_KR differ?
JPK_KR_PD covers accounting-ledger entries together with the data needed to settle income tax. JPK_ST_KR concerns the register of fixed assets and intangible assets. Both structures are submitted under the same reporting obligation, but they are separate XML files.
Who does the JPK CIT obligation apply to, and from when?
The obligation comes in stages. From 1 January 2025 it applies to CIT taxpayers with revenue above EUR 50 million and to tax capital groups. From 1 January 2026 it covers the remaining CIT taxpayers and PIT taxpayers filing JPK_V7 monthly. From 1 January 2027 it extends to the remaining taxpayers keeping accounting books.
Do you have to generate the JPK file in a separate tool?
No. ANEGIS JPK CIT is built into Dynamics 365 and uses the system's standard general-ledger tables. You do not export data to an external application or re-enter it by hand.
What does data verification look like before the file is sent?
The process has two steps. First the data goes to a preparation stage, where you can verify or correct it in the Dynamics 365 interface. Only approved data is then turned into a JPK file ready to send.
What happens when the Ministry of Finance changes requirements or deadlines?
The ANEGIS team updates the module in line with the current Ministry of Finance guidance. That was the case, for example, in February 2026, when a regulation of the Minister of Finance moved the first JPK_KR_PD filing deadline from the end of March to the end of July 2026.
Let's talk about your project
Let us know what you need: implementation, migration, system development, or a question you’re looking to have answered. We’ll get back to you with a concrete proposal for the next step - not a sales pitch.




























