From Forecasting to Hedge Accounting: Driving Earnings Predictability in a Volatile FX Environment

From Forecasting to Hedge Accounting:

Driving Earnings Predictability in a Volatile FX Environment

Ask any corporate treasurer what keeps them up at night, and "the FX rate three months from now" is usually somewhere on the list.

In a recent webinar, Corpay Cross-Border's Jim Kessler, VP of Global Treasury Solutions, and Robert Norton, Global Treasury Solutions Team Lead, teamed up with Tim Potter, Managing Director at HedgeStar, to walk through what it actually takes to build a cash flow hedging program: one that holds up from the first forecast in a spreadsheet to the final journal entry in the financial statements.

Why Cash Flow Hedging Matters

Cash flow hedging exists to solve a deceptively simple problem: a business knows revenue or expenses are coming in a foreign currency, but has no idea what that currency will be worth by the time the transaction actually happens. Left unmanaged, that uncertainty shows up in three costly ways: missed payments and overdrafts that eat into liquidity; unpredictable FX losses on the balance sheet and cash sitting idle instead of being deployed efficiently.

The risk itself comes from three directions at once: business risk (global revenue and cost mismatches, intercompany flows), financial impact risk, and market forces - interest rates, macroeconomic shifts, geopolitical events - that can move rates overnight.

As Robert Norton put it,'the only certainty in FX is ‘the rate as of right now'. 'Everything a treasury team does after that is about managing what happens next.'

The consensus was that it's worth separating the two risks that show up across a company's FX lifecycle:

Margin risk is what cash flow hedging addresses directly the risk that a forecasted revenue or expense books at a different rate than when it was projected.

Remeasurement risk, sometimes called balance sheet risk, kicks in after that exposure is booked but before it's paid and converted.

This webinar focused squarely on the first half of that cycle: getting the forecast right, and locking in a rate before uncertainty erodes it.

Why Spreadsheet-Based FX Forecasting Breaks Down

For most companies, cash flow hedging starts and often stays in Excel. Jim Kessler has lived that reality from the corporate treasury side, and he was blunt about where it breaks down.

Budget rates, typically set during a September or October planning cycle and locked in by November or December, are often stale before the year they're meant to guide even gets underway.

'By the time you get into - call it Q1 or Q2 - those rates are stale,' Jim said.

Add in the fact that exchange rates move constantly, and any spreadsheet without an automated rate feed becomes a manual chore. Errors in a single cell can quietly fail to carry over, and nobody notices until the numbers don't add up.

The problem compounds with scale.

When multiple subsidiaries are each submitting their own forecast in their own spreadsheet version, consolidating that into one coherent picture by currency pair becomes, in Jim's words, 'very challenging and error-prone in ways that can materially affect what a business ends up hedging.'

There's often no audit trail either: no record of who changed what, when, or why, just a folder full of files named "v2," "v3," "v10," with no way to know which version reflects reality.

Then there's the timing mismatch and the difficulty of tracking hedged versus unhedged positions in real time as that forecast shifts. Layer on top of all this what Jim calls one of corporate treasury's most persistent structural risks: institutional knowledge concentrated in one person. 'When that person's on vacation, out on leave,[EP10] that knowledge goes away and everybody else is left scrambling,' he said.

None of this is a reason to avoid hedging. It's the case for getting out of the spreadsheet altogether.

How to Build a Cash Flow Hedging Program That Scales

The alternative Jim described is a structured, automated approach, one built around a framework Corpay calls CASE: Capture, Analyze, Strategize, Execute.

It starts with capturing exposures accurately, then analyzing them - looking at where risk has shown up historically and projecting where it's likely to emerge going forward. From there, a strategy gets formulated based on that data, and finally, trades get executed to hedge the exposure. Crucially, the process doesn't stop at execution. 'You want to execute, evaluate, and keep on iterating,' Jim said, underscoring that a hedging program is a living process, not a one-time setup.

Technology sits underneath every step of that framework, and Jim was direct about why that is:

'It's very difficult to run a cash flow hedging program using Excel spreadsheets, even with one currency pair,' he said. An automated platform replaces manual rate updates with a real-time feed, gives every change a visible audit trail, and critically removes the single-point-of-failure risk of one person holding all the institutional knowledge.

