Currency conversion: what each role knows and where the gaps bite

Treasury knows the rate actually dealt. Payables knows when money left and in which currency. The ledger team knows which rate policy the books must follow. Budget holders know what they committed in home currency. Trouble sits at the joins, where a rate chosen by one role is explained by another.

The dealer or treasury analyst

This person holds the facts nobody else sees in full. They know whether a conversion was done at spot or drawn against a forward contract. They know the spread the bank charged, the value date agreed and whether the trade was netted against an opposite flow elsewhere in the group.

What they usually lack is the link back to the underlying documents. A dealer converts a lump of currency to cover a payment run. Which invoices sit inside that lump is invisible from the dealing screen. So the confirmation goes into a shared folder and the context stays in someone's head.

Payables and receivables staff

The transaction teams know the invoice currency, the agreed terms and the awkward details. A supplier deducted bank charges before crediting the account. A customer short paid because they converted at their own bank's rate. A partial settlement left a small foreign balance open.

On the receiving side, these staff record incoming foreign receipts, reconcile them to what was billed and post adjustments when the converted amount falls short. Most of those adjustments get coded as an exchange difference, even when part of the gap is really a fee or a dispute.

They often key a rate by hand or accept whatever the system defaults to. Few of them know where that default came from or when it was last refreshed.

The ledger and reporting accountant

The accountant knows the policy. Transactions book at a rate for the transaction date or a period average. Open monetary items get revalued at the closing rate. Foreign currency reports must agree to general ledger balances before anything goes to a regulator, a lender or a central reporting body.

What this role sees, though, is a realised gain or loss line with no story attached. A large swing could be genuine market movement. It could equally be a dealer using a forward rate the ledger never knew about, or a clerk posting at last month's figure. Working out which takes digging through emails, because the evidence lives with the other roles.

Budget holders

A programme manager or department head commits spending in home currency at a planning rate. They track execution against that budget and assume the number holds.

They rarely know that a weakening home currency has quietly consumed their headroom until the next execution report lands. In public bodies this matters more. Spending authority is often a legal limit, and an overrun caused by exchange movement can still count as a breach that must be reported. The budget holder did nothing wrong, yet carries the consequence.

Where the gaps turn into problems

The most common failure is rate source mismatch. Treasury deals at one rate, payables books at a system rate, and the ledger revalues at a third. Each figure is defensible. Together they produce a difference that nobody owns and everyone explains differently.

Payment scheduling adds its own version of this. A disbursement schedule is built and certified in home currency, quality checks pass on those amounts, and the actual settlement converts later at a different rate. The schedule looked correct when approved. The ledger now shows a variance against a certified document.

Fees disguised as exchange differences distort analysis for years. Once bank charges sit inside the gain or loss account, treasury cannot measure what conversion really costs and procurement cannot negotiate it.

Revaluation reversals catch teams out at period end. If open items were revalued and then settled before the reversal ran, the gain or loss gets counted twice or not at all. The accountant spots it. The clerk who settled the item has no idea anything happened.

Questions to ask the people who run it

The documented procedure and the daily habit are rarely the same. Ask these of the people doing the work, not their managers.

• Where does the rate on a typical posting come from, and who last updated it?
• When a payment converts at a different rate from the invoice, what happens to the difference, and who decides the account code?
• Does anyone tell the ledger team when a forward contract is used to settle?
• How are bank charges separated from exchange movement, if at all?
• What do budget holders hear about currency movement, and when?
• Which reconciliation breaks most often at month end, and what is the usual fix?
• Is there a spreadsheet somewhere that holds rates or mappings the system does not?

That last question tends to reveal the real process. A private rate table or a manual mapping file is usually where knowledge from one role got stranded.

What a change usually breaks

Automating rate feeds or consolidating payment runs can remove the very manual step where someone noticed a problem. Before redesigning, find out which person currently catches the mismatch, and make sure the new design still gives them the information they used to catch it. Otherwise the error does not disappear. It just reaches the financial statements later.

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.