Why most businesses don't have an FX policy
Large multinationals typically have a formal treasury function with defined hedging policies, approval thresholds, and dedicated staff. Most smaller and mid-sized businesses have none of that — FX decisions get made invoice by invoice, often by whoever happens to be looking at the payment that week, with no consistent logic applied from one decision to the next.
This isn't necessarily a problem if your FX exposure is small and infrequent. But once a business is regularly paying or receiving meaningful sums in a foreign currency, ad hoc decision-making starts to cost real money — not because anyone is making bad individual decisions, but because there's no consistency, no record of what was decided and why, and no clear escalation path when a payment is unusually large or a currency is moving unusually fast.
A simple written FX policy fixes most of this, and it doesn't need to be complicated. Here's a practical framework you can put together in an afternoon.
Step 1: Define your exposure
Start by listing every recurring source of foreign currency exposure — every currency you regularly pay or receive in, roughly how often, and roughly what volume. This doesn't need to be precise; the goal is to understand the shape of your exposure, not produce a perfect forecast.
A useful exercise: for each currency, note whether your exposure is one-directional (you only ever pay in EUR, never receive) or two-directional (you both pay and receive in the same currency, which can partially offset on its own without any action needed).
Step 2: Set a threshold for when the policy applies
Not every payment needs a formal process. A common approach is to set a simple threshold — for example, any single payment under $10,000 equivalent can be converted whenever convenient, no review needed, while anything above that threshold follows the steps below. Pick a number that reflects what's genuinely material for your business; there's no universal right answer, but it should be low enough to cover your largest recurring supplier payments.
Step 3: Decide your default approach for each currency
For each currency above your threshold, decide on a default behavior. Three common starting points:
Convert on receipt of invoice. Simple and predictable — you always convert as soon as you know the amount and due date, removing any timing decision entirely. This is the lowest-effort approach and a reasonable default if FX isn't a major cost center for your business.
Convert within a defined window before the due date. For example, "convert at any point in the final 5 business days before payment is due, based on prevailing conditions." This gives some flexibility to avoid converting on an obviously bad day, without requiring active daily monitoring.
Split into tranches. For larger or longer-dated payments, convert a portion early to lock in certainty and leave the remainder to convert closer to the due date. This is a middle ground between full exposure to rate movement and full certainty.
There's no single correct choice — the right default depends on your risk tolerance, how much time your team has to actively monitor rates, and how much a rate move would actually affect your margins on the underlying business. A useful gut check: if a 3% adverse move on this payment wouldn't meaningfully affect your business, a simple "convert on receipt" default is probably fine. If it would meaningfully affect margins or cash flow, a more deliberate approach is worth the extra effort.
Step 4: Set a simple escalation rule
Define a single rule for when something gets flagged to a more senior person rather than handled by default policy — for example, "any single payment over $50,000, or any planned conversion delayed by more than 5 business days past its due date, requires sign-off from [role]." This prevents large payments quietly drifting without anyone reviewing whether the default approach still makes sense.
Step 5: Write it down, however briefly
The policy doesn't need to be a formal document — a single page or even a structured note is enough, as long as it's written somewhere your team can refer back to consistently. The value isn't in the polish, it's in having one agreed approach instead of reinventing the decision every time a foreign currency invoice lands.
A minimal policy might read:
"Payments under $10,000 equivalent: convert on receipt of invoice. Payments $10,000–$50,000: convert within 5 business days of the due date, monitoring for unusually adverse moves. Payments over $50,000: split 50/50 — convert half on receipt, half within 5 business days of due date, with sign-off from [name] if delaying further than that window."
That's a complete, usable policy. It can always be refined later.
Step 6: Review it periodically, not constantly
Revisit the policy every 6–12 months, or after any payment that didn't go to plan, rather than trying to adjust it after every single transaction. The goal is a stable, repeatable process — not a policy that changes every time the market moves, which defeats the purpose of having one.
Where a tool helps
A written policy tells you what to do by default. Knowing whether today is a good day to act within that policy — whether you're in the "convert on receipt" camp or the "window before due date" camp — still benefits from visibility into current market conditions, upcoming events that might move the rate, and how today compares to the recent range.