Group CFOs running multiple legal entities in ERPNext hit a wall at consolidation. ERPNext supports a company tree and Multi-Company setups, and its Consolidated Financial Statement report can roll up a parent and its children, but it stops short of what a real group close needs: it does not post or track intercompany elimination entries, it applies limited translation logic when subsidiaries keep different functional currencies, and it gives you little audit trail for the adjustments that turn a stack of standalone ledgers into a defensible group P&L and balance sheet. Finance teams end up exporting each entity to spreadsheets, hand-keying eliminations, and rebuilding the same reconciliation every period — slow, error-prone, and impossible to drill back into ERPNext.

We build a dedicated Frappe app (its own module, installed via bench get-app and bench install-app) that adds a proper consolidation layer on top of your existing ERPNext GL. New DocTypes model the pieces the core is missing: a Consolidation Group (the set of companies and ownership relationships you consolidate), a Consolidation Run (a period-scoped snapshot with status workflow — Draft, Translated, Eliminated, Finalized), an Elimination Rule catalog, and Intercompany Elimination Entry records that store both sides of every knock-out with a full audit trail. The engine reads GL Entries per company for the selected period, translates each subsidiary's balances into the group currency using period-appropriate rates (closing rate for balance-sheet accounts, average rate for P&L, with the residual booked to a currency-translation-adjustment account), applies your elimination rules against tagged intercompany parties, and produces consolidated trial balance, GL, P&L and balance sheet — each with drill-down from the rolled-up group figure to per-entity contribution down to the originating voucher.

Technically, the app is wired the ERPNext-native way. hooks.py doc events keep intercompany transactions tagged as they post; scheduler events can pre-stage nightly rate pulls and balance snapshots so month-end runs are fast; whitelisted server methods expose the consolidation engine over the Frappe REST API so your BI tools or a group reporting portal can pull finalized figures. Consolidated reports are delivered as Query/Script Reports and a workspace, permissions are enforced through role profiles (a Group Finance role sees consolidated output; entity accountants stay scoped to their own company), and client scripts add the run controls and drill-through links in the UI. Everything is compatible with Frappe/ERPNext v15 and v16 and is built to survive upgrades because it extends core through documented hooks rather than patching it.

Because this is build-to-order, we start from your actual company tree, chart-of-accounts mapping, ownership percentages and elimination policies rather than a generic template. After a scoping call we confirm the exact entities, currencies, elimination rules and report layouts in writing, build against that spec, and validate on a staging copy of your data. Typical delivery is one working week from confirmed scope. You receive the installable source, install it (or we install it) on your bench, run UAT on staging with a rollback plan, and go live with a support window and the git repository handed over to you.