示意预览Send & receive structured FA(2) invoices through Poland's KSeF,
with UPO receipts and reference tracking, ready for the 2026 mandate.
什么是 Poland KSeF E-Invoicing Connector？
Send & receive structured FA(2) invoices through Poland's KSeF, with UPO receipts and reference tracking, ready for the 2026 mandate. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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.
你得到什么
- Fully built, tested Odoo module (source code) packaged with __manifest__.py, models, views, security, QWeb reports, and data files, installed in your Odoo 17/18/19 instance
- Environment-specific configuration: KSeF credentials wiring, NIP/company setup, tax-to-FA(2) field mapping, and scheduled-action tuning
- KSeF sandbox/test-environment validation of at least one full outbound submission with UPO retrieval and one inbound retrieval before go-live
- Technical and user documentation covering setup, the send/receive workflow, rejection handling, and reference-number reconciliation
- A live training session (recorded) for your accounting team on issuing, monitoring, and reprocessing KSeF invoices in Odoo
- A defined post-go-live support and bug-fix window with an SLA for KSeF-related issues
- Handover of source access (your private repo or ECOSIRE-hosted) plus a maintenance plan for future KSeF schema and regulatory updates
这是给谁的
Polish VAT-registered SME on Odoo
A trading, manufacturing, or services company registered for VAT in Poland that must move to structured e-invoicing before the 2026 KSeF mandate and wants it native inside its existing Odoo Accounting, not a separate portal.
CEE Odoo implementation partner
An integrator serving clients across Central and Eastern Europe who needs a reliable, reusable KSeF connector to roll out to multiple Polish customers without building FA(2) generation and API auth from scratch on every project.
Finance / accounting lead
A controller or chief accountant responsible for compliance who needs auditable UPO receipts, tracked KSeF reference numbers, and a clear rejection queue so no invoice slips through unconfirmed.
Multi-entity CFO or group finance manager
A finance leader overseeing several Polish legal entities who needs each company to submit under its own NIP and credentials from one Odoo deployment, with consistent controls and reporting across the group.
Poland KSeF E-Invoicing Connector 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| FA(2) XML generation from your posted Odoo invoices | 包含 | Possible, but you build and maintain the FA(2) schema mapping yourself | Sometimes, but often tied to one Odoo version or a generic mapping | 不包括在内 |
| KSeF API auth, session tokens, and outbound submission | 包含 | Build from scratch against KSeF API docs | Varies by vendor; may need extra services | 不包括在内 |
| UPO receipt retrieval stored on the invoice | 包含 | Must implement polling and attachment storage yourself | Sometimes included | 不包括在内 |
| Inbound KSeF invoice retrieval into Odoo | 包含 | Rarely built; adds significant scope | Often missing or paid add-on | 不包括在内 |
| Built and tuned for your Odoo 17/18/19 and tax config | 包含 | Yes, if you have the in-house Odoo capacity | Generic; you adapt it to your setup | 不包括在内 |
| one working week delivery with sandbox validation and go-live support | 包含 | Depends entirely on your team's availability | Self-install; support quality varies | 不包括在内 |
| Documentation, team training, and defined support window | 包含 | You produce and maintain it | Usually docs only, limited support | 不包括在内 |
| Ongoing updates for KSeF schema and regulatory changes | 包含 | Your ongoing burden | Depends on vendor roadmap | 不包括在内 |
关于Poland KSeF E-Invoicing Connector的常见问题
How long until the KSeF connector is live in my Odoo, and what happens after I buy?
This is a build-to-order module, not an instant download. After purchase we start a short scoping call to confirm your Odoo version (17/18/19), tax setup, NIP/company structure, and hosting. Typical lead time is one working week from that call to a validated go-live, including testing against the KSeF sandbox. You receive the installed module, configuration, and documentation at handover.
What support and updates do I get after go-live?
Every engagement includes a defined post-go-live support and bug-fix window with an SLA for KSeF-related issues. Because KSeF's FA schema and API evolve, we also offer a maintenance plan that keeps the module aligned with regulatory and schema changes across the 2026 mandate rollout and beyond. Support terms are confirmed in writing before the build starts.
Does this work with the mandatory 2026 KSeF requirement and the FA(2) format?
Yes. The module generates FA(2) structured XML, authenticates against the KSeF API, submits invoices, and retrieves the official UPO confirmation receipt and KSeF reference number for each document, which is exactly what the mandate requires. We validate the full cycle against the KSeF test environment before your production cutover, and adapt to schema versions in effect at your go-live date.
Which Odoo versions and editions are supported?
Odoo 17, 18, and 19, on both Community and Enterprise. The module is packaged with a clean __manifest__.py and pinned dependencies, and we build against your exact version so it installs cleanly whether you run on-premise, on Odoo.sh, or on ECOSIRE managed hosting.
Can it both send and receive invoices through KSeF?
Yes. Outbound, it pushes your posted customer invoices and credit notes as FA(2) XML and stores the returned UPO and reference number. Inbound, a scheduled action queries KSeF for invoices issued to your NIP and imports them into Odoo automatically, so both sales and purchase documents flow through the national system.
How is access controlled and can external systems read the data?
Access is governed by ir.model.access.csv and record rules so only authorized accounting users can submit, reprocess rejected documents, or view UPO receipts. If you invoice from an external ERP or e-commerce platform, we can optionally expose submission state and KSeF reference numbers over Odoo's XML-RPC/JSON-RPC API so your other systems stay in sync.
相关模块
Poland KSeF E-Invoicing Connector
Send & receive structured FA(2) invoices through Poland's KSeF, with UPO receipts and reference tracking, ready for the 2026 mandate.
- FA(2) structured XML generation from posted account.move invoices and credit notes, mapping Odoo partner, tax, and line data into the KSeF-required schema
- KSeF API authentication with session initiation, token-based auth (interactive and authorization-token flow), and automatic session-token refresh
- Outbound invoice submission that pushes signed FA(2) XML to KSeF and polls submission status until accepted or rejected
- UPO (Urzedowe Poswiadczenie Odbioru) receipt retrieval, stored as an attachment on the source invoice for a complete audit trail