Foreign-exchange movements can affect far more than the remeasurement line in a monthly close. They influence the cash needed to pay overseas suppliers, the value of foreign-currency receivables, the translated results of foreign subsidiaries and the economics of cross-border funding. For a US or Canadian group, the controller’s challenge is to connect these exposures to reliable forecasts, approved treasury actions and defensible financial reporting.
A sound FX control framework does not attempt to predict every currency movement. It makes exposures visible, prevents unauthorized dealing, ensures that hedges relate to genuine business risks and records the accounting consequences consistently. The following framework is designed for controllers working with treasury, FP&A, procurement, sales and regional finance teams.
1. Build a complete inventory of currency exposures
Start with a central exposure register rather than relying only on the open-items report from accounts payable and accounts receivable. Include forecast purchases and sales, intercompany balances, foreign-currency debt, cash balances, leases and other contractual cash flows where relevant. Separately identify the net investment in foreign operations when the group manages that exposure.
For each exposure, capture the legal entity, functional currency, transaction currency, amount, expected settlement or recognition date, source system, counterparty and responsible owner. Distinguish recognized monetary balances from forecast transactions and translation exposures; they have different accounting and risk-management characteristics.
Controller example: A Canadian parent buys components in US dollars, sells finished goods in Canadian dollars and has a US subsidiary whose functional currency is the US dollar. The supplier payable, forecast purchase commitments and translation of the subsidiary’s financial statements should not be combined into one undifferentiated “USD exposure.”
2. Confirm functional currency and transaction data
Functional currency is an accounting assessment, not simply the currency selected for a bank account or management report. Controllers should ensure that each entity’s functional currency determination is documented and revisited when facts and circumstances change. Keep transaction currency, local currency, functional currency and group presentation currency clearly distinguished in systems and reporting.
Review customer and supplier master data, contract terms, invoice currency, exchange-rate types and dates, and intercompany agreements. Incorrect currency codes or inconsistent exchange-rate sources can create errors that appear to be market volatility but are actually data-quality failures.
3. Produce a forward-looking exposure forecast
Build a rolling forecast by currency and time bucket—weekly or monthly depending on the volatility and cash-management needs of the business. Reconcile the forecast to the operating plan, purchase orders, sales pipeline, production plan and expected settlement dates. Show both gross inflows and outflows before calculating net exposure so that natural offsets are visible and can be challenged.
Track forecast accuracy by currency, entity and horizon. A forecast that is accurate in total but consistently late or early can still produce the wrong hedge maturity. Record changes to forecast assumptions and identify who approved material overrides.
4. Set a board-approved treasury policy and dealing mandate
The policy should define the purpose of hedging, permitted instruments, eligible counterparties, approved currencies, tenor limits, hedge ratios, exposure thresholds, authorization levels and prohibited activities. It should state whether speculative positions are prohibited and explain how exceptions are approved and reported.
Separate deal initiation, execution, confirmation, settlement and accounting where practical. Users who can create or amend bank beneficiaries should not automatically have authority to execute derivatives. Maintain an approved counterparty list and monitor credit limits and collateral terms.
5. Link every hedge to an underlying business exposure
Before executing a forward, option or swap, treasury should identify the exposure being managed and explain how the instrument reduces the risk. A hedge should not be justified solely by a view that a currency is likely to move. Document the amount, currency, timing, risk being hedged, expected business cash flow and the consequences if the forecast transaction does not occur.
Consider natural offsets first. A US subsidiary with recurring USD receipts and USD supplier payments may have a smaller net cash exposure than the gross amounts suggest. Netting must reflect actual cash-flow timing, legal-entity constraints and the company’s approved risk-management approach; it should not be created only to obtain a preferred accounting outcome.
6. Control trade execution, confirmation and settlement
Use approved dealing channels and retain time-stamped trade tickets or equivalent evidence. Independently confirm key terms with the counterparty, including currency pair, buy/sell direction, notional amount, rate, trade date, maturity, settlement instructions and any optionality. Resolve confirmation mismatches promptly.
At each reporting date, reconcile the treasury position report to bank or counterparty statements and the general ledger. Investigate missing trades, duplicate confirmations, amendments, early terminations and settlements that have not cleared. Obtain independent valuation support for material derivatives and review valuation inputs, model changes and counterparty credit adjustments as appropriate.
7. Maintain hedge-accounting documentation at inception
Economic hedging and hedge accounting are not the same thing. A company may reduce its commercial FX risk without qualifying for hedge accounting. Where hedge accounting is intended, involve technical accounting before or at the time the hedge is designated—not after period-end when the desired accounting result becomes apparent.
Under US GAAP, ASC 815 contains the authoritative requirements for derivatives and hedging. FASB ASU 2025-09, issued in November 2025, makes targeted improvements to Topic 815, including changes affecting groups of forecasted transactions, forecasted nonfinancial transactions and certain dual-hedge strategies. For public business entities, the amendments are effective for annual periods beginning after December 15, 2026; for entities other than public business entities, they are effective for annual periods beginning after December 15, 2027. Early adoption is permitted. Controllers should assess which amendments affect their hedge portfolio and transition planning rather than assuming all entities have the same adoption date.
Under IFRS, hedge accounting is addressed in IFRS 9, with related risk disclosures in IFRS 7. The IFRS Foundation announced in September 2026 that the IASB had published a Request for Information as part of its post-implementation review of hedge accounting; the comment period runs until January 26, 2027. This is a review and consultation, not itself a change to the existing requirements. Canadian entities reporting under ASPE should assess the applicable Canadian Handbook requirements separately; do not assume that ASC 815 or IFRS 9 treatment can be carried across unchanged.
8. Reconcile derivative valuations and FX accounting through the close
Establish a monthly close schedule covering the capture of all trades, independent fair-value information, derivative subledger or treasury records, journal entries and balance-sheet reconciliations. Reconcile realized and unrealized gains and losses to the relevant instruments and underlying exposures. Review whether amounts recorded in earnings, other comprehensive income or accumulated other comprehensive income are consistent with the applicable accounting policy and designation.
For foreign operations, distinguish transaction gains and losses from translation adjustments. Review exchange-rate source, rate type, rate date and consolidation mapping. Investigate unusual movements in foreign-exchange gain or loss and cumulative translation balances, especially when entities change functional currency, are disposed of or undergo restructuring.
9. Integrate FX controls into SAP and reporting systems
In SAP S/4HANA or another ERP, validate exchange-rate tables, rate types, currency settings, valuation methods, posting accounts and interfaces to treasury systems. Confirm that the rates used for operational postings, period-end valuation and consolidation are approved and traceable to a documented source. Restrict who can maintain exchange rates and retain evidence of changes.
Where treasury trades are recorded outside the ERP, reconcile trade identifiers and settlement data to accounting entries. Monitor failed interfaces, manual uploads, duplicate postings and late rate updates. A dashboard should show exposures by currency, maturity, legal entity and business owner, with drill-down to source transactions.
10. Report exposures, hedge performance and exceptions to management
Give the CFO and audit committee a concise view of the largest currency risks and the actions taken. Useful measures include net exposure by currency, forecast accuracy, hedge coverage against policy limits, maturity concentrations, counterparty utilization, valuation differences, overdue confirmations and unresolved reconciliation items.
Run sensitivities that show how reasonably possible currency movements could affect cash flows, earnings and equity. Under IFRS, IFRS 7 requires disclosures about the nature and extent of risks arising from financial instruments and how the entity manages those risks, including qualitative and quantitative information. The sensitivity analysis should be consistent with the way management assesses risk and should not hide material concentrations behind an aggregate number.
Controller’s FX risk control checklist
- Current exposure register covering recognized, forecast and translation exposures.
- Documented functional-currency assessments and approved rate sources.
- Rolling cash-flow forecast by currency, entity and maturity bucket.
- Approved treasury policy, dealing limits and counterparty mandates.
- Documented link between each hedge and the underlying exposure.
- Independent trade confirmation and settlement reconciliation.
- Hedge-accounting designation and documentation completed at inception where applicable.
- Independent derivative valuation and monthly GL reconciliation.
- ERP exchange-rate access controls, interface monitoring and audit trails.
- Management reporting on sensitivities, forecast accuracy and policy exceptions.
Conclusion
Effective FX management is a cross-functional control discipline. Treasury may execute the transactions, but controllers help ensure that the exposure data is complete, the accounting is supportable, the ERP records are reliable and management understands the remaining risk. A disciplined framework reduces avoidable volatility, improves cash visibility and makes year-end reporting more defensible.
Official references
- FASB ASU 2025-09 — Derivatives and Hedging (Topic 815): Hedge Accounting Improvements (November 2025).
- IFRS Foundation — IFRS 9 Financial Instruments.
- IFRS Foundation — IFRS 7 Financial Instruments: Disclosures.
- IFRS Foundation — IASB Request for Information on hedge accounting (September 2026).
Disclaimer: This article is for general informational purposes only and is not accounting, legal, investment or treasury advice. Entities should assess their own risk exposures, contracts, internal policies and applicable accounting framework, including authoritative guidance and effective dates.
