A build-to-order Odoo integration that sends and receives structured invoices through Poland's mandatory KSeF national e-invoice system directly from Odoo. ECOSIRE builds it to your confirmed scope, installs it, and supports it after go-live. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $599.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo integration that sends and receives structured invoices through Poland's mandatory KSeF national e-invoice system directly from Odoo. ECOSIRE builds it to your confirmed scope, installs it, and supports it after go-live.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
Generates FA(2)/FA(3) structured invoice XML validated against the Ministry of Finance schema before submission
Transmits invoices to the KSeF test and production API and persists the returned KSeF number (numer KSeF) on the account.move
Stores the official UPO (Urzedowe Poswiadczenie Odbioru) confirmation per invoice as a retrievable attachment
Authenticates via KSeF token, qualified signature, or trusted profile (ZAW-FA) — chosen at scope time
Interactive and batch session handling with automatic session open/close against the KSeF gateway
Fetches inbound invoices addressed to your NIP and creates draft vendor bills (account.move) for review
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 2-4 weeks from confirmed scope. Pricing starts from $599 (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.
Runs accounting on Odoo and needs a self-hosted KSeF path before the 2026 mandatory rollout, without handing invoice data to a third-party partner integration. Wants issuing, UPO storage, and rejection handling to live inside Odoo.
Manages books for several NIP-registered entities and needs multi-company submission, per-client credentials, and reliable inbound-invoice fetching to create draft vendor bills at scale.
Owns the Odoo instance and wants a maintainable module with clear security rules, a sandbox/production switch, and XML-RPC/JSON-RPC hooks — not an opaque black box — so the team can support and extend it.
Operates a multi-entity group where only the Polish company needs KSeF, and wants a scoped build that adds structured e-invoicing for that entity while leaving the rest of the group's invoicing untouched.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Poland KSeF National E-Invoicing 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Poland KSeF National E-Invoicing,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Fit to Polish KSeF mandate | Purpose-built for FA(2)/FA(3), UPO, and the national API | Possible but you specify every schema detail yourself | Generic coverage, may lag schema or edition changes | |
| Authentication options | Token, qualified signature, or ZAW-FA — built to your method | Whatever your developer scopes and maintains | Often one fixed method, take it or leave it | |
| UPO and KSeF number storage | Persisted per invoice, retrievable and reportable | Must be designed and tested from scratch | Usually stored, format and access vary | |
| Inbound vendor bills | Fetches inbound invoices into draft vendor bills | Extra build effort, frequently skipped | Sometimes outbound-only | |
| Correction and advance invoices | Faktura korygujaca and zaliczkowa flows included in scope | Additional analysis and build per case | Coverage varies by product | |
| Ownership and maintainability | Full source and git repo handover, documented | You own it but carry all the design risk | Often closed/proprietary, vendor-locked | |
| Multi-company / multi-NIP | Per-company credentials and record-rule isolation | Depends on how carefully it is built | May assume single entity | |
| Delivery and support | Scoped build, UAT on staging, rollback plan, support window | Depends on your contractor's process | Install-and-hope, generic support queue |
No. This is a build-to-order productized service. ECOSIRE builds the module to your confirmed scope — your KSeF authentication method, VAT/GTU mapping, and company structure — then installs and supports it. It is not an existing apps.odoo.com download.
Typical delivery is 2-4 weeks from confirmed scope. The clock starts once we've completed the scoping call, agreed the authentication method and mappings, and you've approved the written quotation. Larger multi-company or heavy-customization builds can extend that, which we flag during scoping.
Pricing starts from $599 as an indicative single-company base scope. After a short scoping call we issue a fixed written quotation for your exact requirements. Drivers such as additional Polish entities, deeper localization logic, inbound-invoice automation depth, and integrations adjust the final quote. You approve the fixed price before any development begins.
We build against Odoo 17.0, 18.0, or 19.0, on Community or Enterprise. You tell us your target line and edition at scope time and we deliver source code compatible with it, tested on a matching staging instance.
We implement your chosen method: KSeF token, qualified signature, or trusted profile (ZAW-FA). We pick one primary method during scoping based on how your team operates, and build interactive and batch session handling around it.
Every engagement includes a post-go-live support window for defect fixes and schema-conformance issues. Because the KSeF schema and rules evolve, we can quote a separate maintenance arrangement to keep the module aligned with future Ministry of Finance schema updates beyond the initial window.
Yes. It sends structured FA(2)/FA(3) invoices and records the KSeF number and UPO, and it fetches inbound invoices addressed to your company from KSeF, creating draft vendor bills for your team to review and post.
A build-to-order Odoo integration that sends and receives structured invoices through Poland's mandatory KSeF national e-invoice system directly from Odoo. ECOSIRE builds it to your confirmed scope, installs it, and supports it after go-live.