Errors discovered too late
Find data-quality issues before a file reaches the filing stage.
JPK compliance for Odoo · SAF-T
Validate, reconcile, review, and export Polish JPK files directly from your Odoo data. Catch discrepancies before filing, document every decision, and keep a complete audit trail.
For Odoo 17–20 · Community & Enterprise
The problem
A technically generated JPK file can still contain discrepancies, missing records, or unresolved accounting differences.
Find data-quality issues before a file reaches the filing stage.
Compare reported fixed-asset values, depreciation, and stock amounts with the general ledger.
Track reviewers, excluded records, corrections, and export activity in one documented workflow.
How it works
Create a report using company, period, warehouse, asset, and stock-movement data from Odoo.
Run documented validation rules, identify errors, and navigate to affected records.
Compare JPK amounts with general-ledger balances and document discrepancies.
Require reviewer confirmations, enforce separation of duties, and document excluded records.
Generate XML from a frozen snapshot, validate against the bundled official XSD schemas, and record the file hash and export history.
See it in Odoo
Real Odoo 20 screenshots on demo data (fictitious companies). The interface is also available in English.
Compliance dashboard
Reports for every company on one kanban – with blocking errors, warnings, workflow stage and internal deadline.
Features
01
66 rules, each linked to a registered source – the official XSD schema or the Ministry of Finance brochure – with its verification date. Every finding links to the affected record and suggests a fix. Errors block the export; warnings can be accepted with a justification.
02
Opening value, accumulated depreciation and period depreciation are compared with accounts 010/020, 071/072 and 401, and stock movements with inventory accounts. Every difference must be explained before export.
03
The preparer cannot approve their own report. The reviewer confirms four checkpoints, and excluded records – assets retired before the period, returns, scrapping – stay visible with their reason. Nothing disappears silently.
04
The file is built from a frozen data snapshot, checked offline against the official XSD schema and sealed with a SHA-256 hash. Exports are versioned, downloads are logged, and you attach the UPO after filing.
05
Run reports for many client companies on one dashboard. Company-level access rules, User / Reviewer / Manager roles, and internal deadlines with reminders.
06
Interface labels, rule explanations and suggested fixes are available in both languages – for accounting teams in Poland and international implementation partners.
JPK structures
JPK_ST_KR(1)
JPK ST KR – fixed-asset and intangibles register, depreciation, and accounting reconciliation. Filed together with JPK_KR_PD.
JPK_MAG(1)
JPK MAG – warehouse movement reporting for supported PZ, WZ, RW and MM documents – one file per warehouse.
JPK_MAG(2)
from 1 Jan 2027The newer warehouse structure: additional document types, the records method, and the INW stock-count section built from recorded counts.
The add-on has no official certification and does not guarantee acceptance of a file by the tax authority. Whether a structure applies to a company is decided and recorded by the user.
Technology
Python · Odoo ORM · PostgreSQL · XML / XSD
Compatibility
JPK_ST_KR tax data is kept on the add-on's tax cards – this works on Community too. If Odoo Assets (Enterprise) or OCA account_asset_management is installed, tax cards can be created from the asset register and book values are read automatically. The add-on only reads data – it never changes accounting or stock records.
Odoo
17
Odoo
18
Odoo
19
Odoo
20
Edition
Community
Edition
Enterprise
Simple pricing
JPK Compliance for Odoo
€200one-time on Odoo Apps
A focused JPK compliance workflow for Polish businesses and accounting firms.
Review compatibility and installation requirements before purchasing.
Odoo 17, 18, 19 and 20. Each version has its own release of the add-on on Odoo Apps – choose the one that matches your installation.
Yes. All features work on Community, where JPK_ST_KR data is kept on the add-on's tax cards. If Odoo Assets (Enterprise) or OCA account_asset_management is installed, book values are read from the asset register.
JPK_ST_KR is the fixed-asset and intangibles register, filed together with JPK_KR_PD. JPK_MAG covers warehouse movements and is provided on request of the tax authority – one file per warehouse, as JPK_MAG(1) or as JPK_MAG(2) from 1 January 2027.
The add-on runs 66 rules, each linked to an official source. Errors block the export and link to the record that needs fixing. Warnings can be accepted with a justification. The finished XML is also checked against the official XSD schema.
Yes. Opening value, accumulated depreciation and period depreciation are compared with accounts 010/020, 071/072 and 401, and stock movements with inventory accounts. Every difference must be explained before export.
Yes. One dashboard for many client companies (Odoo multi-company), company-level access rules, User / Reviewer / Manager roles and internal deadlines with reminders.
No. The add-on prepares and checks the file but does not send it. “Validated locally” never means submitted – you file through the official channel, and the report becomes “Submitted” once the UPO is attached.
Every export is a new version linked to a frozen data snapshot, its validation result and a SHA-256 hash. Downloads are logged, and earlier versions remain available according to the retention policy.
Bring preparation, validation, reconciliation, review, and export into one traceable workflow inside Odoo.