If you run high-volume order flows in Odoo, you already know the friction: a single customer places ten separate sales orders across a month and expects one clean invoice, but Odoo's native "Create Invoice" acts per-order, leaving your finance team either manually stitching line items together or sending a stack of small invoices that the customer's AP department rejects. The same pain runs in reverse on procurement — many purchase orders to one vendor should reconcile against one consolidated vendor bill, not twenty. Odoo core does support batch invoicing when you multi-select records in the same list, but it groups by partner and a few hard-coded keys with no control over grouping logic, no cross-order deduplication, no consolidated QWeb layout, and no guardrails when currencies, fiscal positions, or invoice addresses differ. That is where native runs out of road.

This is a made-to-order module we build for your database — not an existing download. At its core is a transient wizard (models.TransientModel) that accepts a selection of confirmed sale.order or purchase.order records and produces one account.move per validated group. We implement the grouping engine as a configurable strategy — default keys are partner_id, currency_id, company_id, and fiscal_position_id, extendable to your own dimensions (invoice address, salesperson, analytic account, project, delivery period) — with compute methods decorated by @api.depends so totals and eligibility recalculate live. Each generated invoice line carries a link back to its originating sale.order.line / purchase.order.line, so the standard "Source Document" and drill-down remain intact and your audit trail is never broken. Pre-flight validation blocks unsafe merges (mixed currencies, mismatched fiscal positions, partially-invoiced quantities) and surfaces a clear reason rather than silently producing a wrong account.move.

On the technical surface the build ships as a proper addon: a versioned __manifest__.py declaring dependencies on sale, purchase, and account; ORM models and wizard; ir.model.access.csv plus record rules so consolidation respects your existing multi-company and sales-team boundaries; XML/OWL views that add the "Consolidate Invoices" action to the Sales and Purchase list views; a dedicated QWeb report template that renders the consolidated document grouped by source order with subtotals; and optional automated actions (ir.cron / base.automation) so recurring consolidation — for example, one invoice per customer at month-end — can run unattended. Every generated document is available through the standard XML-RPC/JSON-RPC API, so downstream integrations and e-invoicing flows see a normal account.move. We target Odoo 17.0, 18.0, and 19.0, and we build against Community or Enterprise depending on your edition (Enterprise-only features such as full accounting reconciliation views are respected, never assumed).

Build-to-order delivery works in stages: a short scoping call to confirm your grouping rules, editions, and edge cases; a fixed written quotation; development on an isolated branch; UAT on a staging copy of your database; then production install with a rollback plan and a post-go-live support window. Typical delivery is one working week from confirmed scope, depending on complexity and your team's review turnaround. Pricing starts from $999 (indicative, single-company base scope); multi-company consolidation, bespoke grouping dimensions, custom consolidated report layouts, and integration with existing e-invoicing or EDI flows increase the quoted scope. You receive a firm fixed price after the scoping call — never a surprise.