Multi-currency consolidation: where the FX errors hide

Multi-currency consolidation in Indian groups follows Ind-AS 21, The Effects of Changes in Foreign Exchange Rates. The standard is well-written, the consolidation tools (SAP, NetSuite, Oracle Hyperion at the larger end; Tally Prime Server with manual overlays at the smaller end) handle the mechanics, and most finance teams treat consolidation as a once-a-quarter task that the system runs and the controller reviews.

What audit findings consistently show is that the system runs the mechanics correctly, the controller reviews the output, and four specific errors hide in plain sight because the review is at the consolidated level, not at the transaction level. We have audited and remediated multi-currency consolidations for groups with operations across Singapore, the United States, the United Kingdom, the UAE, and Mauritius, and the same four patterns recur.

The Ind-AS 21 framework

First, the framework. Three steps.

Functional currency determination. Each entity in the group operates in its functional currency — the currency of the primary economic environment in which the entity operates. For an Indian subsidiary of a Singapore parent that sells in USD and pays employees in INR, the functional currency is often INR despite the USD revenue. The functional-currency determination drives everything else.

Monetary vs non-monetary items. At each balance-sheet date, monetary items (cash, receivables, payables, debt) are translated at the closing rate. Non-monetary items (inventory, fixed assets, prepayments) are not retranslated if they are carried at historical cost; they retain the rate at which they were originally recognised.

P&L translation. P&L items are translated at the rate prevailing on the transaction date, or for practical reasons at the average rate for the period. Most groups use monthly average rates because daily-rate translation is operationally heavy.

Translation reserve. The differences from translating the opening net assets at the closing rate, and from translating P&L at average rates while balance-sheet items are at closing rates, accumulate in the foreign currency translation reserve (CTA) in other equity (OCI).

Where the FX errors hide

Four locations, in roughly the order we find them.

1. Revenue translation gain or loss not segregated from operational FX

A revenue invoice booked at the rate prevailing on the invoice date, paid by the customer 45 days later at a different rate, creates an FX gain or loss that is operational in nature (the customer paid, the rate moved). This gain or loss is correctly classified as 'other income' or 'finance cost' under the operational FX line, not as part of revenue.

The error: the consolidation system applies the closing-rate translation to the AR balance at quarter-end, generating an unrealised translation FX. The system then classifies this unrealised FX in the same line as the realised operational FX from settled invoices. The result is a mixed line that combines genuine operating FX exposure with translation noise, and the management team cannot separate signal from noise when reviewing the P&L.

The fix: a separate sub-ledger for translation FX (unrealised) and operational FX (realised), with the consolidation system mapped to keep them apart. This is a one-time setup change in the ERP that pays back every quarter.

2. Intercompany loan re-measurement quarterly — netting off in CTA but not reviewed

An Indian parent with a USD loan to a US subsidiary, or a Singapore parent with an INR loan to an Indian subsidiary, has an intercompany monetary item that gets retranslated at each balance-sheet date. The translation movement on the loan creates an FX in the lender's books and an offsetting FX in the borrower's books. On consolidation, the two largely cancel out in the translation reserve.

The cancellation is intended by Ind-AS 21 when the loan is, in substance, a long-term investment that forms part of the net investment in the foreign operation. The cancellation is wrong when the loan is a genuine debt instrument with defined repayment terms and the loan is not part of the net investment.

The audit finding: groups treat all intercompany loans as 'net investment' loans by default, eliminate the FX in CTA, and never review the substance. When an external lender or a tax authority looks at the same loan, they ask: does this loan have repayment terms? Is it interest-bearing? Has there been actual repayment? If the answers point to a genuine debt instrument, the FX should hit the P&L, not the CTA, and the group has been understating P&L FX volatility for years.

3. Hedge accounting documentation missing for forward contracts

Indian groups with USD or EUR revenue often hedge through forward contracts with their bank, locking in a future rate for an expected receipt. Under Ind-AS 109, hedge accounting is permitted only if the hedge relationship is documented at inception with: the type of hedge, the hedged item, the hedging instrument, the risk being hedged, the hedge effectiveness methodology.

Most finance teams know this. What they miss is the documentation discipline. The treasury team books the forward, sends a note to finance, and finance applies hedge accounting in the books. The Ind-AS 109 documentation — the formal designation memo, the effectiveness testing methodology, the periodic effectiveness retesting — exists in spirit but not in the file.

When the auditor asks for the documentation, the finance team produces an after-the-fact memo. The audit conclusion: hedge accounting cannot be applied retrospectively. The FX gains and losses on the forwards must be re-routed from OCI back to the P&L for the affected periods. The restatement is uncomfortable.

The fix is process, not policy. Every forward contract gets a one-page designation memo signed within 5 working days of booking, with the effectiveness methodology defined and the hedge relationship documented before the next reporting date.

4. Capex from overseas suppliers — date of recognition wrong

A piece of equipment imported from Germany, ordered in March, shipped in April, landed in India in May, capitalised in June. The exchange rate at each of those dates is different. Under Ind-AS 21, a non-monetary item should be recorded at the rate prevailing on the date of the transaction — which, for the imported asset, is the date the asset becomes available for use, or in some interpretations the date of import customs clearance.

The common error: the finance team uses the rate on the date of the supplier invoice (March) or the date the customs duty is paid (May) inconsistently across import transactions. The result is a fixed-asset register where similar imports during the same quarter are recorded at materially different rates, and the depreciation expense for the subsequent quarters reflects these inconsistencies.

The fix: a written policy on the date used for foreign-currency capex recognition (we recommend bill-of-entry date for imports, which aligns with customs clearance and is documented in the import documentation), applied consistently across every import, with quarterly review by the controller.

What good consolidation hygiene looks like

Three operating disciplines.

Functional currency reviewed annually. As subsidiaries grow, mature, or shift business mix, the functional currency can change. A US subsidiary that started as a sales office for the Indian parent (INR functional) and is now a standalone P&L with USD revenue and USD payroll has likely shifted to USD functional. The review needs to happen annually and the change, if any, needs to be applied prospectively under Ind-AS 21.

Quarterly intercompany substance test. Every intercompany monetary item — loans, payables, receivables — gets a quarterly review against substance. Is this in essence a long-term net investment, or is it a debt instrument with repayment terms? The classification drives the FX treatment.

Forward contract calendar. Every open forward contract tracked against its hedged item, with monthly effectiveness testing where required, documented in a central register. Bank confirmations matched against the register at each quarter-end.

Consolidation is not a system output. It is an accounting position that the system supports. Treating it as the latter, and documenting it accordingly, prevents the four errors above. Treating it as the former is how those errors hide for years.