Where currency conversion breaks: handoffs, exceptions and workarounds

Currency conversion breaks where a rate changes hands: loading the rate table, paying at a bank rate that differs from the booked one, receiving short foreign receipts, and revaluing before every posting is in. The evidence shows up as suspense balances, manual journals and gains or losses nobody can explain.

The rate table handoff

Treasury usually owns the rate source. Accounting owns the system that uses it. The gap between them is where most trouble starts. If the feed fails or someone uploads the file late, transactions post at the prior rate or at no rate at all. Some systems quietly fall back to the last rate they hold.

To spot it, compare the rate date on posted documents with the posting date. Look for batches of invoices that sit in a hold status every morning until someone fixes the table. Watch for a recurring email asking whether today's rates are loaded yet. That email is a control nobody has written down.

Payments that settle at a different rate

An invoice is booked at one rate. The bank executes the payment days later at its own rate, often with a spread. The difference has to land somewhere. Done properly, it goes to realized gain or loss. In practice it often goes to a clearing account while someone works out what happened.

The signs are easy to find. A suspense or clearing account for foreign payments that never quite empties. Payment disbursement schedules that pass quality checks but fail to match bank statements. Treasury and payables each blaming the other for the variance. If staff keep a private spreadsheet to tie bank confirmations back to vouchers, this break is live.

Foreign receipts that arrive short

Customers pay in their currency. Intermediary banks take fees along the way. What reaches the account is less than the invoice, and cash application cannot tell whether the shortfall is a fee, a rate effect or a genuine underpayment.

This shows up as small open balances on customer accounts that age without anyone chasing them. It also shows up as revenue adjustments posted in bulk at period end with vague descriptions. When revenue reconciliations keep listing the same unresolved items, short receipts are usually the cause. Bank fees booked as exchange losses distort both lines.

Rate type confusion

Most ledgers hold several rate types. Spot for transactions, average for some income statement items, historical for equity and certain assets, closing for revaluation. Each has a legitimate use. Problems begin when a configuration change or a new entity defaults to the wrong one.

Nobody notices until consolidation. Then the translation reserve moves in a way the controller cannot explain, or intercompany balances fail to eliminate because each side used a different rate type. Ask how often intercompany mismatches are cleared with a topside entry. Frequent topsides point here.

Revaluation run too early

Period-end revaluation of open foreign balances depends on every invoice, receipt and payment for the period being posted first. Close calendars often schedule it on a fixed day regardless. Late postings then sit unrevalued, or the job gets run again and reversed by hand.

Look for revaluation reversals and reruns in the journal history. Check whether the foreign currency reports sent to oversight bodies or head office were prepared before or after the final revaluation. A report that cannot be traced to general ledger balances at the date it was signed is a common finding, and this is often why.

Conversions done outside the ledger

When the system rate is wrong or missing, people convert in a spreadsheet and post the result as a local currency amount. The transaction looks clean. The foreign amount and the rate used are gone. Later, nobody can revalue it, reconcile it to the counterparty, or prove the figure in an audit.

The tell is journals in functional currency against accounts that should carry a foreign balance. Another is a shared folder of rate workbooks with names like "final" and "use this one." Budget execution and treasury reports built from these entries will tie to the ledger but not to anything underneath it.

Questions to ask the people who run it

The documented process tends to describe the system. The people describe the workarounds. Ask them directly.

• Where do today's rates come from, and what happens on the morning they are missing?
• Who decides which rate type a new entity or account uses?
• When a payment settles at a different amount from the one booked, where does the difference go first?
• How do bank fees on incoming payments get recorded, and who decides whether a short payment gets chased?
• Is there any spreadsheet used to convert, check or reconcile foreign amounts? Can it be shown?
• Has revaluation ever been rerun or reversed during close, and why?
• Which balances get cleared with a manual entry at consolidation?
• If the foreign currency report had to be traced back to the ledger today, which step would be hardest?

Listen for hesitation and for the name of one person who "just knows" how a step works. That person is often the real control, and any redesign that removes their role without replacing it will break again.

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.