The Poland KSeF E-Invoicing Connector is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports for your specific configuration — it is not an off-the-shelf apps.odoo.com download and there is no instant download at checkout. After purchase, our Odoo engineers develop and deploy a native integration between your Odoo Accounting and Poland's Krajowy System e-Faktur (KSeF), the National e-Invoicing System that becomes mandatory for VAT-registered businesses in 2026.

At the core, the module extends account.move to generate compliant FA(2) structured XML directly from your posted customer invoices and credit notes, mapping Odoo partner data, tax lines, and payment terms into the FA(2) schema fields KSeF expects. Computed fields (built with @api.depends) derive KSeF-specific values — invoice hash, issue metadata, and gross/net breakdowns — while a dedicated ksef.document model tracks every submission's lifecycle: draft, sent, accepted, rejected, and the returned KSeF reference number.

Authentication is handled through the KSeF API: the module manages session initiation, token-based auth (interactive or authorization-token flow), and session refresh, storing credentials securely and never exposing secrets in the UI. Outbound submission pushes the signed FA(2) XML to KSeF and polls for the UPO (Urzędowe Poświadczenie Odbioru) — the official confirmation receipt — which is stored as an attachment against the invoice for your audit trail. Inbound retrieval periodically queries KSeF for invoices issued to your NIP, so purchase documents received via the system land in Odoo automatically.

Automation is wired through Odoo scheduled/automated actions so submission and retrieval run without manual clicks; QWeb reports render a KSeF-visualized human-readable copy of each structured invoice for your customers and internal review. Access is governed by ir.model.access.csv plus record rules so only your accounting team can send, view UPOs, or reprocess rejected documents. The connector is designed for Odoo 17, 18, and 19 (Community and Enterprise), and can also expose submission state over XML-RPC/JSON-RPC if you drive invoicing from an external system.

Because every deployment differs — chart of accounts, tax configuration, multi-company, NIP structure, and whether you are on Odoo.sh, on-premise, or ECOSIRE managed hosting — we scope the build to your environment during onboarding and hand over a documented, tested, production-ready module within a typical one working week lead time.