Group operating model guide
Choose the right structure for legal entities, branches, warehouses, shared services and management reporting before configuration begins.
In ERPNext, a Company should generally represent an accounting entity with its own books, while branches may be analysed using warehouses, Cost Centers, Accounting Dimensions and permissions. The correct design depends on legal ownership, tax registration, stock ownership, banking, intercompany activity and reporting—not merely the organisation chart.
Do not confuse a company, branch and warehouse
Groups often begin implementation by copying the organisation chart into ERPNext. That can create too many Companies, duplicated masters and complicated reporting. The better starting point is legal and accounting reality: who owns the transaction, stock, bank account, receivable, payable and tax obligation?
A Company in ERPNext carries its own Chart of Accounts and accounting defaults. A warehouse represents stock location or responsibility. Cost Centers and Accounting Dimensions support analytical views. User Permissions and company restrictions limit access. These tools solve different problems and should not be used interchangeably.
Use a decision model before creating entities
| Question | If yes, consider | Why it matters |
|---|---|---|
| Does the unit keep separate statutory books? | Separate Company | Ledger, fiscal settings and financial statements belong to the entity |
| Does it own physical stock separately? | Company and/or warehouse structure | Transfers, valuation and intercompany sale may differ |
| Is it a location within one legal entity? | Warehouse, Cost Center or Accounting Dimension | Supports branch analysis without duplicating the ledger |
| Should users see only selected operations? | Roles and User Permissions | Access is a security decision, not an accounting structure |
Tax registrations, trade licences and reporting obligations should be reviewed with qualified advisers. A system structure must follow the approved legal treatment rather than trying to define it.
Make intercompany activity visible and reconcilable
ERPNext supports intercompany invoices and journal entries. The group still needs a policy for transfer pricing, markup, currency, tax, settlement, goods in transit and period cut-off. One entity’s sale should correspond to the counterparty’s purchase, with differences investigated rather than manually forced.
- Use dedicated intercompany customer and supplier relationships.
- Define who initiates and who confirms the paired transaction.
- Match quantities, values, currency and document dates at period end.
- Track stock or services delivered but not yet invoiced by either entity.
- Reconcile balances before consolidation and retain explanations for differences.
Use dimensions for branch and management visibility
Cost Centers and Accounting Dimensions can capture branch, department, channel or another analytical segment. Choose dimensions that answer recurring decisions. Too many mandatory dimensions slow data entry and create low-quality defaults; too few force finance back into spreadsheets.
Warehouse reports show stock by location, while financial dimensions show revenue, expense and profitability according to configured postings. A branch performance view may require allocations for shared payroll, rent, marketing or central services. Define that management methodology openly—it is not a fact automatically produced by software.
Balance local access with central governance
Role Based Permissions, User Permissions and company restrictions can limit records and actions. Avoid creating broad administrator access for convenience. Define who may create masters, change price, transfer stock, post journals, approve payments, reopen periods and view payroll or other sensitive data.
Central teams may own policy and master data while branches execute transactions. That model needs service levels and escalation so central control does not become a bottleneck. Access should be reviewed after transfers, role changes and exits—not only at initial setup.
A safe implementation sequence for groups
Confirm the legal and reporting model
Document entities, registrations, currencies, banks, stock ownership, branches and management views.
Prototype two contrasting units
Test one complex entity and one branch or subsidiary to expose sharing, permissions and intercompany issues.
Reconcile opening positions
Load and validate each entity’s trial balance, parties, bank, stock, assets and intercompany balances.
Test the group close
Run branch reporting, intercompany matching, currency treatment and consolidation outputs before go-live.
Roll out with governance
Use a repeatable company or branch onboarding pack, data owner and access review for every new unit.
ERPNext can provide consistent source data across the group, but formal consolidation, eliminations and statutory reporting requirements should be validated. Some groups may use external consolidation or business-intelligence tools.
Know where group reporting needs additional design
Multi-company visibility is not the same as formal consolidation. Groups may need elimination of intercompany revenue, cost, receivables, payables and unrealised profit; consistent account mapping; ownership adjustments; currency translation; and statutory presentation. Confirm whether ERPNext reports meet the requirement or whether a controlled consolidation workbook or specialist tool is needed.
Create a group reporting calendar with entity submissions, reconciliation, intercompany confirmation, adjustments, review and lock dates. Use common definitions for revenue, margin, headcount and branch performance. If local entities can change account or dimension structures independently, establish a mapping and change process. Comparable data is a governance achievement, not an automatic consequence of using one application.
Frequently asked questions
Can ERPNext manage multiple companies in one system?
Yes. ERPNext supports multiple Company records, each with its own accounting structure and defaults. Setup should reflect genuine legal and accounting entities, with permissions and intercompany processes tested carefully.
Should every branch be created as a separate Company?
Not necessarily. A branch within one legal entity may be represented through warehouses, Cost Centers, Accounting Dimensions and permissions. Separate books, ownership, tax and statutory requirements may justify a separate Company.
Does ERPNext support intercompany transactions?
ERPNext supports intercompany invoices and journal entries. The group must still define transfer pricing, tax, currency, settlement, cut-off and reconciliation policies.
Can branch users be restricted to their own data?
ERPNext provides roles, User Permissions and company restrictions. The exact access model should be tested for reports, linked records, exports, APIs and administrative actions—not only the main forms.
Can ERPNext produce consolidated financial statements?
ERPNext can provide multi-company financial data, but consolidation, eliminations, currency translation and statutory presentation requirements should be validated. Some groups may use additional reporting or consolidation tools.
What data is needed for a multi-company migration?
Prepare reconciled balances for each entity, shared and local masters, intercompany counterparties and balances, currencies, banks, tax settings, warehouses, dimensions, open transactions, assets and user access rules.
Create one operating model without blurring legal responsibility
We can help you design the company, branch, warehouse, dimension and access structure before costly configuration decisions become difficult to reverse.
Useful references
- ERPNext Company setup
- ERPNext Inter Company Invoices
- ERPNext Accounting Dimensions
- ERPNext Role Based Permissions
- Craft Interactive ERPNext implementation
Product behaviour can vary by ERPNext and Frappe version, installed applications, configuration and custom code. UAE tax, privacy, employment and sector requirements should be confirmed with qualified advisers and the relevant authorities. This article provides implementation guidance, not legal, tax or accounting advice.