Poland's transition to mandatory KSeF (Krajowy System e-Faktur) means that from the 2026 rollout, structured invoices must be issued and received through a single national platform — not as free-form PDFs. Standard Odoo account handles VAT invoicing well, but it has no concept of the FA(2)/FA(3) national schema, no path to authenticate against the KSeF API, no place to store the returned KSeF number (numer KSeF), and no way to persist the official UPO confirmation. Finance teams end up bridging that gap by hand — exporting, reformatting, and re-keying into a government portal — which is exactly the manual, error-prone process the mandate is meant to eliminate.

ECOSIRE builds a dedicated Odoo integration for your instance that closes this gap end to end. It extends account, account_edi, base_vat, and l10n_pl with new models (models.Model) that generate valid FA(2)/FA(3) invoice XML matched to the Ministry of Finance schema, then transmit it to the KSeF API and record the response against the originating account.move. Compute fields (@api.depends) derive the structured payload from the invoice lines, taxes, GTU codes, and procedure markers (procedury), while ir.model.access.csv entries and record rules keep the KSeF token, session data, and confirmations locked to the right users and companies. Authentication is built to your chosen method — KSeF token, qualified signature, or trusted profile (ZAW-FA) — with interactive and batch session handling that opens and closes sessions automatically.

Technically, the module manages the full lifecycle on the invoice. Outbound invoices are validated against the schema before submission; the returned KSeF number and the UPO (Urzedowe Poswiadczenie Odbioru) are persisted per invoice and exposed on dedicated fields and QWeb-rendered attachments. A status-polling routine (implemented as a scheduled automated action) checks acceptance or rejection asynchronously and surfaces any rejection reasons directly on the invoice chatter, so accountants never have to log into an external portal to find out why a document bounced. Inbound invoices addressed to your company are fetched from KSeF and turned into draft vendor bills for review. The build also covers correction invoices (faktura korygujaca) and advance invoices (zaliczkowa), an offline-mode QR (KOD) fallback with a human-readable visual PDF attached alongside the structured XML, a sandbox/production environment switch, and multi-company support so each Polish entity submits under its own credentials. Everything is exposed through the standard Odoo XML-RPC/JSON-RPC API for downstream automation, and the module is delivered targeting your Odoo 17.0, 18.0, or 19.0 line, Community or Enterprise.

Because this is build-to-order, delivery follows a clear path: a scoping call to confirm your KSeF authentication method, VAT and GTU mapping, correction/advance-invoice needs, and company structure; a fixed written quotation; development against that scope; UAT on a staging instance wired to the KSeF test environment; then production cutover with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional Polish entities, deeper localization work (extra GTU/procedure logic, custom correction workflows), inbound-invoice automation depth, and integrations with existing systems increase the quoted scope.