German VAT-registered companies must file a periodic Umsatzsteuervoranmeldung (UStVa) and transmit it through the ELSTER portal, but Odoo core stops at the boundary. Out of the box Odoo can compute a German tax report and give you the totals per tax, yet it has no notion of ELSTER Kennziffern (the numbered fields like 81, 86, 66, 61, 35/36 that the tax authority expects), and it produces no ELSTER-compatible XML you can hand to the portal or an ERiC-based pipeline. Finance teams end up re-keying figures from the Odoo tax report into a separate tool every month — slow, error-prone, and a reconciliation headache when a late invoice shifts a period total.

This is a made-to-order localization module we build, install, and support for your specific chart of accounts and tax configuration. Technically, it introduces a ustva.declaration model (models.Model) representing one filing period, with a compute layer (@api.depends on your account.move / account.tax postings) that aggregates net and tax amounts and maps each Odoo tax to its ELSTER Kennziffer through a configurable mapping model rather than hard-coded IDs — so your bookkeeper controls which tax feeds field 81 vs 86 without a code change. The declaration produces a validated ELSTER XML payload (Elster/UStVa schema, correct Nutzdaten structure, period and Steuernummer/Steuer-ID headers) as a downloadable attachment, plus a human-readable QWeb summary report for internal sign-off before anything is submitted. Access is gated with ir.model.access.csv and record rules so only the accounting team (and, in multi-company setups, the right company) can generate or view a period.

The module ships with a clean __manifest__.py declaring the account dependency, is delivered for your target Odoo major version (17.0, 18.0, or 19.0), and works on both Community and Enterprise — we adapt the tax-report data source to whichever accounting layer your edition exposes. Because generation is deterministic and driven off posted journal entries, re-running a period after a correction simply regenerates the XML from current data; an optional automated action can flag when a locked period has new postings that would change the declaration. The export is also reachable over Odoo's XML-RPC/JSON-RPC API if you want to trigger it from an external filing routine.

Delivery is build-to-order: we start with a short scoping call, confirm your tax mapping and edition, then build, test on a staging copy of your database, and install to production — typically 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company consolidation, additional Kennziffer coverage or Dauerfristverlängerung handling, and migrating historical periods for backfilling increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.