Intercompany Transactions & Reconciliation

ECOSIRE builds a purpose-fit module that closes that gap for your specific company structure. At its core is a set of new ORM models (models.Model) that record configurable company pairings — for each ordered pair of res.company records you define the partner mapping, the mirror document type, the target journals, tax mapping, and pricelist. When a source document is validated, an automated action (or an overridden action_confirm/action_post) generates the mirrored counterpart in the other company: a sales order becomes a purchase order, a customer invoice becomes a vendor bill, and the corresponding account.move lines are created with @api.depends-driven computed fields so amounts, taxes and currency are derived from the source rather than retyped. Every mirrored record carries a stored reference back to its origin so the pair is always traceable and never double-generated on re-validation.

On top of the mirroring, we build the reconciliation layer your close actually needs: a balance reconciliation report (rendered as a QWeb report and an on-screen list/pivot view built in XML/OWL) that pulls the posted intercompany receivables and payables per company pair and flags any variance — unmatched documents, amounts that differ, or entries stuck in draft on one side. Line-level tagging marks intercompany moves as elimination-ready so your consolidation or group reporting can strip them cleanly. Access is governed by ir.model.access.csv plus record rules that keep each company's users scoped to their own data while letting the sync engine cross the boundary under a controlled context. Everything is exposed over the standard XML-RPC/JSON-RPC API, so an external consolidation tool or a parent-company script can read pairings, trigger a reconciliation run, or pull the variance report programmatically.

Because this is a build-to-order engagement, nothing is a blind download. We start with a short scoping call to map your entity structure, the document flows you want mirrored, your tax and multi-currency rules, and your chart-of-accounts alignment. We then build against your Odoo major version (17.0, 18.0 or 19.0), respecting Community vs Enterprise differences — if you already run Enterprise inter-company rules we extend and reconcile with them rather than fight them. You get the work validated on a staging copy of your database (UAT) before anything touches production, with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full installable source, documentation, and a post-go-live support window.