A budget is written in one currency and spent in another. Between the two sits a number that moves on its own: the exchange rate. When it moves the right way, a program quietly gains a little room. When it moves the wrong way, a clinic’s drug supply shrinks, a month of rations thins, a planned activity is cut, and the loss is recorded as a technicality. We tend to treat currency as weather, something that happens to us, outside the design. But the rate is not weather. It is a force we can plan for, share, and partly tame, and pretending otherwise means the people we serve absorb a risk no one decided to give them.
Where the value leaks out
The leak is rarely dramatic. It is slow and procedural. A grant is committed in a strong currency many months before it is spent in a weaker, volatile one. By the time the money lands and converts, the local cost of what it was meant to buy has shifted. Inflation in the operating country, a sudden devaluation, a gap between the official rate and the rate at which money can actually be moved: each one shaves value off the original promise. None of it is fraud. None of it is waste in the way an auditor would flag. It is friction in the financial plumbing, and because it does not look like waste, we have learned to treat it as nothing.
The deeper problem is who ends up holding the loss. In most arrangements, the risk settles at the bottom of the chain. The agreement is fixed in the donor’s currency, the commitment is locked, and whoever is closest to delivery absorbs the difference when the rate turns. The organization with the least financial cushion, often a local partner running on thin margins, ends up carrying a risk created far upstream by the structure of the deal. The actor least able to weather a currency swing is the one most exposed to it. That is not a plan. It is the residue of how the chain was built, and a residue can be redesigned.
Currency risk runs downhill, and it pools at the bottom, on the partner with the least cushion and the most at stake.
This is not a story about a careless treasurer or a reckless funder. The funder who fixes a grant in a stable currency is being a responsible steward of money they answer for. The finance team that follows the agreed rate is doing its job correctly. The incentive is working as designed. The trouble is that the design quietly assigns a real risk to whoever is weakest, and calls the result an accident. We can decide differently.
Treating currency as a choice, not a fate
The answer is not to pretend we can predict the markets, and it is not to demand that any single actor swallow the whole risk. It is to bring currency out of the technical footnotes and into the design of the deal, where it belongs. A few moves make that real, and they are ones funders and implementers are better off agreeing together, since neither gains when a swing erases a month of work.
Name currency risk openly in the budget and the agreement, rather than leaving it as a silent assumption that only becomes visible when it has already cost something. A risk that is written down can be discussed. A risk that is hidden in a fixed rate can only be discovered, usually too late.
Decide deliberately who carries the swing, instead of letting it roll downhill by default. A contingency line that either party can draw on, a clause that revisits the rate if it moves beyond an agreed band, a willingness to commit in the currency of spending where that is possible: each one shares a risk that currently lands on whoever is least able to bear it.
Shorten the gap between commitment and conversion where the operating environment is volatile, because much of the loss lives in the long wait between a grant being promised in one currency and spent in another. The longer the money sits in transit, the more the rate can move against the work.
And measure the erosion honestly, so we can see how much of the original promise survives conversion. If we never count what currency costs us, we will keep treating it as nobody’s problem, which in practice means it becomes the frontline’s problem.
None of this requires a trading desk or a forecast no one can make. It requires treating the exchange rate as part of the program rather than an act of nature that befalls it. A currency swing that thins a month of food is not a footnote in a financial report. It is a cut to the work, decided by a structure we wrote, and it is a structure we can write better, together, starting with the next agreement we sign.