The owner of a Kathmandu trading group wakes up in Pokhara, where he has come to inspect a new retail space for his fourth company. Before the property visit, he opens his phone. In three seconds he has checked yesterday's cash balance across all four entities: the import trading company in New Baneshwor, the retail chain in Pokhara, the construction materials company in Bhaktapur, and the new holding company incorporated last Baisakh. He taps into the Bhaktapur entity to see why the receivables balance increased by NPR 12 lakh last week. It is two invoices from the same large contractor - he makes a mental note to call the accounts manager about follow-up.
This is what group company management software makes possible. Not four separate accounting systems requiring four separate logins, four separate month-end processes, four separate reports that someone has to manually consolidate in Excel. One platform, all entities, real-time view, controlled access per entity for staff who only need to see their own company's data.
Nepal's family business culture produces group structures organically. What starts as one trading company spawns a construction arm when a large project opportunity arrives, then a hospitality entity when the family buys a property in Pokhara, then a real estate holding company when the financial advisor recommends separating the assets. Within a decade, the founder is managing four or five legal entities, each with its own PAN, VAT registration, bank accounts, and staff - and typically, each with its own accounting setup that no one has time to consolidate properly.
The Group Management Problem in Nepal Businesses
Managing a group of Nepal companies without unified software creates three recurring problems. The first is visibility: the owner or board cannot see the group's true position without waiting for each entity's accounts team to prepare a summary. By the time the summaries arrive - typically after month-end close, often weeks into the following month - the information is historical rather than actionable. Decision-making operates on data that is always at least a month old.
The second problem is consolidation. When the board or bank wants a group-level financial statement, someone has to aggregate the five entities' financials. This is manual work: export each entity's trial balance, bring it into Excel, eliminate intercompany transactions (the loan from the holding company to the trading subsidiary, the management fees between entities, the shared-cost allocations), and produce a consolidated P&L and balance sheet. Experienced finance teams do this in three or four days. Less experienced teams take longer, make more errors, and often skip the intercompany elimination step - which means the consolidated figures are overstated by the value of transactions between group companies.
Nepal's Company Act 2063 and the related Company Regulations require groups of companies where one entity holds a controlling interest in another to maintain group-level financial records and in some cases produce consolidated financial statements. The Office of the Company Register (OCR) has progressively increased oversight of group reporting. Businesses that have grown their group structure without formalizing the financial reporting architecture may find that a financing institution, investor, or regulatory review requires consolidated statements they are not currently producing. Building the consolidated reporting capability before it is demanded is significantly less stressful than building it under deadline.
The third problem is control. When each entity has its own software and its own accounts team, the group owner has limited visibility into what decisions are being made at each entity level. A subsidiary's accounts manager approves a vendor payment that, across the group, represents a third payment to the same vendor for the same service across three entities - a pattern that might indicate overbilling. Without a group-level view, no one sees the pattern. With unified software, the pattern is visible in a cross-entity vendor report.
Group management software addresses visibility, consolidation, and control simultaneously. The owner gets a real-time view, the finance team gets automatic consolidation, and the board gets the cross-entity transparency that four separate systems cannot provide. The investment in unified group software typically pays for itself within the first quarter of consolidated reporting, simply from the finance team time that is no longer spent on manual aggregation.
Architecture - How Unified Group Management Works
Group company management in a modern ERP works through a multi-tenant or multi-entity architecture where each legal entity has fully isolated data - its own chart of accounts, its own financial statements, its own VAT registration records - but all entities exist within one platform that a group-level administrator can access. The isolation ensures that the accounts team at Company A cannot see or modify Company B's data. The group view allows the owner to see all entities simultaneously without switching between systems.
User access is entity-scoped. The accounts manager at the Bhaktapur construction company has access to that entity only. The group CFO has access to all entities. The founder has a group-level dashboard that shows consolidated key metrics across all entities in one view, with the ability to drill into any entity for detail. Access can be configured to allow read-only group view without entity-level modification rights - useful for the founder who needs visibility but should not be able to post transactions.
"The right group management architecture isolates each entity's data completely while giving the owner exactly the cross-entity visibility they need - no more, no less. The goal is not one big combined ledger; it is one unified window into four separate ledgers."
A principle seen consistently across well-managed Nepal group structures
Intercompany transactions - loans between entities, management fees charged by the holding company to subsidiaries, shared cost allocations - need to be recorded in both entities and tracked for consolidation elimination. Group software handles this through intercompany posting: a management fee charged by the holding company to the trading subsidiary is recorded as income in the holding company and as an expense in the trading subsidiary, with a link that allows the consolidation engine to eliminate both sides when producing the group-level statement. Without this link, the elimination must be done manually during consolidation - the most error-prone step in the entire process.
Multi-entity architecture in an ERP is different from simply having multiple accounts in one system. True multi-entity support means each company has an independent chart of accounts, its own VAT and TDS registers, its own user access scope, and its own financial statements - while the group-level view and consolidation engine treat all entities as one financial universe for reporting purposes.
Group-Level Reporting and Consolidated Financial Statements
The primary output of group company software is consolidated financial reporting: a group P&L, group balance sheet, and group cash flow statement that represent all entities as a single economic unit with intercompany transactions eliminated. For Nepal family business groups, this consolidated view is what a financing bank, a potential investor, or a regulatory review will ask for first.
Below the consolidated level, group reporting also includes comparative reporting across entities: which company contributed the most revenue this quarter, which entity has the highest cost-to-revenue ratio, which subsidiary's receivables are most overdue. These comparisons are not possible when each entity has a separate accounting system - they require a common data platform where all entities' data can be queried together. Group software provides this out of the box; manual consolidation in Excel provides only the aggregate view, not the entity-by-entity comparison.
For the Nepal group owner who manages both operations and finance, the most useful daily output is not the full consolidated statement - that is a month-end product. The daily output is a group cash position report: today's bank balance across all entities, all accounts, in one view. This single report - which takes thirty seconds to read on a phone - answers the question that most group owners ask most frequently: "Do we have enough cash across the group to cover this month's obligations?"
Group reporting serves different audiences at different frequencies. The board and financiers need monthly consolidated financial statements. The owner needs a daily group cash position. The group CFO needs weekly cross-entity variance reports. Good group software provides all three without requiring the finance team to produce each as a separate manual exercise. Define the reporting calendar before implementing the system so the configuration meets the actual information needs from day one.
Frequently Asked Questions
Yes, each entity can maintain its own chart of accounts reflecting its specific business structure - the trading company will have different expense categories than the hospitality entity. For consolidated reporting, the group finance team maintains a mapping that aligns each entity's account codes to a common group reporting structure. This mapping allows the consolidation engine to aggregate the right accounts from each entity into the correct group-level line item, even when the underlying account codes differ between entities. Maintaining some degree of consistency in the chart of accounts structure across entities simplifies the mapping and reduces the risk of misclassification in the consolidated statements.
In Nepal, all businesses use the Bikram Sambat fiscal year starting Shrawan 1, so this is not typically a variable. For group structures that include a foreign subsidiary or joint venture partner on a different fiscal calendar (rare but possible), the group reporting period is defined at the group level and each entity's data is pulled for the overlapping period. In most Nepal group structures, fiscal year alignment is not an issue. The more common period mismatch is different month-end closing dates across entities, which the consolidation engine handles by using actual posted data as of the consolidation run date rather than waiting for formal monthly close from each entity.
The right time is when the owner finds themselves making financial decisions without an accurate view of the group's combined position. Practically, this typically occurs when the group has three or more active entities, when intercompany transactions (loans, management fees, shared costs) exceed NPR 1 crore annually, or when a financing institution asks for consolidated group financials for the first time. Starting before that pressure point is better - setting up unified group management for two entities is easier than retrofitting it onto five entities with years of untracked intercompany transactions. The transition cost increases with the number of entities and the age of unreconciled intercompany accounts.
Multi-Entity Group Management with Automated Consolidation and Mobile Group Dashboard
MISAC's multi-company architecture supports unlimited entities under one tenant, each with fully isolated data, its own chart of accounts, its own VAT and TDS registers, and its own user access scope. The group owner or CFO configures a group-level dashboard that pulls key metrics from all entities simultaneously: group cash position across all banks, total group receivables and payables, group revenue and expense summary for the current period. This view is available on the MISAC mobile app - the owner traveling between Kathmandu and Pokhara checks the group position the same way they check messages, without calling anyone or logging into four systems.
MISAC's Custom Financial Statement Grouping allows the group finance team to define a consolidated statement layout that maps each entity's accounts to the appropriate group-level line. The consolidation engine runs automatically, pulling live posted data from all entities, applying the configured intercompany elimination rules, and producing the group-level P&L and balance sheet without manual Excel work. The same Accounting-First architecture that ensures every subsidiary transaction posts a complete double-entry journal also ensures that every intercompany transaction is trackable for elimination purposes - because the data integrity starts at the individual voucher level.
MISAC Intelligence Pvt. Ltd. works with Nepal family business groups and holding company structures across trading, construction, hospitality, and real estate. We have seen the full range of group management challenges: from two-entity groups that need a simple combined view to five-entity groups with complex intercompany loan structures that require formal consolidation. Contact us at mis.ac to discuss your specific group structure and how MISAC handles it.
Ready to See MISAC in Action?
Manage all your Nepal group companies from one platform - real-time consolidated view, mobile dashboard, and automatic intercompany elimination.