Every Polish VAT-registered business lives on a monthly deadline: the JPK_V7M (or quarterly JPK_V7K) file that merges the VAT declaration and the full records ledger into one XML document the tax office parses automatically. On top of that, the Krajowa Administracja Skarbowa can demand any of the other SAF-T structures — JPK_FA for sales invoices, JPK_KR for the accounting books, JPK_MAG for warehouse movements, JPK_WB for bank statements — often with only a few days' notice. Odoo's stock l10n_pl chart of accounts and base_vat validation give you the ledger, but out of the box it does not assemble, mark, and XSD-validate these government files. Teams end up exporting to spreadsheets, hand-tagging GTU codes, and hoping the gateway accepts the upload — which is exactly where a late correction or a rejected schema turns into a real penalty.

ECOSIRE builds a suite that turns Odoo into the file factory for the whole JPK/SAF-T family. On the account.move and account.move.line models we add computed fields for the GTU_01–GTU_13 goods and service group codes, the procedure markers (SW, EE, TP, TT_WNT, MPP, and the rest), and the document-type markers (RO, WEW, FP), driven by @api.depends logic on product category, partner, and journal so a bookkeeper tags once and lets the ORM propagate. A dedicated jpk.declaration model groups a period's moves into the exact JPK_V7 sections, exposes a VAT register preview grouped the way the file is structured, and renders the XML through a QWeb template mapped field-by-field to the current Ministry of Finance schema. Before anything leaves Odoo the output is validated against the official MF XSD, so a malformed file is caught on your screen, not at the gateway.

The on-demand structures share the same engine. JPK_FA reads posted customer invoices, JPK_KR walks the journal entries and account balances, JPK_MAG pulls stock.move warehouse data, and JPK_WB maps account.bank.statement lines — each generated for an arbitrary date range from a single action so you can answer a tax-office request in minutes. Split-payment (MPP) obligations and the white-list account flag feed the file automatically from the invoice and partner records. Corrections are first-class: a correction run carries the right cel złożenia purpose code, and the XML is digital-signature-ready with UPO (Urzędowe Poświadczenie Odbioru) reference tracking so every confirmed submission is auditable. Multi-company support and period-lock integration keep a closed month from being quietly re-opened and re-edited after the file has gone out. Everything is exposed over Odoo's XML-RPC/JSON-RPC API and gated by ir.model.access.csv plus record rules so only the accounting team touches declarations.

Because this is built to order, nothing is downloaded and switched on today: after you request a quotation we run a short scoping call, confirm your Odoo edition (Community or Enterprise) and version (17.0, 18.0 or 19.0), agree the exact JPK structures and marker logic your business needs, and then build, install and support it. Typical delivery is one working week from confirmed scope, with UAT on a staging database before anything touches production. Pricing starts from $999 (indicative, single-company base scope); additional company codes, deeper localization depth (extra marker rules, custom invoice types, warehouse edge cases), and data-migration volume from a legacy JPK process increase the quoted scope.