Finance teams that raise many small invoices for the same customer end up drowning in paperwork: ten deliveries in a month become ten account.move records, ten PDFs, ten payment references, and ten reconciliation lines. Customers ask for one consolidated invoice; your team ends up either credit-noting and re-keying by hand or exporting to a spreadsheet to bolt figures together. Odoo core has no supported way to fold several posted or draft invoices into a single document — the sale/subscription "invoicing policy" batches at generation time, not after the fact, and there is no button that says "combine these five into one." That gap is exactly where manual workarounds creep in and errors follow.

ECOSIRE builds Merge Invoices as a proper Odoo module for your database. At its core it adds a server action and wizard over account.move: select several draft (or, per your policy, cancellable-and-reissuable) customer invoices for the same partner, currency, and company, and generate one consolidated account.move whose lines are the union of the source invoice lines — preserving analytic distribution, taxes, product references, and the source document numbers as a traceable origin. The wizard validates that partners, currencies, fiscal positions, and companies match before it will merge, and it records a clean audit trail (ir.logging plus a message on the chatter of both the merged invoice and the sources) so an auditor can always walk from the single invoice back to what it replaced. Access is governed by ir.model.access.csv and record rules so only accounting users with the right group can run a merge, and multi-company record rules keep the action inside the operating company. We wire the whole thing with a __manifest__.py that depends only on account, ship OWL/XML views and a QWeb-ready consolidated layout, and keep the compute logic in tested @api.depends methods rather than fragile onchange hacks — so it upgrades cleanly across Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise.

Because this is a productized service, not a shelf download, the behaviour is shaped to your reality during scoping: whether merges happen on drafts only or reverse-and-reissue posted moves, how source references are stamped on the consolidated lines, whether you group by partner-and-period or by a custom key, how down-payments and existing credit notes are handled, and whether the action is exposed in the list view, on the partner, or triggered by an automated action or the XML-RPC/JSON-RPC API for headless batch runs. You get code built for your version and your chart of accounts, not a generic binary you have to bend to fit.

Delivery is build-to-order. After a short scoping call we confirm exact scope in writing, then build on a staging copy of your database, run UAT with your team, and cut over with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, depending on edge cases and how many localizations or integrations touch invoicing. Pricing starts from $299 (indicative, single-company base scope); multi-company consolidation, deep localization or e-invoicing hooks, and large historical data migration increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.