German exporters who zero-rate intra-Community supplies (innergemeinschaftliche Lieferungen) live under a documentary burden: the tax office can revoke the VAT exemption on any delivery where you cannot produce proof that the goods physically arrived in another EU member state. That proof — the Gelangensbestätigung — must carry specific data points (recipient, quantity and commercial description of goods, place and month of arrival, date of issue, and the recipient's or carrier's signature), be reconcilable to the underlying invoice and delivery, and survive a Betriebsprüfung years later. Odoo out of the box tracks the sale, the delivery order, and the invoice, but it has no concept of an arrival confirmation as a first-class, auditable document. Teams end up maintaining Word templates and shared drives, chasing customer signatures by email, and hoping the paper trail holds up under audit. A typical off-the-shelf apps.odoo.com module rarely covers the German-specific field set, the collective quarterly confirmation, or a defensible audit log.

We build a dedicated module that models the Gelangensbestätigung as its own Odoo object. A new models.Model (for example ecosire.arrival.confirmation) links back to the sale.order, stock.picking, and account.move via proper Many2one relations, with @api.depends compute fields that pull the ship-to partner, the commercial goods description and quantities from the delivered move lines, and the destination member state — so the confirmation is always reconciled to real transaction data rather than re-keyed. A QWeb PDF report renders the confirmation in German (and bilingual DE/EN where you need it) with every legally required field, and an automated action (or scheduled ir.cron) can generate and dispatch confirmations at the point of delivery or as a collective monthly/quarterly Sammelbestätigung per customer. Status is tracked through a state field (draft → sent → confirmed) so you always know which deliveries still lack proof, with a warning list of at-risk zero-rated invoices.

The build handles the parts that make this defensible rather than merely cosmetic. Access is governed by ir.model.access.csv plus record rules so only finance and compliance roles can confirm or reopen a document, and every state change and field edit is written to the chatter and an immutable audit log via mail.thread tracking. Where you collect the customer's confirmation electronically, we can expose a tokenised portal/QWeb page or wire a signature capture so the returned Gelangensbestätigung attaches straight back to the record. For EDI or customer-portal integrations we use Odoo's XML-RPC/JSON-RPC API or a controller endpoint rather than brittle CSV drops. The module ships compatible with Odoo 17.0, 18.0, and 19.0, and we confirm at scoping whether you are on Community or Enterprise, since that affects available document, sign, and studio primitives we build against.

Because this is build-to-order, nothing is a pre-existing download. After a short scoping call we confirm your exact field set, languages, collective-confirmation rules, and integration points, then hand back a fixed quote and timeline. Typical delivery is 2–4 weeks from confirmed scope, delivered on a staging database for UAT before we install to production with a rollback plan. Pricing starts from $299 (indicative, single-company base scope); multi-company setups, additional destination-country templates, electronic signature/portal capture, and ERP-to-carrier or EDI integrations increase the quoted scope.