A build-to-order Odoo module that automatically assigns DATEV-compliant customer (debitor) account numbers the moment a partner becomes a customer, so your accounting export matches your German chart of accounts every time. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
A build-to-order Odoo module that automatically assigns DATEV-compliant customer (debitor) account numbers the moment a partner becomes a customer, so your accounting export matches your German chart of accounts every time. ECOSIRE scopes, builds, installs, and supports it for you.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Odoo 上构建、配置并安装。
约 2–4 周内上线，并提供上线后的支持期。
German accounting teams running Odoo hit the same wall when they reconcile with DATEV: every customer needs a debitor account number that fits the SKR03/SKR04 numbering ranges (commonly the 10000–69999 debitor band), and Odoo core has no concept of it. Out of the box you either leave partner.ref blank, type numbers by hand into a spreadsheet, or bolt on a fragile pre-export step. The results are duplicate numbers, gaps that break the DATEV/ASCII export, and a Steuerberater who sends the file back. It gets worse at scale — a sales team creating dozens of customers a week cannot be trusted to remember the next free number in a shared sequence.
We build a focused Odoo module that generates the DATEV debitor number automatically and deterministically. Technically, it extends res.partner with a stored, indexed debitor field and hooks the assignment into the ORM: a create/write override (or an ir.actions.server automated action) fires when a partner first becomes a customer, draws the next value from a dedicated ir.sequence bounded to your configured DATEV range, and guards against collisions with a SQL unique constraint plus a pre-write check so two concurrent sales users can never claim the same number. A @api.depends-driven compute keeps any display/mirror fields in sync, and the assigned number flows into partner.ref (or a custom field) so the standard DATEV export and your account.move postings pick it up with no extra manual step.
Configuration lives in a small settings model: start number, range ceiling, zero-padding width, and whether numbers are reused when a partner is archived. Where you run multi-company or several accounting books, we scope the sequence per company so each entity keeps its own contiguous debitor range. Everything ships with ir.model.access.csv rules plus record rules so only accounting roles can edit the number, an XML/OWL settings view for the configuration, and — when useful — a QWeb report or list export of the debitor register for your tax advisor. We can also expose read access over Odoo's XML-RPC/JSON-RPC API so an external DATEV-side tool can pull the mapping. The module targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise (Enterprise's DATEV-specific accounting features are respected, not duplicated).
Delivery is build-to-order: it starts with a short scoping call to confirm your chart of accounts (SKR03 vs SKR04), the exact debitor range, multi-company layout, and how existing customers should be back-filled. We then build against your Odoo version on a staging copy, run UAT with you, and deploy with a rollback plan; typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company debitor ranges, migration of large existing customer bases, and deeper DATEV/export integration increase the quoted scope.
Runs Odoo Accounting and exports to DATEV monthly. Needs every customer to carry a valid, unique debitor number in the SKR range so the ASCII export is accepted by the Steuerberater without manual cleanup.
Receives DATEV exports from a client on Odoo. Wants contiguous, gap-aware debitor numbering and a clean debitor register so bookings map to the right accounts with no reconciliation friction.
Manages several German entities in one Odoo database. Needs per-company debitor ranges that never collide, plus role-based control over who can edit the number.
Creates new customers throughout the day and cannot be expected to know the next free number. Needs the debitor number assigned silently and correctly at partner creation.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Fit to your DATEV / SKR setup | Built to your exact SKR variant and debitor range | Fully bespoke but you own all analysis | Generic assumptions, may not match your range | |
| Automatic assignment on customer creation | Silent assignment via ORM hook / automated action | Whatever you build; must design the trigger | Often only a manual button or import | |
| Concurrency / duplicate protection | `ir.sequence` + unique constraint + pre-write check | Only if you engineer it | Varies; frequently unguarded | |
| Multi-company debitor ranges | Per-company scoped sequences, no collisions | Possible with extra effort | Usually single-range only | |
| Existing-customer back-fill | Controlled, logged back-fill run included | You script and validate it | Rarely provided | |
| Access control on the number | Record rules limit edits to accounting roles | Depends on your build | Often editable by anyone | |
| Version & edition coverage | Built and tested on 17/18/19, Community + Enterprise | Whatever you target | Often lags Odoo major versions | |
| Ongoing support & upgrades | Support window + agreed upgrade path | You maintain it | Vendor-dependent, generic |
No. This is a build-to-order product. We build the module against your Odoo version and your chart of accounts, then install and support it. It is not an existing marketplace download, so it fits your DATEV setup rather than forcing a generic one.
Typical delivery is 2–4 weeks from confirmed scope. The timeline starts after the scoping call, once we have agreed your SKR variant, debitor range, multi-company layout, and any back-fill of existing customers. Larger migrations or deeper integrations extend it.
Pricing starts from $249 (indicative, single-company base scope). After a short scoping call we send a fixed written quote. Multi-company ranges, back-filling a large existing customer base, and additional DATEV/export integration increase the scope and the quote.
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. On Enterprise we respect the built-in DATEV accounting features rather than duplicating them; the module fills the automatic-debitor-numbering gap that core does not cover.
Every build includes a post-go-live support window for defect fixes and small adjustments. Beyond that we offer ongoing support and version-upgrade work (for example moving the module from Odoo 17 to 18 or 19) as a separate agreed engagement.
Yes. We include a controlled back-fill routine that assigns compliant, gap-aware debitor numbers to your existing customer base in a single logged run, so both new and legacy partners end up in your DATEV range. The run is validated on staging first.
No. Assignment draws from a dedicated `ir.sequence` and is protected by a SQL unique constraint plus a pre-write next-free check, so concurrent creation by multiple sales users cannot produce a collision.
A build-to-order Odoo module that automatically assigns DATEV-compliant customer (debitor) account numbers the moment a partner becomes a customer, so your accounting export matches your German chart of accounts every time. ECOSIRE scopes, builds, installs, and supports it for you.