The hidden FX exposure sitting in your receivables ledger, and how treasury teams actually hedge it
The moment you book a receivable denominated in a foreign currency, you have taken a position. You are long that currency, exposed to every pip of movement between invoice date and settlement date. In industries where payment terms run sixty, ninety, sometimes a hundred and twenty days, that is a meaningful position to carry. What most treasury teams underestimate is how much exposure accumulates inside the receivables ledger itself, before a single hedge is placed or a monthly report has been run.
The Structural Problem Nobody Owns
Your accounts receivable balance is not a neutral accounting entry.
Receivables are managed by finance and accounting. Hedging decisions live in treasury. Those two functions run on different rhythms, different systems, different reporting cadences. Exposure accumulates on one side of the organization before the other side can respond, and the lag is rarely flagged as a risk management failure because nobody owns the gap explicitly. It falls between the org chart.
I have watched this play out repeatedly: a treasury team running a technically sound hedge program, properly approved, properly documented, with one critical flaw. Their hedge book reflects the receivables position as it existed at the start of the quarter. The actual ledger has moved substantially since then, and nobody told them.
The longer that lag persists, the more unhedged foreign-currency exposure the company is carrying, without anyone treating it as a position that needs to be managed.
Why the Exposure Is Larger Than It Looks
A few dynamics compound this in ways that don't surface cleanly in aggregate reporting.
Invoice timing is lumpy. Large deals close at quarter-end, invoices batch together, and the receivables ledger can spike materially in a matter of days. A treasury team monitoring exposure weekly or monthly will consistently be behind the actual position. That's not a failure of process; it's a consequence of how enterprise sales cycles work. But it means the hedge program is perpetually calibrated to yesterday's position.
Customers do not pay on schedule as often as finance models assume. Extended days sales outstanding stretches the exposure window beyond what the original hedge was sized to cover. If you hedged ninety days and your customer pays on day one-fifteen, you have a gap. A real one, with real P&L consequences.
Partial payments create mismatches that aggregate hedging programs simply aren't designed to handle with that kind of granularity. A customer who pays sixty percent of an invoice on time leaves a residual foreign-currency receivable that maps onto nothing in the hedge book.
The net result: the notional hedge coverage treasury reports does not correspond to the actual economic exposure sitting in the ledger on any given day. The two numbers drift apart continuously, typically in the direction of underhedging.
Closing the Information Gap
The foundational fix is shortening the cycle time between receivables data and treasury visibility. When treasury has direct, frequent access to the foreign-currency receivable balance, they can size and time hedges with meaningfully greater precision.
This is not necessarily a technology problem. Some teams solve it with integrated ERP and treasury management systems. Others solve it with a disciplined manual process that runs every few days. I've seen both work. What distinguishes the teams that manage this well is that they treat the receivables ledger the way a trading desk treats a position report: as current information, not a monthly snapshot. The hedge program calibrates against that current position, not against a forecast that was built at the start of the quarter and hasn't been touched since.
Building Hedges That Can Absorb Uncertainty
The receivables ledger is not a fixed number. It moves daily as invoices are raised and payments arrive. A hedge program that treats it as static will produce basis risk, the difference between what you have hedged and what the underlying exposure actually is on settlement date.
One approach is hedging a defined percentage of expected exposure rather than the full notional, building coverage in layers as the receivable balance becomes more certain. Early in the payment window, you hedge conservatively. As settlement approaches and the receivable confirms, coverage increases. The mechanics aren't complicated. The discipline is in running the process without letting it slip when things get busy.
Options deserve more consideration than most corporate treasury teams give them. A vanilla forward commits you to a rate on a specific date; if your customer pays early or late, that forward no longer corresponds to the underlying exposure, and you now have two problems instead of one. An option preserves flexibility without abandoning protection — think of it as buying an umbrella instead of betting on sunshine. Whether the premium is worth paying depends on how unpredictable your receivables schedule actually is, but in my experience, that calculation is made less often than it should be.
Owning the Residual
Even well-run hedge programs generate residuals: partial payments, amended invoices, cancellations after a hedge is already booked. This cannot be eliminated. It can be managed, but only if someone owns it explicitly, which is precisely the kind of operational detail that tends to fall through the cracks between finance and treasury.
Teams that handle this well maintain a clear reconciliation cadence. Someone is responsible, by name, for matching the hedge book to the receivables ledger on a defined frequency, identifying mismatches, and either closing out excess hedges or extending coverage where gaps exist. The results feed directly into how subsequent hedges are structured.
Not Every Currency in the Book Deserves the Same Treatment
Applying a uniform approach across your full receivables ledger is a mistake, and it tends to create the most trouble at the edges.
Liquid, freely traded currencies — euros, sterling, yen — have deep forward markets and manageable bid-ask spreads. Hedging them is operationally straightforward. Emerging-market currencies are a different category entirely. Capital controls, restricted forward markets, and thin liquidity can mean the hedge instrument you need simply doesn't exist in the form you require, or costs more than the exposure justifies.
In those cases, the realistic alternatives are natural hedges, funding local operations in the same currency as the receivable, or accepting a residual exposure managed through pricing strategy rather than financial instruments. The discipline is knowing which currencies in your ledger are hedgeable and which are not, and building your risk framework around that honest distinction rather than pretending uniformity is achievable.
What It Actually Costs When This Goes Wrong
The losses from unhedged receivables exposure rarely arrive as a single dramatic event. They accumulate as a persistent drag on margin: invoices raised in a currency that weakened gradually, settlement proceeds that land consistently below the budgeted rate, revenue erosion that shows up in the variance column every quarter without a clearly identified cause.
Occasionally the loss is acute. A sharp currency move during a long settlement window. A large receivable exposed at exactly the wrong moment. Those events get noticed. The chronic version is more damaging in aggregate precisely because it is diffuse enough that no one builds a business case for addressing it. It registers as noise. It becomes the number nobody explains in the quarterly review, just accepted as part of doing business internationally.
The exposure in your receivables ledger is real. It accrues every time you book a foreign-currency invoice. Managing it doesn't require exotic instruments or a sophisticated technology stack. It requires someone deciding that the gap between the hedge book and the economic reality beneath it is worth closing, and then running that process with enough consistency that the gap doesn't just quietly reopen the following month.