One practical tool is Cash Flow at Risk (CFaR) analysis, run at a 95% confidence level, which measures the potential adverse impact of FX movement on forecasted cash flows. Used well, it allows a company to move away from all-at-once spot purchases toward a layering strategy, building hedge coverage gradually over time.

A common example is what Jim calls the 80-60-40-20 strategy: hedging 80% of exposure for the quarter closest to maturity, 60% for the next, 40% for the one after that, and 20% for the furthest out, rolling forward as each month completes and a new trailing month gets added. 'It really helps with getting team discipline in the process,' Jim noted, adding that once the program is up and running, 'everybody's rolling in the same direction.'

Jim was also candid about the time it takes for the program to mature. He described it as a crawl-walk-run progression: get the forecast out, measure it against actuals every cycle, and use that n comparison to sharpen accuracy before scaling up hedge coverage.

'Everyone starts out in a place where “our data is bad", he acknowledged, but that's a starting point, not a disqualifier. Treasury and finance teams that stick with the process, he added, 'become more FX savvy over time,' building both better forecasts and a better hedging program as they go.

Once a program is established, expansion typically follows a similar logic. It starts with G10 currencies where liquidity and pricing are straightforward, then extends into markets that require non-deliverable forwards (NDFs), where value is marked-to-market on expiry and the difference is settled in a reporting (base) currency, rather than through an exchange of the buy and sell currencies.

Why Hedge Accounting Is More Than Compliance

Getting the hedging strategy right solves the economic side of the equation. But without hedge accounting, the accounting doesn't necessarily reflect that economic reality. This is where Tim Potter picked up the conversation.

Hedge accounting, Tim Potter explained, is a privilege, not a default. 'It is preferential treatment for derivative instruments or other financial instruments designated as hedging instruments,' he said, and earning that treatment means satisfying the requirements of ASC Topic 815 - a piece of guidance he acknowledged 'a lot of people cringe' at the mention of.

Here are the practical stakes: without hedge accounting, unrealized gains and losses on a hedge flow straight through earnings every reporting period, even though the underlying transaction hasn't happened yet. Over the life of a 12-month forward contract, that can mean a volatile hedge ultimately does exactly what it was designed to do: settle at the original agreed rate on expiry, and be recognized on the balance sheet as earnings.

With hedge accounting, those unrealized gains and losses are deferred through other comprehensive income and only recognized in earnings when the hedged transaction actually occurs, offsetting the FX impact of that transaction directly.

'We're going to have a really nice netting effect and we're also going to mitigate all of that disgusting noise' between execution and maturity, Tim said.

Qualifying for that treatment requires formal documentation prepared at the outset: identifying the hedging instrument, the hedged item, the risk management objective, and an initial effectiveness assessment.

"Highly effective," in accounting terms, generally means an 80% to 125% offset between the hedge and the underlying risk, tested through either a qualitative approach or quantitative methods like regression analysis.

Tim noted there's meaningful flexibility built into the guidance: hedges maturing within the same fiscal month as the transactions. The offset can generally be assumed to be perfectly effective, a friendlier standard than many treasury teams assume going in.

This is precisely the work HedgeStar handles on Corpay's clients' behalf - documentation, quarterly effectiveness testing, and the journal entries hedge accounting requires; as Jim described it, functioning, as 'a complete end-to-end hedge accounting solution provider' that lets client’s internal teams avoid hiring a specialized (and costly) resource in-house.

The Bottom Line

Strip away the acronyms — CFaR, NDF, ASC 815 — and the message from this session is straightforward: cash flow hedging only works as well as the forecast underneath it, and it only shows up correctly in the financial statements with disciplined hedge accounting behind it. Getting there means moving off individual spreadsheets, building a systematic and iterative process, and treating hedge accounting not as a compliance afterthought, but as the piece that finally connects the economics of a hedge to the numbers a business actually reports.

As Jim summed it up: the goal isn't perfection on day one, it's building a program deliberately, one that removes FX as an unknown variable and lets treasury and finance teams "make better decisions with confidence."

Cross-Border

Global payments

Risk management