How currency exposure monitoring and hedging is set up in finance and ERP systems

Currency exposure is usually measured inside the ERP, where foreign currency invoices, bank balances and intercompany items sit. Hedging usually happens in a separate treasury system or a spreadsheet. The two meet at revaluation, at deal settlement and in the general ledger, and that is where most of the friction lives.

Where the exposure data comes from

The ERP holds each transaction in its document currency and in the company's functional currency. Open receivables and payables can be pulled by currency, and bank accounts can too. Intercompany loans and trading balances often matter most and are the least tidy. Each side may book in a different currency or at a different rate.

Forecast exposure is harder to pin down. Expected sales and purchase commitments rarely live in one place. Teams typically collect them through a template sent to business units, then load the result into the treasury tool. The quality of that forecast decides how useful the hedge program can be.

Rates and revaluation

A rate table drives everything. Most setups hold more than one rate type. Postings use a spot rate, and period end uses a closing rate. Some companies also keep an average rate for translating income. Rates are fed from a market data provider or a central bank source. Someone should own the job of checking that the feed loaded before postings start.

At period end a revaluation run restates open foreign currency items at the closing rate. Unrealized gains and losses go to designated accounts, and the run usually reverses at the start of the next period. Realized differences are booked when an item is paid or collected. Configuration choices matter here. Which accounts are revalued, and whether by line item or by balance, shapes what the exposure report shows.

Capturing and settling hedges

Hedging deals are normally recorded in a treasury management system. Smaller operations keep a deal log in a spreadsheet. That works until volumes or audit scrutiny grow.

A dealer agrees the trade with the bank. A separate back office person matches the bank's confirmation against the captured deal. Keeping those duties apart is the main control in this area.

Settlement instructions flow from the treasury tool to payments, or are keyed into the bank portal by hand. Accounting entries for deals, including mark to market valuations, usually reach the ERP through an interface file or a journal upload. The mapping between deal types and GL accounts lives in that interface. It tends to be understood by very few people.

Hedge accounting and reporting

Where hedge accounting is applied, each relationship needs documentation at inception. That covers the hedged item, the instrument, the risk being hedged and how effectiveness will be assessed. Some treasury systems handle designation and effectiveness testing. Many companies still do this in workbooks and post the resulting entries to reserves manually.

Reporting pulls from both systems. A typical pack shows net exposure by currency, hedged amounts, the hedge position against policy limits and the valuation of open deals. Every figure in it should trace back to a ledger balance or a deal record. Where foreign currency reports go to a parent entity, a lender or a regulator, that tracing is checked before sign off.

Foreign currency receivables deserve a separate look. Aged balances in a weak currency lose value while collection drags on. A credit team that chases them on the same cycle as local balances may not see the risk.

Common points of friction

Rates in the treasury system and the ERP drift apart because they come from different feeds or are captured at different times of day. Intercompany balances fail to agree, so the exposure figure is wrong before anyone hedges it. Forecasts arrive late or are copied from the last cycle. The deal interface can also break quietly, leaving valuations unposted until reconciliation catches the gap.

Early close outs and rolled deals cause their own trouble. The treasury tool records them cleanly, but the ledger often needs a manual adjustment that nobody has written down.

Questions to ask the people who run it

• Which exposures actually get hedged, and who decides when a forecast is firm enough to act on?
• On the day a trade is placed, where does the exposure number come from: a system report or a personal workbook?
• Who loads exchange rates, and what happens when the feed fails?
• How are bank confirmations matched, and has anyone ever both dealt and confirmed the same trade?
• Which manual journals are posted for hedges or revaluation, and who reviews them?
• When intercompany balances disagree, which side is treated as correct?
• How are rolled or early closed deals reflected in the ledger?
• What do the policy limits say, and when were they last breached or waived?
• Which reports are rebuilt by hand each period, and why does the system version not get used?

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.