Translation is where the group view either holds or doesn't
Every Australian-headed group with PRC operations performs three FX-related steps every reporting period:
- Remeasurement at the entity level. Foreign-currency monetary items in the entity's books are remeasured to the entity's functional currency at the closing rate (typically CNY for a PRC operating subsidiary, HKD for a Hong Kong holding entity). Non-monetary items stay at historical rate. This is HKAS / IAS 21 / AASB 121 mechanics, applied entity by entity.
- Translation to the group's presentation currency. The entity's functional-currency financial statements are translated into AUD for inclusion in the group: assets and liabilities at closing rate, income and expenses at average rate, equity at historical rate, with the residual posted to the foreign currency translation reserve (FCTR).
- Reconciliation to prior period FCTR. The movement in the FCTR is explained from the prior period to the current period.
Each step is mechanically simple. The interactions between them, across two reporting calendars and three frameworks, is where the friction lives.
The four timing choices that compound
1. Functional currency determination
The functional currency of a PRC operating subsidiary is almost always CNY, but it is not automatic. AASB 121 / IAS 21 requires a judgement based on the primary economic environment, the currency of sales and costs, the currency of financing, and the currency in which receipts are retained.
For PRC entities funded by an AUD or USD intercompany loan, with sales priced in CNY but a parent that retains decision authority and treasury control, the determination requires evidence. Where this judgement was never documented, every subsequent translation rests on an untested assumption.
If you are unsure how this FX remeasurement timing is currently impacting your group close, you can run a 2-minute diagnostic via our Close Clash Calculator to see where the evidence path is breaking down.
2. Closing rate selection
The "closing rate" sounds like a single number. In practice, groups have to choose:
- Whether to use the official PBOC central parity rate, an interbank rate, or a published rate from a financial data provider
- Which time of day the rate is taken
- Whether the same source is used for all entities and all periods
- Whether to use the last business day of the period or a rolling end-of-day rate
Different choices produce materially different translated balances over time. Auditors expect one documented policy, applied consistently.
3. Average rate selection
For income and expense translation, AASB 121 permits rates that approximate the actual rate at the date of the transaction. In practice, most groups use a monthly or daily average. The choice affects:
- How translation of revenue and expenses ties to translated working capital
- How interim period averages roll into year-end averages (a quarterly average is not the average of three monthly averages)
- How comparability holds when rates move sharply within a period
Where the policy is not documented, each cycle's choice is implicitly the one inherited from last cycle, which is not an audit-defensible position.
4. Cut-date alignment
This is the structural one. The China entity closes on a different rhythm than the Australian parent. If the entity-level remeasurement is performed at the PRC statutory cut (31 December) but the group cut is 30 June, the translation has to bridge a six-month gap during which the entity may have continued posting against the closed period.
The sequence has to be: freeze the entity TB at the group cut date (30 June or 31 December), apply remeasurement in the entity's functional currency at that date, then translate to the presentation currency. Doing the steps in the wrong order produces residuals that cannot be reconciled to anything.
The patterns we see when timing is uncontrolled
When FX timing is left to local convention rather than group policy, the symptoms are predictable:
- The FCTR movement cannot be explained line by line; it is reconciled "in total" with a balancing figure
- Intercompany loan revaluation sits on one side of the loan but not the other
- Half-year translation differences disappear into year-end without trace
- Auditors expand their FX testing because they cannot rely on a process control
- Board commentary on FX impact becomes assertion rather than analysis
Each of those is an audit problem that started as a policy problem.
The policy structure that holds
The minimum structure to keep translation explainable:
- A documented FX policy, owned by group finance, refreshed annually. It states: functional currency per entity (with rationale), rate sources (closing and average), cut-date discipline, and treatment of intercompany monetary items.
- A standing FX translation pack template for each entity, covering closing rate, average rate, opening equity at historical, current period translation, and the FCTR movement.
- Intercompany loan revaluation booked as a named entry on both sides of the relationship, with the FX gain or loss eliminated where appropriate at consolidation.
- An FCTR continuity schedule, refreshed each period, showing opening balance, current period translation differences by entity, and closing balance — sufficient for an auditor to tie movement to source.
When that structure is in place, FX stops being a residual category in the consolidation and becomes a controlled, audit-defensible part of the group's reporting.