We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Explainer3 min readPublished

Why foreign exchange translation differences don't reconcile cleanly

A forex translation gap almost always comes from mixing rates that were never meant to be mixed — a transaction-date rate here, a closing rate there, an average rate somewhere else — applied inconsistently across the same balance.

Foreign exchange translation differences fail to reconcile because Ind AS 21 actually requires three different exchange rates for three different purposes — the transaction-date rate for the original entry, the closing rate for monetary items at the reporting date, and sometimes an average rate for P&L items — and when any of these gets substituted for another, or applied to the wrong category of item, the resulting gain or loss figure won't tie back cleanly even though every individual rate used was, on its own, a correct published rate for that date.

Where the mixing actually happens

  • Non-monetary items (like a foreign-currency advance for a fixed asset) get re-translated at the closing rate like a monetary item would, when they should stay at the historical rate.
  • A monthly average rate is used for the full year's revenue translation while actual transactions occurred unevenly across months, creating a gap against transaction-level detail.
  • A forward contract or hedge is marked at its own contracted rate while the underlying exposure is separately re-translated at the closing rate, and the two aren't reconciled against each other.
  • Different ERP modules (treasury, AP, the general ledger) pull exchange rate feeds from different sources or at different times of day, so the "closing rate" used isn't actually identical across all balances being translated.
  • A balance that should have been settled and realized during the year is still carried and re-translated as if unsettled, because the settlement entry used a different rate and didn't fully clear the original translated balance.

Checking only whether the net forex gain/loss figure looks reasonable relative to the rupee's movement during the year can pass even when several individual mismatches are offsetting each other inside that number. A reconciling net figure is not evidence that every balance was translated at the right rate — only tracing specific balances back to the rate actually applied confirms that.

What actually resolves it

Separating monetary from non-monetary foreign-currency balances explicitly, and tracing a sample of each back to the specific rate used against the rate that should have applied for that category, is what finds the mismatch — not re-checking the arithmetic on a net translation figure that was never going to reveal which underlying rate was wrong.

This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.

Related resources

Free tools, no signup

Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.