Monitoring international rates: what each role knows that the others do not

Treasury knows why a rate moved. The system owner knows where it is stored. Local finance knows which rate the bank actually used. Group reporting knows which rate policy requires. Trouble starts when one of them changes a rate, a source or a timing without telling the others.

Treasury sees the market

Treasury watches rates because it has positions to manage. It knows when a central bank surprised the market and when a currency is thinly traded. It also knows when a published closing rate reflects nothing a dealer would actually quote. It holds the hedge book and the contracted rates inside it.

The gap is downstream. A dealer may treat a late afternoon fix as perfectly sound, while the ledger has already posted with the morning fix. Treasury often keeps its own spreadsheet of rates that never reaches the accounting system at all. When treasury explains a loss using its rates and the accounts show a different number, the meeting goes badly for everyone.

The rate table owner sees the plumbing

Someone maintains the rate table in the ERP or consolidation tool. Often this is a systems accountant or an IT analyst. They know which feed loads overnight, which rate types exist, how inverse rates are derived and what the system does with a missing value.

The purpose of each rate type is another matter. A rate type set up long ago for a single subsidiary loan may still drive a report nobody remembers commissioning. When the feed breaks, this person may copy the prior day forward to keep postings moving. That is a sensible call made quietly, and nobody downstream can see it happened.

Local finance sees what the bank did

Subsidiary accountants know the rate the bank applied to a payment, which seldom matches the table. They know which local regulator insists on a central bank rate for statutory books. They also know which customers pay late in a weakening currency. A foreign currency receivable that ages badly carries a collection problem and a revaluation problem together. Local finance feels the first long before group notices the second.

Their blind spot is the group view. A local team may book at the statutory rate and assume group will sort out translation. Group translates at its own rate type, and the difference lands in an account local finance never opens.

Group reporting sees the policy

The consolidation team knows the accounting policy. Closing rates for monetary balances, averages for the income statement, historical rates for equity and certain non-monetary items. They know where translation differences flow and what the auditors tested last cycle.

What escapes them is the market context behind a strange rate, or the operational reason a subsidiary booked what it did. Faced with an unexplained difference, they post a top-side adjustment. The cause stays in place and returns at the next close.

Where the gaps bite

Intercompany balances suffer first. Each side of an intragroup sale or loan records the transaction in its own currency, sometimes on different dates and at different rates. Settlement then happens at whatever the bank applied. When the counterparties reconcile, the residual looks like an argument about amounts. It is really an argument about rates. Tracking settlements against intercompany receivables, and agreeing in advance which rate governs, clears most of the noise.

Interest on cross-border intragroup loans causes a different kind of pain. Treasury sets the rate against a benchmark. Tax cares whether it holds up as arm's length. The booking team applies whatever the agreement says. If the benchmark is retired or a reset date slips past, no one owns noticing.

Tolerances fail more quietly. Many teams set a threshold for how far a loaded rate may drift from a reference before anyone investigates. The table owner picked the threshold. Treasury has never heard of it. Group reporting assumes rates are checked line by line. When a bad rate passes inside the tolerance, each party believes someone else was watching.

Questions to ask the people who run it

Written procedures describe the feed and the policy. The workarounds live in people's heads, and these questions tend to bring them out.

• Where does each rate type come from, and who notices when the source sends nothing?
• When the feed fails, what gets loaded instead, and who hears about it?
• Which rate did the bank apply to the last large intercompany settlement, and does anyone compare it with the table?
• Which reports or entities still depend on a rate type nobody has reviewed recently?
• Does any subsidiary keep statutory books at a rate different from the group, and where does that difference end up?
• Who has the authority to declare a published rate wrong, and what evidence would they want?
• How do intragroup loan rates reset, and who confirms the reset actually happened?
• Has anyone overridden a rate by hand since the last audit, and is the reason written down anywhere?

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.