A Nepal trading company starts in Kathmandu. After five years, it opens a branch in Pokhara. Two years later, a third location in Biratnagar. Now the owner manages three teams, three cash flows, three stock rooms, and three customer bases - with accounting that still runs through the Kathmandu head office by consolidating hand-delivered monthly reports from the branches. The Pokhara branch manager emails a summary at month-end. The Biratnagar accountant sends a spreadsheet. Someone in Kathmandu aggregates everything, and three weeks after month-end, the owner has a picture of what happened last month.
This delay is not just inconvenient - it means the business is making decisions about all three branches based on information that is already a month old. A slow-moving inventory problem in Biratnagar is only visible when the month-end report arrives. A cash shortfall in Pokhara surfaces when the branch calls asking for a transfer, not when the first warning signals appear in the accounts. The head office cannot see the branches; the branches cannot see each other; nobody has a real-time picture of how the multi-branch business is actually performing.
Multi-branch ERP changes this. Each branch operates its own transactions - purchases, sales, receipts, payments, inventory movements - in the same platform the head office uses. Every transaction posts in real time. The Kathmandu management team can see the Pokhara branch's stock position, yesterday's collections, and the outstanding supplier invoices at any moment, without waiting for a monthly report or calling the branch manager.
Branch-Level Accounting Within a Unified General Ledger
Multi-branch ERP operates through cost center architecture: each branch is a cost center within the single company's chart of accounts. Every transaction - a Pokhara sales invoice, a Biratnagar purchase payment, a Butwal payroll run - is tagged to its branch cost center at the point of entry. The general ledger accumulates all transactions from all branches in one place, with each transaction carrying its branch tag. This gives the head office accountant two views simultaneously: the individual branch P&L (how is Biratnagar performing this month?) and the consolidated company view (how is the total business performing?). Both come from the same data - the cost center tag is the only difference.
Branch-level balance sheets are more complex than branch P&Ls, because some balance sheet items are genuinely company-wide - the owner's equity, the central bank loans, the head office property. The practical approach for most Nepal multi-branch businesses is to produce full P&Ls per branch and use cost center reporting for cost and revenue analysis, while the balance sheet remains at the company level with branch-specific items (branch bank accounts, branch inventory, branch receivables) reported separately as subsidiary schedules.
Nepal businesses operating across multiple provinces must comply with local VAT registration requirements if turnover at any single location exceeds the threshold for VAT registration. A business with a Kathmandu head office that is VAT-registered must also register the Pokhara branch separately if that branch's transactions are above the VAT threshold - branches are not automatically covered by the head office registration in all cases. Separate VAT invoicing, purchase registers, and TDS registers per branch are required by IRD. Multi-branch ERP should maintain these as separate registers per location, even when the underlying accounting is unified in one general ledger.
Stock management across branches has its own requirements. The head office needs to see total company stock as well as per-branch stock. An order received at the Pokhara branch for an item that is out of stock in Pokhara but available in Kathmandu needs to trigger an inter-branch transfer, not a lost sale. Multi-branch inventory tracking shows real-time stock at every location, supports inter-branch transfer orders, and accounts for goods in transit between locations so the stock count is accurate at every point of the transfer process.
Cost center architecture is the right approach for most Nepal multi-branch operations where branches are parts of one legal entity (same PAN, same VAT registration or registered separately per IRD requirement). This produces branch-level financial analysis from one unified general ledger, without the complexity of intercompany accounting required when branches are separate legal entities.
Branch Governance - Authority, Access, and Accountability
Multi-branch operations require clear governance: what can each branch do autonomously, and what requires head office approval? Without defined rules, branch managers either over-delegate (approving expenditure they do not have authority for) or under-delegate (referring every small decision to head office, slowing operations). The ERP enforces the governance rules through role-based access and approval matrix configuration.
A practical governance model for a Nepal four-branch business: each branch manager can approve purchase orders up to NPR 2,00,000, leave applications for their own team, and customer credit limits within the approved policy range. Purchases above NPR 2,00,000 route to the head office CFO or owner. New vendor creation requires head office approval to prevent branches from creating informal local suppliers outside the approved vendor list. Salary changes require HR director approval regardless of which branch initiates them. These rules are configured in the ERP approval matrix and enforced automatically - the branch manager cannot submit a NPR 5,00,000 purchase order directly without it routing to the head office approval queue.
Branch-level user access scoping is as important as the approval matrix. The Biratnagar branch accountant should see Biratnagar's transactions, vendor list, and inventory - not Pokhara's or the Kathmandu head office's confidential accounts. The branch sales team should see customer information for their branch without access to other branches' pricing or customer margins. Configuring access scopes by branch and by role within the branch prevents cross-branch data exposure and ensures that branch performance comparisons are made at management level, not at the accounts team level where competitive dynamics between branches could affect behavior.
Performance reporting per branch creates accountability that informal monthly reports cannot. When the branch manager knows their branch P&L, stock turnover rate, and collection efficiency are visible to head office in real time, not just at month-end, the day-to-day discipline around entries, collections, and stock management improves. The reporting is not surveillance - it is the same information the branch manager should be managing anyway. Making it visible to head office simply ensures that accountability exists at both ends.
Branch governance is the human infrastructure that makes multi-branch ERP effective. The technology enforces the rules; the rules must be defined first. An approval matrix that reflects how authority actually works - not how an org chart says it should work - is the key. Spend time on the governance design before the configuration. A well-designed approval matrix that matches operational reality gets followed; one that ignores how decisions are actually made gets bypassed.
HR and Payroll Across Multiple Branch Locations
Managing HR across Nepal branches creates complexity in three areas: attendance tracking when staff are at different locations, payroll processing that accounts for branch-specific allowances, and leave management when leave approvers are in different cities from the staff they manage. Multi-branch ERP addresses all three.
GPS-based attendance on the mobile app works for each branch location without requiring additional hardware. The geofence is configured for each branch address - Kathmandu head office, Pokhara branch, Biratnagar branch - and staff check in from their assigned location. The system verifies GPS coordinates against the registered geofence before accepting the check-in. Staff who work across multiple locations can have multiple geofences assigned to their profile. Biometric devices at each branch sync to the central HR system, so attendance data from Biratnagar's biometric device appears in the central payroll system alongside Kathmandu's mobile attendance.
Payroll for multi-branch operations needs to handle location-specific allowances - Kathmandu office has a transport allowance that the Biratnagar branch does not, or vice versa. The payroll structure accommodates branch-specific allowance types without requiring a separate payroll run per branch. The single monthly payroll run produces a payroll register filtered by branch, with each branch's payroll total posted to that branch's cost center in the accounting system automatically.
HR and payroll across branches is most efficiently managed from a single configuration with branch-specific parameters rather than separate setups per branch. One payroll master with different allowance profiles per branch location produces a single, consolidated payroll that posts to each branch's cost center automatically. The alternative - separate payroll setups per branch - creates reconciliation work at every period-end and makes cross-branch transfers of staff administratively complicated.
Frequently Asked Questions
Yes. The ERP handles this through separate tax profiles per branch location. Each registered branch has its own VAT registration number, its own VAT purchase register and sales register, and issues invoices under its own registration. The central accounting system aggregates all branches in the general ledger while keeping the VAT registers separate and correctly attributed to each registration. When preparing the VAT return for each branch, the system filters to that branch's transactions only. The head office accounting view shows the consolidated picture; the VAT reporting view shows each branch's registration separately.
Inter-branch cash transfers within one legal entity are treated as internal fund movements, not as income or expense. The ERP handles this through a clearing or inter-branch account: when the head office transfers NPR 5,00,000 to the Pokhara branch, the head office records a debit to Inter-Branch Clearing (Pokhara) and a credit to the head office bank account. The Pokhara branch records a debit to its bank account and a credit to Inter-Branch Clearing (Head Office). At consolidation or in the branch-level view, the clearing accounts offset. In the company's full accounts, neither the debit nor the credit appears as an external transaction - it is a movement of funds within the same entity.
For branches within one legal entity, using a single chart of accounts across all branches is strongly recommended. This makes cross-branch comparison meaningful (Biratnagar's rent expense uses the same account code as Kathmandu's rent expense) and simplifies consolidated reporting. If a branch has genuinely unique expense categories that head office does not use, those can be added to the chart of accounts as branch-specific codes - but the core accounts should be shared. Using separate charts of accounts per branch creates the same aggregation problem as separate accounting software per branch, just within one system rather than across multiple systems.
Branch-Level Control with Real-Time Head Office Visibility and Mobile Access
MISAC's Accounting-First architecture posts every branch transaction to the unified general ledger in real time with the branch cost center tag applied automatically. The head office finance team sees all branches simultaneously in the consolidated view; the CFO drills into any branch for detail with one tap. Every transaction that enters the system - from the Biratnagar stock receipt to the Pokhara sales invoice - follows the same double-entry rules and produces the same automatic journal, regardless of which branch initiated it. Branch-level P&L, stock reports, and receivables ageing are available at any moment by filtering the unified data on the branch dimension.
MISAC's Mobile ERP makes branch management practical for Nepal's geography. The Pokhara branch manager approves purchase orders on their phone. The Biratnagar accounts team submits expense claims from the branch without traveling to Kathmandu. The owner switches between branch views in the MISAC mobile app with one tap - color-coded company profiles ensure they always know which entity's data they are looking at. GPS attendance with geofencing operates independently at each branch location without requiring separate HR software per branch.
MISAC Intelligence Pvt. Ltd. works with Nepal businesses managing two to eight branch locations across the country. Our experience covers the common patterns in multi-branch Nepal operations: the Kathmandu-Pokhara two-branch trading company, the construction group with site offices in multiple districts, the retail chain with stores across three cities. Each structure has different governance requirements but the same underlying need: one view, all branches, real time, from anywhere. Contact us at mis.ac to map your branch structure into a configuration that matches how your business actually operates.
Ready to See MISAC in Action?
Manage your Kathmandu, Pokhara, Biratnagar, and Butwal branches from one ERP with real-time visibility and branch-level controls from any device.