Running Treasury Across Currencies for a Global SaaS Team

List every currency you receive revenue in and every currency you pay expenses in, then net them against each other. A company billing in euros and also paying a European engineering team in euros has a much smaller real exposure than the gross numbers suggest, because the incoming and outgoing euros partly offset. Most teams overestimate their FX risk because they look at revenue or costs in isolation instead of the net position.

Do this exercise monthly for the first two quarters after you start operating in a new currency, since the net position shifts as headcount and customer mix change. Say your gross euro revenue is 300,000 and your gross euro payroll is 250,000; your real net exposure is the 50,000 difference, not the larger of the two figures.

Work through the exposure map in this order:

1. List every currency you receive revenue in and every currency you pay expenses in, so the full picture sits on one page.
2. Net each currency's inflows against its outflows to find the real exposure, not the larger gross figure.
3. Repeat the exercise monthly for the first two quarters, since headcount and customer mix change the net position.
4. Use the net figure to decide how much cash to hold in each currency and which exposure deserves a hedge.

Once you know your net exposure in a currency, decide how much of it to hold as cash in that currency versus converting back to your reporting currency right away. Holding enough foreign currency cash to cover the next one to two months of expenses in that currency avoids repeated small conversions and their fees; converting the rest back reduces how much of your balance sheet is exposed to a currency move you can't control.

Write this rule down as a policy rather than deciding case by case, or you'll end up converting reactively whenever the rate happens to look good that week, which is a timing bet, not a treasury decision.

Not every currency exposure needs a hedge. A small, short-term net position often costs more to hedge than it would cost to simply absorb the swing. A large, multi-quarter commitment, like a fixed euro-denominated lease or a large team payroll run in a currency that's been volatile, is a better candidate for a forward contract or a natural hedge, such as billing that same customer segment in their local currency to offset the cost.

Software businesses generally run thicker gross margin than services or retail businesses do, which gives more room to absorb an FX swing before it shows up in the numbers your board watches¹. That cushion is exactly why many software companies skip hedging small exposures and only bother once a single currency commitment gets large relative to that margin.

A forward contract locks in a conversion rate for a future date, which removes the uncertainty but also removes any upside if the rate moves in your favor, and it typically requires a banking relationship set up to offer them. A natural hedge, matching revenue and costs in the same currency, costs nothing extra but only works when your business mix allows it. Doing nothing is a legitimate choice for small, short-dated exposures, as long as it's a deliberate choice and not an oversight.

Whichever you pick, apply it consistently rather than hedging some months and not others based on how confident someone feels about where rates are headed. A policy that hedges opportunistically is really just speculation wearing a treasury hat.

Decide, and document, which rate convention you use to convert foreign transactions into your reporting currency, spot rate at transaction date, month-end rate, or an average, and apply it consistently so your financials don't jump around because of a rate methodology change rather than the business itself. Inconsistent conversion methodology is one of the more common findings when a global SaaS company's books get their first real audit.

A global payroll platform like Deel or Rippling handles the local-currency payment side of a distributed team, which removes one recurring source of manual FX conversion from your own treasury workflow.

A common misstep is pricing a new multi-year international contract entirely in your own reporting currency to avoid FX exposure, then discovering at renewal that the customer's local-currency budget has shifted enough that they push back hard on the renewal price. Passing all the FX risk to the customer doesn't eliminate it; it just moves the pressure to a different point in the relationship. Building a small, explicit FX buffer into international pricing tends to age better than assuming the exposure disappears because the invoice says dollars.