Monitor and execute risk and hedging transactions: how the process runs

Treasury sets a hedging strategy that senior finance approves. Analysts then measure the interest rate and currency exposures the business creates, and dealers trade within agreed limits. The back office confirms and settles each deal. Accounting records the hedge entries, tests effectiveness and reports results back to the people who own the strategy.

The steps in order

1. Set the strategy and policy. The treasurer drafts a risk policy covering permitted instruments, hedge ratios, approved counterparties and dealing authority. The CFO reviews it, and a board or risk committee signs it off.

1. Collect exposure data. Subsidiaries, FP&A and the payables and receivables teams submit forecasts of foreign currency flows. The debt team supplies details of floating rate borrowings and upcoming refinancings. This input is usually the weakest link, because the people providing it rarely see how it gets used.

1. Measure interest rate risk. A treasury analyst models how rate moves would affect interest cost and compares the fixed and floating mix against the policy target.

1. Measure foreign exchange risk. The same analyst, or a colleague, nets currency positions across entities. Transaction exposure is separated from translation exposure, since each is handled differently.

1. Review wider exposures. A risk manager looks at counterparty credit, concentration with any single bank, and commodity price risk where it exists. Breaches of counterparty limits are flagged before any new trade is proposed.

1. Recommend hedges. The analyst writes up which positions to cover, with which instrument and for what tenor. The treasurer approves within delegated authority. Anything above that level goes to the CFO.

1. Document the hedge relationship. Before or at the moment of trading, the hedge accountant prepares designation paperwork that links the instrument to the hedged item and states how effectiveness will be tested. Late documentation is a common audit finding.

1. Execute the trade. A dealer in the front office obtains competing quotes from approved banks, often on an electronic platform, and books the deal. Trade details are captured in the treasury management system straight away.

1. Confirm independently. Back office staff match the bank's confirmation against the booked trade. Dealers should not touch this step. Mismatches go back to the front office for explanation.

1. Settle cash flows. The cash management team releases payments and receipts on value date and ties them to bank statements.

1. Value and monitor positions. A middle office analyst marks open trades to market, checks them against limits and runs effectiveness tests. Exceptions are escalated to the treasurer.

1. Post accounting entries. The hedge accountant or general ledger team posts fair value changes, amounts deferred in equity and reclassifications into profit and loss. Manual journals are routed for approval before posting.

1. Reconcile. Treasury subledger balances are agreed to the general ledger, and positions are agreed to counterparty statements. Differences are corrected and explained.

1. Report. The treasurer presents exposure, hedge cover and results to the CFO and the risk committee. Financial reporting uses the same data for statutory disclosures.

1. Feed results back into strategy. Persistent forecast errors, ineffective hedges or market shifts prompt the treasurer to revise the policy, which restarts the cycle.

Where the hand-offs tend to break

The gap between steps 2 and 3 causes most trouble. Business units send forecasts in different formats, on different dates, with different assumptions. Analysts then spend effort cleaning data instead of analysing it.

A second weak point sits between execution and documentation. When dealers trade quickly in a moving market, designation memos can follow days later. Auditors may then reject hedge accounting for that trade, and the earnings volatility the hedge was meant to remove comes back.

Segregation between dealing and confirmation is often clear on paper. In small teams, though, the same person may cover both during holidays or illness.

Questions to ask the people who run it

Written procedures and daily practice drift apart in this process. These questions help surface the difference:

• Where do exposure forecasts actually come from, and who chases late submissions?
• How often do forecasts turn out wrong, and does anyone go back and measure it?
• Who books a trade when the usual dealer is away?
• Is the designation memo written before the trade, or reconstructed afterwards?
• Which confirmations arrive by email or phone instead of through the matching platform?
• What spreadsheets sit outside the treasury management system, and who maintains them?
• When a limit is breached, who hears about it first, and what happens next?
• Which manual journals get posted every period, and why can the system not generate them?
• What reconciling items have stayed open for a long time?
• If the policy changed tomorrow, which steps would the team struggle to adapt?

What changes tend to disturb

New systems often shift who captures trade data, which can quietly erode the separation between front and back office. Centralising exposure collection improves data quality but changes the relationship with subsidiary finance teams, who may feel they have lost visibility of their own positions. Any redesign should map who holds authority at each step before and after, since approval rights are where gaps open up 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.