The CFO of a Kathmandu business group opens her laptop on Ashwin 28 and stares at three different accounting files. One is the trading company that imports electronics from Shenzhen. One is the construction arm that bids on municipal projects in Lalitpur. One is the real estate company that owns the warehouse the trading arm rents. Three PANs, three sets of audited accounts, three trial balances. The promoter wants one number by tomorrow morning: how is the group actually doing.
This is the working reality of multi-company accounting software Nepal users keep searching for. Family-owned groups with two, three, or five related companies are not the exception in Nepal. They are the structure. A single promoter family commonly runs a trading licence, a construction firm, an import house, and sometimes a hotel or a school, each as a separately registered Private Limited under the Company Act 2063. Each entity files its own VAT returns and income tax return with the IRD. None of them, on their own, tells you how the group is performing.
The gap between statutory entity accounting and consolidated management reporting is where most Nepali groups lose visibility. The books are clean at the entity level. The promoter sees an Excel summary at Tihar that was last refreshed three months ago. Intercompany loans sit unreconciled. Shared rent and management fees are charged in one direction but not booked in the other. When the auditors arrive, the elimination entries are reconstructed from memory.
The Anatomy of a Nepali Business Group
A typical Nepali business group is not a holding company structure in the textbook sense. It is a horizontal cluster of companies, each owned by the same family or the same set of shareholders in different proportions, operating in adjacent sectors. The trading arm imports and sells. The construction arm bids on projects and uses materials sourced through the trading arm. The real estate company holds the godown that the trading arm uses. The hotel, if there is one, is the lifestyle bet.
Each entity has its own PAN, its own VAT registration where applicable, and its own audited financial statements signed by an ICAN member. Each entity has separate cash flow, separate bank accounts, and separate IRD filings. The intercompany linkages are everywhere though. The construction company owes the trading company for cement. The promoter put personal funds into the real estate company through the trading company. The hotel pays a management fee to one of the other entities for shared back-office staff.
When the promoter asks "how are we doing", the honest answer requires consolidation. Consolidation needs three things working together: clean entity books, identified intercompany balances, and a defined elimination logic. Most Nepali groups have the first. Almost none have the second and third running on a continuous basis.
Nepali business groups are structurally multi-entity, not multi-divisional. Consolidation is not optional - it is the only honest way to answer the promoter's basic question of how the group is performing.
The Intercompany Transaction Problem
Intercompany transactions are the single biggest cause of dirty group books. A loan from the trading company to the construction company is a receivable in one set and a payable in the other. If the amounts do not match - because one side recorded interest and the other did not, or because a repayment was booked in one ledger but missed in the other - the consolidated balance sheet will not balance. Auditors then spend the first two weeks of the audit reconciling something that should have been continuous.
The same issue surfaces with shared services. Head office salaries, group accounting staff, the shared CFO's time - all of these are real costs that one entity bears and the others benefit from. If the management fee is not charged consistently, profitability at the entity level is distorted. Some entities look more profitable than they are and pay higher tax. Others look less profitable and attract IRD attention through consistent losses, which is its own risk under the Income Tax Act 2058.
Each registered company in a Nepali group files its own annual income tax return with the IRD by the statutory deadline tied to Ashadh end. The trading company submits its VAT return monthly or trimester-wise depending on turnover, and TDS is deposited by the 25th of the following month. Consolidated management reports are an internal exercise and have no statutory format - which is exactly why most groups never produce them in a disciplined way.
Transfer pricing rules add another layer. When entities under common control transact with each other, the IRD expects those transactions to happen at arm's length. Selling cement from the trading arm to the construction arm at below market rate to shift profit is the kind of move that survives one year and gets queried the next. Related party transactions need to be documented contemporaneously, priced defensibly, and disclosed in the audited accounts under NAS 24.
Intercompany balances and shared service charges need to be booked symmetrically in both entities and reconciled monthly. The cost of letting these drift is paid at year-end in audit hours and IRD risk.
"The books at each entity can be perfectly clean and the group books still tell you nothing. Consolidation is not a once-a-year exercise. It is the only view that lets the promoter act on what the group is actually earning."
A view we hear repeatedly from CFOs of Nepali business groups
Elimination Entries and the Consolidated View
Consolidation is more than adding three trial balances together. If you simply sum the entity numbers, you double-count every intercompany transaction. The Rs 50 lakh loan from the trading company to the construction company appears as both an asset and a liability inside the group. The cement sold from one arm to the other inflates group revenue and group cost of goods sold by the same amount. None of it reflects what the group has actually transacted with the outside world.
Elimination entries remove these intercompany positions. The standard treatment removes intercompany receivables against intercompany payables, intercompany revenue against intercompany cost, and intercompany dividends against investment income. What remains is a view of the group as if it were a single entity transacting only with external customers, suppliers, and lenders. This is the number the promoter actually needs to make decisions about where to deploy capital next.
For a Nepali group with three to five entities, a clean monthly consolidation typically requires four categories of elimination: intercompany trading (sales and corresponding purchases), intercompany loans and interest, intercompany expense recharges and management fees, and unrealised profit on intercompany inventory still held in stock at the reporting date. Building this once as a structured report - not a fresh Excel each month - is what separates groups with real visibility from groups operating on instinct.
The other dimension that matters in a group context is segment reporting. Even after consolidation, the promoter wants to know how the trading segment is doing versus construction versus real estate. The same chart of accounts cannot answer both questions unless every transaction carries a segment tag. Cost centres, business units, or whichever label the system uses, the principle is the same: the accounting structure has to support both entity-level statutory reporting and group-level segment analysis from the same underlying transactions, without parallel books.
Real consolidation is a defined report, not a year-end Excel exercise. Eliminations and segment tags built into the accounting system give the promoter monthly numbers that survive audit scrutiny.
Board and Investor Reporting for Multi-Entity Groups
Once consolidation works, the next problem is the variety of reports the group has to produce. Statutory accounts at the entity level follow Nepal Accounting Standards and Company Act 2063 disclosures. The promoter wants a one-page group dashboard. The bank that lent to the trading arm wants CMA data on that specific entity. The investor or potential partner wants segment profitability and a group-level cash flow. The board wants comparison against last year and against budget. None of these formats are the same.
Most Nepali groups solve this by maintaining multiple parallel Excel files. The accounting software produces an entity trial balance. The Excel files then regroup line items into management format, consolidate, segment-tag, and produce the dashboards. Every refresh is manual. Every formula error is a phone call to the accountant at 9 pm. Every change in chart of accounts breaks last quarter's report.
The cleaner architecture treats the accounting system as the single source. Reports are defined as configurations over the same general ledger. The entity P&L for IRD filing, the management P&L for the board, the segment view by business line, and the consolidated group statement all draw from the same posted vouchers. Change the underlying data and every view updates. Add a new entity to the group and the consolidation logic absorbs it without breaking last year's reports.
Stop maintaining parallel Excel files for different audiences. Define each report as a view over the single ledger. The group can then produce statutory, management, segment, and consolidated reports without rekeying numbers.
Each entity sits on a different desktop. Consolidating means exporting trial balances and stitching them in Excel.
All group entities run on one platform with one login. Each company has fully isolated data and audit trail, but the CFO sees them in one place.
One side records interest, the other does not. Repayments booked on one side are missed on the other. Year-end reconciliation takes weeks.
Counter-entity ledgers are checked on every posting. Mismatched balances surface immediately, not in Ashadh.
The promoter sees the group view months after the period closes. Elimination entries are reconstructed from notes each time.
Group P&L, balance sheet, and segment view refresh from posted vouchers. No export, no rekeying, no version conflicts.
The same data is regrouped manually for the auditor in one format and the board in another. Errors creep in at every refresh.
Statutory format, management format, and bank CMA format are saved as report definitions. Same numbers, different lenses, one click each.
The chart of accounts does not carry segment tags. Splitting overheads between trading, construction, and real estate is done by hand.
Each voucher carries the segment it belongs to. Pivot analysis by business line, branch, or project runs against live data inside the ERP.
Frequently Asked Questions
Yes, and it must. Each registered Private Limited in a Nepali business group remains a separate taxpayer for IRD purposes. Each entity files its own VAT return on the schedule applicable to its turnover and its own annual income tax return after Ashadh closing. The role of a multi-company accounting platform is to keep entity books clean enough for those individual filings while also producing the group view for management. The two layers do not conflict - they sit on the same posted data.
Intercompany loans are valid commercial transactions if they are documented, carry interest at a defensible rate, and are disclosed as related party transactions in the audited accounts under NAS 24. Interest charged is taxable income in the lending entity and deductible in the borrowing entity, subject to TDS provisions where applicable. Interest-free intercompany loans between group companies attract IRD scrutiny and can be challenged under arm's length principles. Verify the current TDS rate on interest payments with the relevant IRD circular before fixing the structure.
Formal consolidated financial statements under NAS are mandatory for entities that meet the parent-subsidiary criteria as defined in the applicable standard, typically driven by control. Many Nepali family groups operate as related entities under common ownership without a formal parent-subsidiary structure, so statutory consolidation may not apply. Even where it is not statutorily required, internal consolidation for management and lender purposes is universally needed. The accounting platform should support both - statutory consolidation where applicable and management consolidation for the group view.
Group Visibility Without Parallel Books
MISAC runs unlimited companies under one tenant with fully isolated data per entity. The CFO of a group switches between the trading company, the construction company, and the real estate company in one click without logging out. Each entity keeps its own chart of accounts, its own VAT and TDS registers in IRD format, and its own Bikram Sambat fiscal year, while the user list, approval chain, and audit trail span the whole group. Adding a new entity to the group is a configuration step, not a separate purchase or a re-implementation.
The Custom Financial Statement Grouping defines reports as configurations over the underlying ledger. The same posted vouchers feed the statutory entity P&L, the management format the board sees, the segment view by business line, and the consolidated group statement with elimination entries applied. Each report is a layout definition, not a separate set of books. When the promoter asks for the group view on a Tuesday morning, it is ready on the dashboard. Pivot reporting then lets the CFO break the group P&L by entity, by segment, by cost centre, or by any custom dimension already on the transaction.
Because the platform is accounting-first, every voucher across every entity auto-posts a complete double-entry journal at the moment it is saved. Intercompany sales generate matching purchase entries in the counter-entity. Stock movements between godowns of different group companies feed both inventory and accounting. Bank statement imports reconcile line by line for each entity. The result is that the group books stay continuously close-able, audit-ready, and consolidation-ready instead of being reconstructed at Ashadh end. MISAC Intelligence Pvt. Ltd. has built this with Nepali business groups in mind - the kind of family-owned clusters where the same CFO sits across the trading, construction, and real estate arms and needs one platform to see them all clearly.
Ready to See MISAC in Action?
If your group runs two or more companies and the consolidated view still lives in Excel, talk to our team about how a single platform can give you continuous group visibility without disturbing entity-level filings.