When the bank asks a Nepal business group for consolidated financial statements to assess a NPR 5 crore term loan application, the group CFO starts what becomes a three-to-four day exercise. Export Company A's trial balance. Export Company B's. Export Company C's. Paste all three into a master Excel sheet. Map each entity's account codes to a common group structure. Identify every intercompany transaction - the loans, the management fees, the shared asset allocations. Calculate the elimination entries. Build the consolidated P&L, balance sheet, and cash flow line by line. Format everything to look like a proper financial statement. Have it reviewed by the CA. Correct the errors. Three days minimum, four if anything needs chasing.
This three-day process happens because the three companies run their accounting on separate systems with no shared data infrastructure. Each produces its own trial balance; the consolidation is manual work performed on exports. The result is accurate enough for the bank submission, but it is always historical by the time it is done, it is not reproducible mid-month for management purposes, and it is entirely dependent on the one person who knows how to do the Excel consolidation model.
Consolidated financial reporting in an ERP automates this process. All entities post to a common platform. The consolidation engine pulls from that common data, applies the elimination rules, and produces the group-level P&L and balance sheet in minutes. The same report can be run monthly for management review, quarterly for banking covenants, and annually for the statutory accounts - with consistent methodology every time.
What a Consolidated Financial Statement Actually Shows
A consolidated financial statement presents the group of companies as if they were a single economic entity. All external revenues are combined; all external expenses are combined; all external assets and liabilities are combined. Transactions between group entities - intercompany loans, management fees, cross-entity sales, shared cost allocations - are eliminated because from the group's external perspective, those transactions never occurred. Money moved between pockets of the same group is not a group-level transaction.
The consolidated P&L therefore shows: total revenue from sales to external customers across all entities (the management fee from Entity A to Entity B disappears); total expenses paid to external vendors across all entities (the interest expense at Entity B that matches the interest income at Entity A both disappear); and the net profit that belongs to the group's shareholders after eliminating all internal activity. The consolidated balance sheet shows: total assets held by the group (external receivables, inventory, fixed assets - the intercompany receivables and payables cancel each other); total liabilities owed to external parties (external bank loans, external payables - the intercompany balances cancel); and shareholders' equity representing the group's net worth.
Nepal Rastra Bank (NRB) requires financial institutions under its regulatory oversight - commercial banks, development banks, and finance companies - to produce consolidated financial statements where they have subsidiaries. For NRB-regulated groups, the consolidation methodology and subsidiary inclusion rules are specified in NRB directives. For non-regulated Nepal business groups, the Company Act 2063 and Nepal Accounting Standards (NAS) provide the framework. NAS has progressively converged with NFRS (Nepal Financial Reporting Standards), which closely follows IFRS. Groups seeking external financing from development banks like NDB or ADB may be required to produce NFRS-compliant consolidated statements - confirm the standard required by your specific lender or regulator before beginning the consolidation process.
Minority interests add another layer of complexity when the group does not own 100% of every subsidiary. If the holding company owns 70% of a subsidiary, the remaining 30% is the minority interest. The consolidated balance sheet includes 100% of the subsidiary's assets and liabilities but shows the 30% minority interest as a separate component of equity. The consolidated P&L shows 100% of the subsidiary's revenue and expenses but allocates the minority's share of profit separately. For Nepal groups where all entities are fully owned by the same family, minority interest may not apply - but for groups with external minority shareholders in any entity, the calculation is mandatory.
Consolidated financial statements show the group's genuine economic position, stripped of all internal transactions. A group with high intercompany activity - loans, fees, cross-entity services - may look very different in the consolidated view compared to the sum of individual entity statements. The consolidated view is what banks, investors, and regulators actually care about. Producing it accurately and consistently should be an ERP function, not a periodic Excel project.
The Consolidation Process - Step by Step
Whether manual or automated, consolidation follows the same sequence. Understanding the steps clarifies what the ERP automates and what still requires judgment.
Step 1 - Agree entity trial balances: confirm that each entity's accounts are complete and correct as of the consolidation date. In an ERP, this means confirming that all transactions for the period have been posted in all entities before running the consolidation. Step 2 - Map entity accounts to group accounts: convert each entity's individual account codes to the common group reporting structure. This mapping is configured once and applied automatically in subsequent consolidation runs. Step 3 - Eliminate intercompany balances: identify all receivables, payables, income, and expense items that relate to intercompany transactions and remove them from the consolidated totals. Step 4 - Eliminate intercompany unrealized profit: if one group entity sold inventory to another entity and that inventory is still on hand, the profit on the internal sale is unrealized from the group's perspective and must be eliminated. Step 5 - Calculate minority interests (where applicable). Step 6 - Produce the consolidated P&L, balance sheet, and cash flow statement.
An ERP consolidation engine automates Steps 2 through 6 completely, given that the account mapping and intercompany elimination rules are correctly configured. Step 1 - ensuring all entity data is complete - remains a human process. The consolidation should only be run after the group finance team has confirmed that all entities have completed their period entries. Running it on incomplete data produces a consolidated statement that is numerically consistent but factually wrong.
ERP consolidation automation does not remove the need for period-close discipline in each entity. Garbage in, garbage out applies to consolidated reporting as much as to any other accounting output. The ERP can automate the assembly of the consolidated statement in minutes, but only after the individual entity accounts are correct. The effort that used to go into manual consolidation should be redirected to ensuring each entity closes correctly and on time.
Management Consolidated Reports vs. Statutory Consolidated Accounts
Groups typically need two types of consolidated financial outputs: management consolidated reports (monthly, for internal decision-making) and statutory consolidated accounts (annual, for the Company Register and for tax and regulatory purposes). The two outputs use the same underlying data but may use different levels of detail, different formats, and in some cases different accounting treatments for specific items.
Management consolidated reports prioritize timeliness and decision-relevance over technical precision. The monthly group P&L might include management adjustments, accruals that are not yet formally posted, and budget comparison analysis. It is produced quickly, often without a formal audit trail, for the owner and board. Statutory consolidated accounts require technical compliance with NAS or NFRS, full intercompany elimination, minority interest calculation, and disclosure notes. They take longer to prepare and are typically reviewed by the group's external auditors before submission.
ERP consolidation serves both purposes from the same data. The monthly management run uses the live posted data with the standard elimination configuration. The year-end statutory run uses the audited data with any year-end adjustments and the full formal presentation. Using the same platform for both ensures consistency: the management accounts and the statutory accounts should not produce materially different group profit figures unless there are specific adjustments to explain. Where they diverge, the explanation should be documented.
Running monthly management consolidations throughout the year significantly reduces the effort of the annual statutory consolidation. A group that consolidates monthly has twelve months of period-tested elimination entries and a well-understood data structure. A group that consolidates only at year-end faces twelve months of accumulated intercompany differences in one exercise. Monthly consolidation is not more work - it is the same work spread across twelve short sessions rather than one long annual effort.
Frequently Asked Questions
The requirement varies by business type and regulator. NRB-regulated financial institutions with subsidiaries must produce consolidated statements as per NRB directives. Companies listed on the Nepal Stock Exchange (NEPSE) must produce consolidated statements per SEBON requirements. Other large groups may be required to consolidate under the Companies Act 2063 or applicable Nepal Accounting Standards. Smaller family business groups may not have a statutory obligation but find that their lenders and investors require consolidated statements for credit assessment. Confirm the specific requirement with your CA or the relevant regulator for your group's structure and size.
Technically, consolidated statements can be produced for any period for which individual entity accounting records exist. In practice, the further back you go, the more complex the intercompany elimination becomes because you need to reconstruct the history of intercompany balances at each period end. For a bank or investor request that requires three years of consolidated statements, the process involves rebuilding the intercompany reconciliation for each year using the available records. A CA familiar with consolidation accounting can manage this retrospective process. Going forward, running the consolidation monthly or quarterly from the start prevents this reconstruction challenge from arising again.
Multi-branch accounting involves branches within one legal entity (one PAN, one company registration). The branches share the same chart of accounts and general ledger; branch-level reporting is done through cost center filtering. Consolidation involves multiple separate legal entities (separate PAN numbers, separate company registrations, separate financial statements). The consolidation process combines independent ledgers and eliminates intercompany transactions. The distinction matters because multi-branch does not require intercompany elimination (there are no separate legal entities creating genuine intercompany transactions), while group consolidation does. The right approach depends on how your business is legally structured, not just how it is operationally structured.
Automated Consolidation Engine with Custom Statement Grouping and Elimination Rules
MISAC's Custom Financial Statement Grouping allows the group finance team to define the consolidated statement structure: which group-level line items consolidate which entity accounts, how minority interest is calculated and presented, and which intercompany flags trigger elimination. Once configured, the consolidation engine applies these rules automatically every time the consolidated report is run. The group P&L and balance sheet that previously took three days now runs in fifteen minutes - from the same data, with the same methodology, every time, without depending on one person's Excel model.
The Accounting-First architecture ensures that every transaction posted in any entity is immediately available to the consolidation engine. There is no export-import step, no file format conversion, no reconciliation between the exported data and the live system. The consolidation runs against the posted transaction records directly. Intercompany transactions tagged at entry are tracked through their full life cycle - creation, settlement, and any adjustments - so the elimination journal at consolidation accurately reflects the current position rather than a static point-in-time snapshot from an export file.
MISAC Intelligence Pvt. Ltd. has implemented group consolidation reporting for Nepal companies from two-entity family groups to multi-sector holding structures with five operating entities. The consolidation configuration covers account mapping, intercompany elimination rules, minority interest (where applicable), and the presentation format that matches the group's statutory reporting requirement. The configuration is tested against historical data before go-live, so the first live consolidation run produces a statement that can be reconciled against the manual process. Contact us at mis.ac to design the consolidation architecture for your Nepal group.
Ready to See MISAC in Action?
Cut your Nepal group's consolidation from three days to fifteen minutes with automated intercompany elimination and custom statement grouping.