Most Nepali business groups grow organically - a trading company expands into construction, an import business spins off a logistics arm, a family patriarch registers separate entities for tax efficiency or liability segregation. Within a few years, the group is routinely moving money, goods, and services between its own companies. The trading subsidiary purchases materials in bulk and transfers them to the construction arm at cost. The parent entity funds a working capital gap for the import company. A shared services arrangement means the parent charges management fees to every subsidiary. Each of these is an intercompany transaction, and each one creates a matching accounting entry in two sets of books simultaneously.
The challenge for the CFO or group accountant is not recording these transactions - it is recording them consistently in both entities, reconciling them at period-end, and then eliminating them entirely when preparing group financial statements. IRD takes a close interest in related party transactions, particularly loans between group companies and management fee arrangements, because these are common vehicles for shifting taxable income. Clean, documented, symmetrical intercompany accounting is the first line of defence in any tax assessment.
This article walks through the accounting mechanics of intercompany transactions in the context of a Nepali family business group - the double-entry in each entity, reconciliation procedures, and the elimination entries required for consolidated reporting. The principles apply whether you are managing two companies or twelve.
What Intercompany Transactions Are and Why They Create Complexity
An intercompany transaction is any transfer of value - cash, goods, services, or an asset - between two entities that share common ownership or control. Under NAS 24 (Related Party Disclosures), Nepali entities are required to disclose material related party transactions in their financial statements, including the nature of the relationship, the value, and any outstanding balances. This is not a disclosure that many CFOs in Nepal take seriously until IRD raises it in an assessment, which is a mistake.
The complexity arises from a structural problem: the same transaction appears as a debit in one entity's books and a credit in another's, but these two sets of books are maintained independently, often by different accounting teams using different software. A loan from the parent to a subsidiary is a debit to "Loan to Subsidiary" in the parent's books and a credit to "Loan from Parent" in the subsidiary's books. If the parent records NPR 50 lakh but the subsidiary records NPR 48 lakh because someone forgot to include the processing fee, you have a reconciling difference that will surface awkwardly during consolidation or, worse, during an audit. Multiply this across a year of intercompany activity and you have a reconciliation problem that can take weeks to untangle.
The deeper issue is that intercompany profit is not real profit from a group perspective. If the trading company sells goods to the construction subsidiary at a 15% markup, the trading company records a gain and the construction subsidiary records a cost. At the group level, neither the gain nor the cost exists - the goods were simply moved internally. Consolidation requires eliminating these intercompany profits and restating the inventory at original cost. Groups that do not track intercompany transactions systematically cannot produce reliable consolidated statements, and in Nepal, consolidated group reporting is increasingly expected by banks for credit facilities and by institutional investors for equity participation.
Intercompany transactions create mirrored entries across two independent ledgers. Asymmetry in recording - different amounts, different dates, different narrations - is the root cause of reconciliation failures at period-end. The discipline required is treating intercompany accounting with the same rigour as third-party accounting, because IRD will.
Common Intercompany Scenarios in Nepali Business Groups
Consider a representative Nepali family group with three entities: Sharma Trading Pvt. Ltd. (the parent, handling import and wholesale), Sharma Construction Pvt. Ltd. (a subsidiary, handling infrastructure projects), and Sharma Imports Pvt. Ltd. (an associate, handling L/C-based procurement). This structure is common across Kathmandu valley business families. The intercompany activity between these three entities typically includes four recurring transaction types.
The first and most common is intercompany loans. The trading company, which collects receivables faster, frequently lends working capital to the construction subsidiary whose project payment cycles are 90 to 120 days. The second is intercompany purchases - the trading company procures materials in bulk at better prices and transfers them to the construction entity at cost or at a small markup to cover logistics. The third is shared service charges - the parent entity employs a common finance team, IT infrastructure, and senior management that serve all three companies, and it charges management fees to the subsidiaries on an agreed basis. The fourth is intercompany asset transfers - the parent purchases a vehicle or equipment and transfers it to a subsidiary for operational use, sometimes with a formal lease arrangement, sometimes informally.
IRD applies heightened scrutiny to three types of intercompany transactions in Nepali group structures. First, loans between related parties where no interest is charged or interest is charged below the bank lending rate - IRD may impute a market rate of interest as deemed income in the lender's hands. Second, management fees charged by a parent to subsidiaries that appear to exceed the actual cost of services provided - these are treated as income shifting if they cannot be substantiated with service agreements and cost allocation schedules. Third, intercompany sale of goods at prices materially different from arm's length - particularly where the transferring entity is tax-profitable and the receiving entity is loss-making. Under Nepal's Income Tax Act 2058, the IRD has authority to restate related party transactions at arm's length value for tax assessment purposes. Maintain service agreements, intercompany loan agreements with market-rate interest clauses, and transfer pricing documentation as contemporaneous records - not as afterthoughts prepared after a notice arrives.
For CFO-level readers, the management fee and shared service arrangement deserves specific attention. Many Nepali groups allocate shared costs informally - the parent simply charges a round figure to subsidiaries without a documented basis. This creates two problems: the subsidiaries cannot substantiate the deduction if questioned, and the parent cannot demonstrate the charge is not a profit shift. The correct approach is a formal cost-plus service agreement signed between the entities, with an allocation key tied to an objective driver - headcount, revenue, or floor space - reviewed annually. We have seen this gap exposed repeatedly during bank credit assessments, where a relationship manager asks for the intercompany service agreement and one simply does not exist.
Every intercompany transaction type in a Nepali group - loans, purchases, management fees, asset transfers - needs a supporting agreement that documents the commercial basis, the pricing methodology, and the settlement terms. Informal arrangements that lack paperwork are the first target in any IRD assessment of a business group.
Automated Intercompany Posting - The Double-Entry in Both Entities
The accounting mechanics of an intercompany loan are worth walking through precisely, because this is where groups most often diverge across their books. Take the specific scenario from the brief: Sharma Trading Pvt. Ltd. lends NPR 50,00,000 (fifty lakh) to Sharma Construction Pvt. Ltd. on Baisakh 1 to cover a project payment obligation. The loan is documented by a promissory note at 10% per annum interest, aligned with prevailing bank lending rates.
In Sharma Trading's books, the entry on disbursement date is: Debit "Loan to Sharma Construction - Intercompany" NPR 50,00,000 and Credit "Bank Account" NPR 50,00,000. This creates a receivable in the trading company's balance sheet. In Sharma Construction's books, the mirror entry is: Debit "Bank Account" NPR 50,00,000 and Credit "Loan from Sharma Trading - Intercompany" NPR 50,00,000. This creates a payable in the construction subsidiary's balance sheet. The narrations in both entries must reference the same transaction - the same date, the same reference number, and the same loan agreement. When you reconcile intercompany balances at Ashadh 31, these two accounts should net to zero from a group perspective: one entity's receivable exactly offsets the other's payable.
Interest accrual on intercompany loans requires matching entries in both books at each period-end. At Ashadh 31, Sharma Trading accrues interest income: Debit "Accrued Interest Receivable" NPR 4,16,667 (NPR 50 lakh at 10% for 10 months, Baisakh through Ashadh) and Credit "Intercompany Interest Income" NPR 4,16,667. Sharma Construction records the matching expense: Debit "Intercompany Interest Expense" NPR 4,16,667 and Credit "Accrued Interest Payable" NPR 4,16,667. Both the interest income in Trading and the interest expense in Construction are eliminated during group consolidation. TDS at the applicable Section 88 rate applies to interest payments made between related entities - confirm the current rate with the applicable TDS heading in the IRD TDS schedule. The TDS is a real cash flow between the entities even though the interest itself is eliminated in consolidation.
For intercompany goods transfers, the entry structure is similar but the elimination at consolidation must also remove any unrealised profit. If Sharma Trading sells goods to Sharma Construction at cost plus 15%, and some of those goods remain in Construction's inventory at year-end, the 15% markup on the unsold portion represents unrealised intercompany profit that must be eliminated from the group's consolidated inventory balance. This is not a theoretical exercise - it directly affects the group's consolidated gross margin and the carrying value of inventory on the consolidated balance sheet. Groups using traditional accounting software typically manage this adjustment in a year-end Excel model, which introduces the risk of formula error and version control issues. The correct approach is an ERP that tracks intercompany transfer prices separately from third-party purchase costs and flags the inventory balance requiring elimination at period-end.
Every intercompany transaction has a debit in one entity's books and a matching credit in another's. These must be recorded on the same date, for the same amount, with the same reference. Any difference is a reconciling item that will surface at consolidation. Automated intercompany posting - where one transaction creates matching entries in both books simultaneously - eliminates the timing and amount discrepancies that manual processes inevitably produce.
Intercompany Reconciliation and Consolidation Elimination
Intercompany reconciliation is the process of confirming that every intercompany receivable in one entity's books has an exactly matching intercompany payable in the counterpart entity's books. This should be done monthly for high-volume groups - not just at Ashadh 31. A difference that sits undetected for eleven months is far harder to investigate and correct than one caught within thirty days of the transaction.
The reconciliation process requires extracting the intercompany account balances from each entity and matching them line by line. For the Sharma group, this means running the "Loan to Sharma Construction" ledger from Trading's books alongside the "Loan from Sharma Trading" ledger from Construction's books, reconciling every disbursement, every principal repayment, and every interest accrual. Common sources of difference include: one entity recording the transaction on the date of bank transfer and the counterpart recording on the date the cheque was issued; TDS deducted at source being recorded only in the paying entity's books but not grossed up in the receiving entity's; and management fees charged by the parent but not yet accepted and booked by the subsidiary's accounts team.
Consolidation elimination is the final step, performed when preparing group financial statements. Under standard consolidation procedures, every intercompany balance - receivable against payable, intercompany revenue against intercompany cost, intercompany interest income against intercompany interest expense - is eliminated in full. The consolidated balance sheet shows the group's position with external parties only. The consolidated P&L shows revenue earned from external customers only. In the Sharma group context, the NPR 50 lakh loan disappears from both the consolidated balance sheet's assets and liabilities; the NPR 4,16,667 interest income in Trading's standalone accounts disappears against the matching interest expense in Construction's standalone accounts. The group consolidated statement looks as if the loan never existed between external parties - because from the group's economic perspective, it did not.
Consolidation elimination is only as accurate as the underlying intercompany reconciliation. Groups that skip monthly reconciliation and attempt a year-end elimination often discover the intercompany accounts do not balance - leaving an unexplained difference in the consolidated balance sheet that requires audit adjustment. Monthly intercompany reconciliation is not administrative overhead; it is the foundation of a credible group consolidated statement.
Frequently Asked Questions
IRD does not mandate a specific interest rate on intercompany loans, but it has authority under the Income Tax Act 2058 to recharacterise below-market loans as deemed income in the hands of the lender. In practice, this means if a parent company lends to a subsidiary at zero interest while the parent itself borrows from a bank at 12%, IRD may assess the parent on the interest income it should have received. The safest practice is to charge interest at the prevailing bank lending rate and document the arrangement with a formal intercompany loan agreement. This also provides the subsidiary with a deductible interest expense, provided the borrowing is used for income-generating purposes and the withholding tax obligations are met.
An intercompany elimination entry removes the effect of transactions between entities within the same group when preparing consolidated financial statements. It is required whenever a group presents accounts that combine two or more entities - to prevent double-counting of assets, liabilities, revenues, and costs that exist only within the group and not with external parties. Common eliminations include: removing intercompany loan receivables against the matching payables; removing intercompany sales revenue against the matching purchase cost; removing intercompany interest income against interest expense; and restating intercompany inventory transfers at the original cost to the group. Eliminations do not affect the standalone accounts of individual entities - they apply only at the consolidated level.
A management fee arrangement between related entities should be supported by a written intercompany service agreement specifying the services covered, the basis for the charge (cost-plus, fixed fee, or revenue-linked allocation), and the payment terms. The allocation key should be objective and consistently applied - common choices include headcount ratio, revenue ratio, or floor space ratio. The parent entity should maintain a schedule of actual costs incurred for the shared services being charged, updated each period, so that the fee can be demonstrated to be cost-reflective and not inflated. TDS applies to management fee payments at the applicable rate under Section 88 of the Income Tax Act 2058 - confirm the current rate with the TDS heading schedule. The receiving subsidiary should book the fee as an expense on the same basis as the parent records it as income.
Multi-Entity Accounting Built for Nepali Business Groups
MISAC is built accounting-first, which means every transaction across every module generates complete, auditable double-entry journal entries automatically. In a multi-entity environment, this architecture extends to intercompany transactions: when a loan disbursement is recorded in the parent entity, the matching liability entry in the subsidiary's books is generated in the same operation. There is no manual re-entry, no timing difference, and no risk of the two sides of the transaction diverging. The same principle applies to intercompany goods transfers, management fee charges, and asset movements - one transaction, two complete journal postings, same reference number in both sets of books. This is what intercompany reconciliation at Ashadh 31 should look like: two ledgers that agree to the cent without a spreadsheet correction in sight.
For group reporting, MISAC's custom financial statement grouping gives CFOs and group accountants the ability to configure consolidation eliminations directly inside the reporting engine. Intercompany account codes are tagged as elimination accounts; when the consolidated report is run, MISAC nets these balances automatically - intercompany receivables against payables, intercompany revenue against cost, intercompany interest income against expense. The result is a consolidated P&L and Balance Sheet that reflects the group's position with external parties only, produced at any date without an annual Excel exercise. Multiple statement formats can run from the same data - one layout for management, one for the bank's credit committee, one for statutory audit - without duplicating data or exporting to Excel.
For business groups navigating IRD scrutiny on related party transactions, clean intercompany accounting is not optional. MISAC Intelligence Pvt. Ltd. has built these capabilities specifically for the Nepali group company context - the multi-entity architecture, the BS calendar support, the IRD-format reporting, and the audit trail that gives every intercompany entry a verifiable chain of approval. If your group is managing intercompany transactions manually across separate accounting systems today, the reconciliation and consolidation work you are doing at year-end is a symptom worth addressing at the system level.
Ready to See MISAC in Action?
If your group manages intercompany loans, shared purchases, or management fee arrangements across related entities, speak with the MISAC team to see how automated intercompany posting and consolidation reporting works in practice.