产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $599.00 USD
- Odoo 版本
- 17, 18, 19
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Romania e-Factura + SAF-T D406
A made-to-order Odoo compliance app that submits CIUS-RO e-Factura invoices to ANAF SPV and exports the SAF-T D406 declaration from the same data. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19.
$599.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
CIUS-RO UBL 2.1 e-Factura XML generation from posted `account.move` records with schema and business-rule validation before submission
OAuth2 authentication and submission to the ANAF SPV endpoint, with automatic polling for the signed response and stored ANAF index/download id
Inbound e-Factura retrieval from SPV that creates draft `account.move` vendor bills with mapped taxes, accounts and partners
SAF-T D406 monthly, quarterly and annual XML export built against the current ANAF D406 schema
Mapping tables (dedicated Odoo models) for D406 accounts, tax codes, products and units of measure, secured with `ir.model.access.csv` and record rules
ANAF taxpayer and VAT-status validation via the anaf.ro API, extending `base_vat` for RO numbers
Romanian VAT rates (19/9/5%) and `l10n_ro` chart-of-accounts integration mapped to the correct e-Factura and D406 tax categories
e-Factura and D406 status and error tracking posted to the `mail.thread` chatter for a shared audit trail
ANAF test-vs-production environment switch so the full round trip is validated before live filing
Automated actions / scheduled cron for batch submission and status polling of pending documents
Optional e-Transport (UIT code) declaration hook for goods-movement reporting, scoped on request
XML-RPC / JSON-RPC callable methods so submission and export can be triggered from external systems
State machine on invoices (draft, sent, validated, rejected) with re-submit handling for ANAF error responses
QWeb status report summarising e-Factura submission state and D406 export runs for finance review
关于此产品
Romanian companies now carry two heavy, deadline-driven obligations at once: every B2B and B2G invoice must clear the ANAF SPV e-Factura channel in the CIUS-RO UBL format, and the SAF-T D406 declaration must be filed on the ANAF schema on a monthly or quarterly cadence plus the annual run. Odoo's native l10n_ro gives you the Romanian chart of accounts, VAT tax groups (19/9/5%) and base_vat validation, and account_edi provides an EDI framework — but out of the box there is no CIUS-RO document builder, no OAuth2 handshake with SPV, no inbound document fetch, and nothing that assembles the D406 XML. Teams end up exporting to spreadsheets, hand-uploading to the ANAF portal, and reconciling errors after the fact.
为什么选择 Romania e-Factura + SAF-T D406
CIUS-RO UBL 2.1 e-Factura XML generation from posted `account.move` records with schema and business-rule validation before submission
OAuth2 authentication and submission to the ANAF SPV endpoint, with automatic polling for the signed response and stored ANAF index/download id
Inbound e-Factura retrieval from SPV that creates draft `account.move` vendor bills with mapped taxes, accounts and partners
SAF-T D406 monthly, quarterly and annual XML export built against the current ANAF D406 schema
Mapping tables (dedicated Odoo models) for D406 accounts, tax codes, products and units of measure, secured with `ir.model.access.csv` and record rules
ANAF taxpayer and VAT-status validation via the anaf.ro API, extending `base_vat` for RO numbers
This is a build-to-order app that ECOSIRE designs, builds, and installs specifically for your Odoo database. We extend account.move with the fields, compute/@api.depends methods and state machine needed to generate valid CIUS-RO UBL 2.1 XML directly from your posted invoices, then submit it to the ANAF SPV over OAuth2, poll for the signed response, and store the returned index and signed document against the invoice. Inbound e-Factura documents are pulled from SPV and turned into draft account.move vendor bills with your mapped taxes and accounts, so accounts payable starts from a matched draft rather than a PDF. Every submission, download, error message and ANAF status lands on the mail.thread chatter so finance and auditors share one timeline.
The SAF-T D406 side reuses the same posted ledger. We build the D406 monthly/annual XML export against the current ANAF schema, driven by mapping tables (regular Odoo models with ir.model.access.csv and record rules) that translate your accounts, taxes, products and units of measure into the codes ANAF expects — so the declaration reflects your real chart rather than a generic template. A dedicated test-vs-production environment switch lets you validate the full round trip against the ANAF test endpoint before any live filing, and an optional e-Transport (UIT) declaration hook can be scoped in for goods movements. Everything is delivered as a proper Odoo module: __manifest__.py with pinned dependencies (account, account_edi, base_vat, l10n_ro), XML/OWL views, QWeb status reports, security rules, and automated actions for scheduled submission and status polling, all callable over XML-RPC/JSON-RPC for integration.
Because it is built to order, there is no instant download — after a short scoping call we confirm the exact e-Factura profiles, D406 mapping depth and environments in writing, then build and hand over on staging for UAT before go-live. Typical delivery is 2 to 4 weeks from confirmed scope. Pricing starts from $599 (indicative, single-company base scope); multi-company groups, deeper D406 mapping, e-Transport, and custom integrations increase the quoted scope.
你得到什么
- Installable, version-pinned Odoo module source for your target version (17.0, 18.0 or 19.0)
- Installation and configuration on your Odoo instance, including ANAF SPV OAuth2 credentials and environment switch setup
- Technical documentation covering models, fields, mapping tables and the XML-RPC/JSON-RPC integration surface
- End-user guide plus a live training session for your finance and AP team
- Post-go-live support window for defect fixes and ANAF-round-trip questions
- UAT on a staging database with a documented rollback plan before production cut-over
- Git repository handover with full commit history and tagged release
- Configured D406 mapping tables seeded from your live chart of accounts and tax setup
这是给谁的
Romanian SME finance manager
Runs monthly VAT and SAF-T D406 filing and needs mandatory e-Factura submission handled inside Odoo without exporting to spreadsheets or the ANAF portal by hand.
Group accountant / shared-services controller
Oversees several Romanian legal entities and wants one consistent e-Factura and D406 process across companies, with mapping tables and audit trail per entity.
Odoo partner / internal ERP team
Maintains a customised Odoo deployment and wants a clean, dependency-pinned module they can read, extend and support, delivered with the git repo rather than a black box.
AP / compliance lead
Responsible for inbound vendor e-invoices and error resolution; needs SPV documents pulled in as draft bills and every ANAF status visible on the chatter for auditors.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Romania e-Factura + SAF-T D406 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Romania e-Factura + SAF-T D406，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Romania e-Factura + SAF-T D406 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| e-Factura CIUS-RO submission | Built for your data, OAuth2 to SPV with signed-response storage | Possible but you design the whole SPV integration from scratch | Generic UBL that may not match your tax/account mapping | |
| SAF-T D406 export | Monthly/annual XML on current ANAF schema, mapped to your chart | Full schema build is a large, error-prone in-house effort | Often sold separately or with fixed, non-configurable mapping | |
| Inbound vendor e-invoices | SPV pull creates mapped draft vendor bills | Must build fetch and mapping logic yourself | Frequently outbound-only | |
| Fit to your chart & taxes | Mapping tables seeded from your live accounts/taxes/UoM | Fully bespoke but you maintain it all | One-size template you adapt manually | |
| Test vs production | Environment switch, full round trip validated in UAT | You build and test the sandbox handling | Varies by vendor, not always exposed | |
| Auditability | Statuses, errors and documents on the `mail.thread` chatter | Whatever logging you choose to build | Limited or vendor-specific logging | |
| Ownership & source | Full source plus git repo handover, yours to extend | You own it but carry all build cost and risk | Licensed binary, limited or no source access | |
| Delivery & support | 2–4 weeks build-to-order, install, training, support window | Long internal project, support is your team's burden | Instant install but self-service configuration |
关于Romania e-Factura + SAF-T D406的常见问题
Is this an app I can download and install today?
No. It is a build-to-order app that ECOSIRE builds specifically for your Odoo database. There is no instant download — we scope, build, install and support it for you, and you receive the full source and git repository on handover.
How long does delivery take?
Typical delivery is 2 to 4 weeks from confirmed scope. After a short scoping call we agree the e-Factura profiles, D406 mapping depth and environments in writing, then build and hand over on staging for UAT before go-live. Complex multi-company or e-Transport scopes can extend the timeline.
How does pricing and scoping work?
Pricing starts from $599 as an indicative single-company base-scope figure. We give a fixed quote only after the scoping call, once the exact companies, mapping depth, integrations and environments are confirmed. Multi-company, deeper D406 mapping, e-Transport and custom integrations increase the quoted scope.
What support and updates do I get after go-live?
Every build includes a post-go-live support window for defect fixes and ANAF round-trip questions. Because the module tracks the evolving ANAF e-Factura and D406 schemas, we can quote ongoing maintenance to keep it aligned as ANAF updates its specifications and validation rules.
Which Odoo versions and editions are supported?
We build for Odoo 17.0, 18.0 and 19.0. The module depends on `account`, `account_edi`, `base_vat` and `l10n_ro`, which are available in Community; we confirm your exact edition and installed localisation during scoping so the dependency chain and accounting flows match your setup.
Can it both submit outbound invoices and pull inbound vendor bills?
Yes. It generates and submits CIUS-RO UBL e-Factura for your sales invoices to SPV, polls for the signed response, and separately fetches inbound e-Factura documents from SPV to create draft vendor bills with your mapped taxes and accounts.
How do you make sure filings are correct before going live?
An ANAF test-vs-production environment switch lets us validate the complete e-Factura and D406 round trip against the ANAF test endpoint on your staging database during UAT. Only after you sign off do we cut over to the production environment, with a documented rollback plan in place.
申请报价
Romania e-Factura + SAF-T D406
A made-to-order Odoo compliance app that submits CIUS-RO e-Factura invoices to ANAF SPV and exports the SAF-T D406 declaration from the same data. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19.
- CIUS-RO UBL 2.1 e-Factura XML generation from posted `account.move` records with schema and business-rule validation before submission
- OAuth2 authentication and submission to the ANAF SPV endpoint, with automatic polling for the signed response and stored ANAF index/download id
- Inbound e-Factura retrieval from SPV that creates draft `account.move` vendor bills with mapped taxes, accounts and partners
- SAF-T D406 monthly, quarterly and annual XML export built against the current ANAF D406 schema