Monitor international rates: how the process runs step by step

Monitoring international rates means capturing foreign exchange and interest rates from an agreed source, checking them, approving them and loading them into finance systems. Accounting then revalues balances with them, and treasury tests exposure against policy. Treasury owns most steps. Accounting and consolidation use the output.

The steps in order

1. Define the rate set. The treasury manager decides which currencies are tracked and which rate types matter: spot, forward, average and any interest benchmarks tied to borrowing or deposits. The financial controller signs off, because every revaluation downstream depends on this choice. The same decision fixes the market data source and the cut-off time at which rates are struck.

1. Set tolerance bands. The treasurer agrees how far a rate may move between captures before someone has to look at it. A second band covers the gap allowed between the primary source and a backup source. These limits belong in the treasury policy, not in an analyst's head.

1. Capture rates at the cut-off. A market data feed usually pulls the values automatically. A treasury analyst confirms the pull ran and that nothing came back blank. Where no feed exists, the analyst keys rates in from the provider's screen, which needs a second person to check.

1. Validate against the backup source. The analyst compares each captured value with an independent quote. Stale prices, inverted currency pairs and missing illiquid currencies are the usual faults. Anything outside the bands set earlier gets flagged.

1. Investigate breaches. For each flag, the analyst works out whether the market genuinely moved or the data is wrong. Genuine moves are noted with a short reason. Bad data is corrected from the backup, and the treasury manager is told about any currency that still cannot be priced.

1. Approve and publish the rate table. The treasury manager reviews the validated set and approves it. A finance systems administrator loads it into the ERP and the treasury management system. Publishing before approval is a common control gap, so the load should be blocked until sign-off exists.

1. Revalue foreign currency balances. General ledger accountants run revaluation on cash, receivables, payables and intercompany balances held in other currencies. Unrealised gains and losses post automatically. Accounts receivable staff watch for customer balances whose value has shifted enough to change collection priority or credit limits.

1. Test exposure against policy. The treasurer compares open currency positions and floating rate debt with the hedging policy. Where exposure sits outside policy limits, a hedging proposal goes to whoever holds dealing authority, often the finance director.

1. Report movements and impact. A treasury analyst prepares a note on significant moves and what they did to earnings, cash and covenant headroom. The treasurer reviews it before it reaches finance leadership and subsidiary finance teams.

1. Lock period-end rates. At month end, treasury freezes closing and average rates for the period. The consolidation accountant uses closing rates for the balance sheet and averages for the income statement of each foreign entity. Once locked, changes need the controller's approval and a documented reason.

1. Review sources and limits. Treasury and internal control revisit the rate set, the providers and the tolerance bands on a scheduled basis. New entities, new currencies and changes in borrowing all trigger an earlier review.

Where it tends to break

The weak points sit at handoffs. Subsidiaries sometimes pull their own rates from a bank website, so the group carries two versions of the same currency. Manual overrides in the ERP often leave no trail. Average rates get calculated in a spreadsheet nobody else understands.

Timing causes quieter trouble. If the cut-off in policy differs from the one the feed actually uses, revaluation and treasury reporting will disagree. Small gaps like this surface at audit, long after anyone remembers why.

Illiquid or controlled currencies deserve their own handling. Official and parallel rates can differ sharply, and the choice between them is an accounting judgement that the controller should own.

Questions to ask the people who run it

• Which source do rates really come from on a normal day, and what happens when the feed fails?
• Who can change a rate after it has been loaded, and where is that change recorded?
• Do subsidiaries use the group table, or do any keep local rates for invoicing or banking?
• How are average rates calculated, and could someone else reproduce the figure?
• When a value breaches tolerance, who actually decides it is acceptable?
• Has the published table ever been loaded before approval to meet a close deadline?
• Which currencies cause trouble repeatedly, and how are they priced when quotes are thin?
• Does the hedging review happen when exposure moves, or only at a fixed point in the calendar?
• What does consolidation do differently from what the policy says?
• If the lead analyst were away, could anyone else run the capture and validation without help?

Answers that drift from the written procedure are not necessarily failures. Often they show where the policy never matched how the work had to be done, and that is the part worth redesigning first.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.