Multi-branch Companies

In multi-branch companies, financial and operational transactions may be recorded without a consistent branch assignment. This can create challenges in access control, performance reporting, inventory traceability, and allocating revenues and expenses to the correct operating unit.

A proposed approach is to establish Branch as a unified operational dimension across transactions. Warehouses, points of sale, and operational activities would be linked to a Branch. Transactional documents would derive the Branch automatically from the selected warehouse, point of sale, or referenced document. For inter-branch transfers, separate Source Branch and Target Branch values would be used.

User permissions, operational reporting, and financial analysis could then be structured around the Branch dimension.

Proposed hierarchy:

Company
│
├─ Operational Branch 1
│ ├─ Cost Centers
│ │ ├─ School
│ │ └─ Hospital
│ ├─ Branch Warehouses
│ └─ Point of Sale
│
├─ Operational Branch 2
│ ├─ Cost Centers
│ │ ├─ School
│ │ └─ Hospital
│ ├─ Branch Warehouses
│ └─ Point of Sale
│
└─ Additional branches as required

In this model, Branch identifies the operating location or business unit, while Cost Center identifies the internal department, project, service line, or activity within that Branch.

Is this a suitable model for multi-branch organizations in ERPNext? What limitations, implementation risks, or design considerations should be addressed, especially across inventory, purchasing, sales, finance, reporting, and user permissions?

Hi @arcchatgpt94 and welcome to the community

You might want to explore accounting dimensions at https://docs.frappe.io/erpnext/accounting-dimensions

Best of luck with your ERPNext journey

ERPNext is not really strong in this area especially if you sale some products in another branch and you dont want them to appear in another branch . You will need to do some customisations to ensure there is strong seperation and at times you will not know what needs to be seperated so you will seperate as you go . For example customers of Branch A will appear in Branch B and many more other things . So you will have some work to do on those customisations but its not much work though maybe a few hours job

Thank you. Accounting Dimensions appears relevant for the financial reporting layer of the branch model, especially for branch-level P&L, budgets, and General Ledger analysis.
However, the matter is broader than financial segmentation. We view Branch not merely as an accounting dimension, but as a core organizational and operational entity.
A branch may have its own employees, employee movements and assignments, attendance, payroll allocation, approvals, departments, warehouses, points of sale, purchasing and sales transactions, assets, projects, operational activities, and financial performance.
The idea is linked everything posseble warehouses, cost centers, employees, departments, and operational transactions would be linked to the relevant branch, with permission and validation rules ensuring that users can only access and process data within their authorized branches.
Would you recommend using Accounting Dimension together with Inventory Dimension, User Permissions, and custom validations for this broader branch model? Are there known limitations or architectural risks we should account for when extending Branch across HR, payroll, inventory, purchasing, sales, finance, and permissions?

Hi @arcchatgpt94

In you particular case, multi company with parent and child set up is required where child company as branch will have its own employees, departments, warehouses, item and COA.

On the other hand, accounting dimension will remain same and serve the purpose of segmental reporting. The user permissions help you control users to stay within restricted enviroment either a company or branch or a warhouse. You need to have custom company link filed on header of each master record such as item, customer or suppliers to have better control on those as well.

Inter company transactions on orders, invoicing and Jvs are possible within child to child or child to parent company. Consolidated Finance Statements with common accounting dimensions will serve reporting purposes effectively.

Thank you for the clarification. In our case, branches are operational and administrative units within one legal company, not separate legal entities requiring independent books, COA, customers, suppliers, or inter-company transactions.
The idea is keep shared master data under one Company and use a unified mandatory Branch field across operational transactions, warehouses, employees, projects, purchasing, stock, and approvals. Accounting Dimensions can support financial analysis, but they do not fully address operational ownership, workflows, and branch-based permissions.

@arcchatgpt94

Creating multi companies and handling them under one legal parent within ERP is a different subject than the actual one. You can do so regardless if you have one legal entity.

It will serve all those purposes of recording and reporting as you wish and mentioned earlier.