ZAR + USD + multi-jurisdiction: getting FX right in Sage Intacct

Foreign exchange treatment is one of those areas where small implementation choices in Sage Intacct have outsized reporting consequences a year later. We see two failure modes regularly: groups that under-configure FX (and end up with unexplained variances on consolidation) and groups that over-configure it (and end up running daily revaluations on a mid-market business that doesn't need them).

This is the configuration playbook we'd use for a typical South African group operating across ZAR, USD, GBP, and the SADC currencies.

Rate sources — pick one, document it

Sage Intacct ships with a built-in currency rate feed. You can also connect a custom feed (Reuters, Bloomberg, central bank rates) or enter rates manually. For most SA mid-market groups, the built-in feed is appropriate; it pulls daily rates from a recognised source, and the rates have a documented methodology your auditor can verify.

What we ask in Discover: which entities trade in which currencies, how often, and what rates does your auditor expect to see? For trading entities, daily rates on transactions are standard. For consolidation, monthly average and period-end spot are the IFRS-aligned defaults.

FX revaluation — monthly minimum

Sage Intacct can revalue foreign-currency-denominated monetary items on any schedule. The trade-off is between accuracy and operational overhead. Our default for mid-market SA groups is monthly revaluation: the system marks open AR, AP, and bank balances to month-end spot rate, posts the unrealised gain or loss to the P&L, and creates a reversing journal at month-start.

Daily revaluation is appropriate for groups with high transaction volumes in volatile currencies; quarterly is rarely sufficient for IFRS compliance.

Transaction gains/losses vs translation adjustments

This is the IFRS distinction that catches finance teams out. Transaction gains/losses arise from settling or revaluing foreign-currency monetary items — they go to P&L (IAS 21). Translation adjustments arise from consolidating the financial statements of a foreign operation — they go to other comprehensive income / equity (also IAS 21, but a different paragraph).

Sage Intacct handles both correctly out of the box, provided you have configured the consolidation engine and the FX revaluation rules. The mistake we sometimes see is consolidation differences ending up in P&L — that is a configuration issue, not a software limitation.

Currency translation adjustment (CTA) on consolidation

When a foreign sub's financials are translated into the group reporting currency, the difference between (a) the rates used for the income statement (typically monthly average) and (b) the rates used for the balance sheet (typically period-end spot) creates a CTA. IFRS requires this to be parked in equity, not run through profit.

Sage Intacct posts CTA to a dedicated equity account on every consolidation run. The auditor sees it, can trace it to its components, and reconciles to the FX rates used.

Where SADC adds nuance

For SADC currencies (ZMW, MWK, ZWG, AOA, MZN) that occasionally undergo redenomination or controls, configure the rate source carefully and document any manual overrides. Zimbabwe's currency history is the obvious example, but Angola's and Mozambique's regimes also warrant attention. Sage Intacct can accommodate manual rate overrides with an audit trail — keep that documented.

The IFRS policy memo your auditor will ask for

Before go-live, document: which rate source is used, how often rates are refreshed, the revaluation cadence, the treatment of transaction gains/losses (which account), the treatment of CTA (which equity account), and the handling of monetary versus non-monetary items per IAS 21. Two pages, signed by the CFO, and your year-end is meaningfully easier.