ERPNext Multi-Company Setup: Consolidation Done Right (2026)

I lead ERPNext and Frappe programmes at MithTech, a team of Frappe specialists in Bengaluru. Multi-company is a common reason Indian groups outgrow their first accounting tool. A promoter starts with one firm, adds a trading arm, spins off a manufacturing entity, and the books end up in three unconnected places. ERPNext is open source under GPLv3 and treats "the group" as part of the product, not a paid add-on. A careless multi-company setup is harder to unwind than starting fresh, so the structure you choose on day one matters more than any feature.

What does multi-company mean in one ERPNext instance?

Multi-company in ERPNext means several legal entities share one database, one login, and one server, while keeping separate books. Companies can sit side by side as sister firms, or nest under a parent in a group hierarchy. Users, items, and reports can be shared or restricted per company, so one team runs the whole group.

The practical gain is one place for the truth. You are not exporting spreadsheets between systems or licensing three separate tools. Stock, contacts, price lists, and reports live once and are filtered by company. For a group promoter, that means one place to see who owes what across every entity.

Skimmable summary: multiple legal companies share one ERPNext database while keeping separate books, arranged as sister firms or a parent-child group.

When should you use one instance versus separate instances?

Choose one shared instance when the entities are commonly owned, need consolidated reporting, and trade with each other. Choose separate instances only when the businesses are unrelated, have different admins, or face data-isolation requirements. Most Indian groups I work with want consolidation and inter-company flows, so one instance is the usual answer.

A single instance gives you group-level dashboards, shared masters, and automatic inter-company posting. Separate instances give you hard isolation at the cost of duplicated setup and manual consolidation. If you are unsure, start with one instance: ERPNext lets you add companies later without rebuilding, and splitting an entity out is easier than merging two databases.

Skimmable summary: use one instance for commonly owned entities that need consolidation and inter-company trade; use separate instances only for independent businesses.

How do you create multiple companies in one ERPNext instance?

Company creation lives under Accounting, and each new company needs a name, an abbreviation, and a default currency. The abbreviation is important because ERPNext appends it to accounts and warehouses to keep entities apart. To build a group, set the Parent Company field so the new company inherits the parent's chart of accounts structure.

One structural tip: keep the account naming and grouping consistent across companies. ERPNext validates child-company accounts against the parent, and a matching structure is what makes the group reports line up.

Skimmable summary: create each company under Accounting with a unique abbreviation and currency, choose a chart of accounts, then set Parent Company to build the group hierarchy.

How do inter-company transactions work in ERPNext?

Inter-company transactions let a sale in one group company create the matching purchase in another. Setup relies on an internal customer and an internal supplier that each "represent" the other company. Once configured, a submitted sales invoice to the internal customer offers Create → Inter Company Purchase Invoice, which fills in the buying company and supplier, so nobody types the invoice twice.

For entities that move goods between them, the same internal-party concept extends to stock transfers, and for pure financial adjustments you can use an Inter Company Journal Entry that writes the reciprocal entry in the other company. The point of all this is elimination: postings on both sides are what let you find and remove inter-company balances at consolidation.

Skimmable summary: configure an internal customer and internal supplier that represent each other's companies, then create the purchase side from the sales invoice instead of typing it twice.

How does GST and multi-GSTIN work for Indian multi-company setups?

GSTIN in ERPNext is linked to the address, not the company header, so each entity or branch can carry its own registration. A group with firms in different states attaches the right address and GSTIN to each company. India-specific tax logic lives in the separate, open-source India Compliance app, not in core ERPNext.

Since ERPNext Version 14, the Indian GST features were moved out of the core product into the India Compliance app, maintained by Resilient Tech. You install it alongside ERPNext to get GST calculation, GSTR return preparation, purchase reconciliation against 2A and 2B, and e-invoice and e-way bill integration with the government portal. Because GSTIN sits on the address, a single company with multiple state registrations can hold branch-wise addresses, each with its own GSTIN. The company address you choose on a transaction sets the GSTIN it is reported under, and India Compliance works out the place of supply from the party's address.

If you are weighing the total effort of a compliant India rollout, the moving parts and where the real work sits are covered in my write-up on ERPNext implementation cost in India. GST setup is often more work than the company setup itself. Our GST compliance setup covers that side.

Skimmable summary: GSTIN attaches to the address, so each entity or branch carries its own registration; install the India Compliance app for GST returns, reconciliation, and e-invoicing.

How do you produce consolidated financial statements?

Consolidation in ERPNext uses the built-in Consolidated Financial Statement report, which merges the Balance Sheet, Profit and Loss, and Cash Flow of every subsidiary under a group company. Run it against the parent entity and ERPNext rolls up the child companies whose accounts follow the parent's chart of accounts.

The quality of your consolidation is decided upstream. If the account structures drift apart between companies, or inter-company flows were posted by hand on only one side, the consolidated report looks wrong and the close goes into chasing differences. Clean masters and consistent inter-company posting are what keep month-end short.

Skimmable summary: run the Consolidated Financial Statement report against a group company to merge subsidiary Balance Sheets, P&L, and Cash Flow, provided the charts of accounts align.

What goes wrong in multi-company setups?

The most damaging mistakes are structural and show up months later at close. Mismatched charts of accounts break consolidation. Skipping the internal customer and supplier setup forces manual double entry and reconciliation errors. Vague company abbreviations create confusing account names. Over-fragmented GST ledgers make returns harder than they need to be.

None of these are ERPNext limitations; they are setup decisions. In the group rollouts our team has handled, the ones that run well on one instance agreed the account structure before creating the companies, and the ones that fight their own data did not. The fix is plain: design the hierarchy, the shared chart of accounts and the inter-company direction on paper first, then build. If you want a second pair of eyes on the plan, that is the scoping an ERPNext implementation starts with.

Skimmable summary: most multi-company problems come from mismatched charts of accounts, skipped inter-company setup, and unclear abbreviations, all fixable by designing the structure before building.

At a glance

Frequently asked questions