Setting up Polish books in Odoo means hitting the wall of localization quickly. Odoo core ships a generic chart and a handful of tax templates, but it has no concept of the Zespol 0-8 plan kont structure Polish accountants expect, no rejestr sprzedazy / rejestr zakupow that map to how VAT is actually filed, no mechanizm podzielonej platnosci logic on payments, and no way to check a counterparty against the Ministry of Finance whitelist before you pay them. base_vat validates a NIP's format but tells you nothing about whether that taxpayer is an active VAT payer, nor whether the bank account you are about to pay is the one on record. Teams patch the gaps with spreadsheets and manual lookups — exactly the fragile foundation you do not want underneath KSeF and JPK layers later.

This is a made-to-order Odoo localization base that ECOSIRE builds for your specific company after a scoping call — not an existing download you install today. We deliver a proper Polish chart of accounts template modeled on the Zespol 0-8 account classes, a complete VAT tax set (23/8/5/0%, reverse charge, exempt, and NP/not-subject), and sales and purchase VAT registers driven off account.move and account.tax so registers reconcile to your ledger by construction rather than by hand. Technically it is a clean Odoo module: a __manifest__.py declaring dependencies on account, base_vat, and base_iban; account-template and tax-template data loaded through l10n-style chart templates; new register models built on models.Model with @api.depends computes rolling up tax amounts; QWeb PDF/XLSX reports for the periodic registers; and access controlled through ir.model.access.csv plus record rules so the registers respect Odoo's multi-company and journal-security boundaries.

The whitelist and split-payment logic is where the localization earns its keep. We wire a service against the MF wykaz podatnikow API to verify a NIP's active-VAT status and its registered microaccount / bank accounts, storing the check result and timestamp on the partner so your AP team has an audit trail before releasing a payment. Split payment is applied at the account.payment level — flagging in-scope invoices, computing the VAT portion routed to the dedicated VAT account, and reflecting the mechanizm podzielonej platnosci on the payment. We add NIP/REGON validation with GUS company lookup to auto-fill contact data, a nota korygujaca (corrective note) document type, fiscal positions for EU/OSS scenarios, and bank statement import mappings for common Polish formats (MT940 / Elixir). All of it is exposed to your other systems through Odoo's standard XML-RPC / JSON-RPC API, and it is built to run on Community or Enterprise across Odoo 17.0, 18.0, and 19.0 (Enterprise adds richer accounting reporting; the core localization behaves identically on Community).

Delivery is build-to-order. After a short scoping call we confirm the exact account structure, tax edge cases, and integrations you need, then build, test on a staging copy of your database, and hand over installable source plus a git repository. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional legal entities, deeper localization coverage (custom register layouts, extra document types), external integrations, and historical data migration volume increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.