Where risk and hedging transactions break down

This process usually breaks where information changes hands. Exposure forecasts arrive late or inconsistent. Trades get booked outside agreed limits. Hedge documentation trails the deal. The accounting entries are built in spreadsheets that never quite agree with the ledger. Each failure leaves visible traces in confirmations, journals and audit queries.

The exposure forecast handoff

Hedging is only as good as the exposure it covers. Business units send forecasts of foreign currency receipts, payments and borrowing needs to treasury. Those forecasts are often built for budgeting, not for hedging, and nobody owns their accuracy once they leave the business.

The symptoms are easy to spot. Hedge ratios jump between periods with no change in strategy. Treasury rolls forwards repeatedly because the underlying cash flow slipped. Analysts keep their own adjusted version of the forecast because they no longer trust the submitted one. When a forecast transaction stops being probable, the hedge often stays designated because no one told treasury.

From strategy to the dealing desk

A risk strategy sets limits, approved instruments and counterparties. The trouble starts when those rules live in a policy document and never reach the dealing system. Dealers then rely on memory or a spreadsheet of limits that someone updates when they remember.

Look for approvals given by email or chat after a trade is already done. Look for counterparty exposure that only gets checked during the period close. A breach found weeks later, with a polite explanation attached, means the control sits in the wrong place.

Trade capture and confirmation

The front office books a trade. The back office matches it against the counterparty confirmation. Small errors at entry, such as a wrong value date or a swapped currency pair, turn into amendments, cancelled settlements and awkward calls to the bank.

An aging list of unmatched confirmations tells the story plainly. So does a high volume of trade amendments, or the same dealer appearing on most of them. If dealers can edit trades after confirmation without a second approval, segregation of duties exists only on paper.

Hedge designation and documentation

Hedge accounting depends on documentation prepared at the start of the relationship. It must identify the hedged item, the risk being hedged and how effectiveness will be assessed. In practice, treasury executes and assumes accounting will document. Accounting assumes treasury has done it.

The giveaway is documentation dated after the trade, or templates copied forward with the old hedged item still named. Auditors asking for designation memos that take days to produce is another strong signal. Late documentation can cost the hedge its accounting treatment entirely, which pushes fair value swings straight into earnings.

Effectiveness testing and accounting entries

This is where most rework happens. Fair values come from the treasury system or bank statements. Effectiveness tests run in spreadsheets. Someone then prepares manual journal entries for the ledger and routes them for approval. Each step introduces a chance to pick the wrong rate, the wrong date or the wrong version of a file.

Recurring reconciling items between the treasury subledger and the general ledger point directly to this problem. Watch for amounts in other comprehensive income that never get released when the hedged transaction occurs. Watch too for correcting entries posted in the following period, and for one person who is the only one able to explain the spreadsheet logic.

Exceptions that nobody planned for

Early terminations, partial unwinds, restructured loans and cancelled purchase orders all force changes to existing hedge relationships. These events are rare enough that no standard procedure exists, so each one is handled from scratch.

De-designation entries recorded late, or not at all, are the clearest evidence. Others include settlement payments made by manual wire because the system could not process an early close, and hedge registers that still list relationships for transactions that ended long ago.

Settlement and the cash side

Forward and swap settlements must reach the payments team with correct standing instructions. Where netting with a counterparty is allowed but not systematised, staff calculate net amounts by hand. Any failed or duplicated settlement here usually traces back to an instruction sent outside the normal payment workflow.

Questions to ask the people who run it

The documented process and the lived one tend to drift apart. These questions surface the gap:

• Which forecast do you actually hedge against, and who adjusted it?
• How do you find out that a forecast cash flow will no longer happen?
• Where do you check a limit before dealing, and what happens if the check is unavailable?
• Who prepares the hedge documentation, and when does it get signed?
• Which spreadsheets would stop the close if their owner were away?
• What manual journals get posted every period without fail?
• When a trade is amended after confirmation, who approves it?
• How was the last early termination handled, step by step?
• Which reconciling items between treasury and the ledger have simply become normal?

The answers to the last question are often the most revealing. Items that everyone has stopped questioning usually mark the handoff that broke 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.