How boutique travel agencies handle FX risk on client deposits

Your client pays a €9,600 deposit on a €32,000 Maldives group booking. Six weeks later, when the USD-denominated resort balance is due, the EUR/USD rate has shifted enough to cost you €700 you never quoted for. That is how FX risk on client deposits quietly eats boutique travel agency margins — not in dramatic blowups, but in small, grinding losses that compound across a season.

The corporate world has treasury desks and forward contracts for this. You have a spreadsheet and a prayer. This guide gives you something in between: a practical framework for shrinking the FX window from deposit to supplier payment, without needing a finance team.

Why the deposit-to-payment gap is where the damage happens

Most FX risk guides are written for exporters shipping goods — their exposure sits in 30–90 day receivable cycles. Your exposure is structurally different. You collect a deposit the moment the client books, then hold it for weeks or months while the supplier invoice denominated in another currency accumulates.

A €32,000 group safari, for example, might look like this:

• Deposit collected: €8,000 in EUR at booking (8 weeks out)
• Supplier payment due: $6,200 to a Kenyan ground operator, in USD, 2 weeks before departure
• Balance collected: €24,000 from the client, 6 weeks before travel

That creates two FX exposure windows: deposit to balance (currency rate drift), and balance to supplier payment (rate drift again). On a busy season with 15 active bookings across USD, THB, and AED suppliers, you are carrying meaningful unhedged exposure at any given moment.

The mistake most agencies make

Collecting everything in the client's currency (EUR or GBP) feels tidy, but it pushes the entire FX burden to the last moment, when you convert to pay suppliers. By then, you have already invoiced the client and have no room to recover a rate move.

The fix is not to invoice in the supplier's currency (that just transfers risk to the client and creates pricing confusion). The fix is to keep the client's deposit in their currency for as long as possible and pay suppliers from that balance directly, shrinking the window where rate drift can bite you.

A practical approach to FX risk on client deposits

Step 1: Invoice in the client's currency, every time

This is the foundation. A UK group expects to see GBP. A German family expects EUR. Invoicing in your own operating currency and asking them to eat the conversion is friction that loses bookings and obscures your pricing.

With a tool like ZenPay, each invoice carries its own currency selection across 11 currencies (EUR, USD, GBP, CAD, AUD, JPY, CHF, SEK, SGD, BRL, CNY). You send the deposit invoice in GBP, the balance invoice in GBP, and the client never thinks about FX. You handle it on your side.

Step 2: Hold deposits in multi-currency wallets, not a single account

This is where most agencies leave money on the table. The deposit arrives in EUR, gets converted to your home currency immediately, and then reconverted to USD when the supplier invoice arrives. Two conversion events, two spread costs, two chances for rate drift.

ZenPay's multi-currency wallets aggregate incoming payments per currency. A €8,000 deposit lands in your EUR wallet. A £5,500 deposit lands in your GBP wallet. You see your actual exposure per currency in one dashboard, not a blended number.

When a USD supplier invoice comes due, you pay it from the USD wallet balance if you have one, or you convert from EUR at a single moment you control. One conversion, not two.

Step 3: Tighten the deposit-to-balance window

The longer the gap between deposit collection and balance collection, the wider your FX exposure. If your booking window is 10 weeks and you collect a 25% deposit upfront with the 75% balance 2 weeks before travel, you are holding that deposit for 8 weeks.

Consider restructuring to a 50% deposit plus a 50% balance 8 weeks before travel on bookings over €20,000. This halves the window on the larger payment. You can build a payment terms preset directly into your invoice templates so every booking triggers the right schedule automatically.

ZenPay supports custom payment terms (Net 7, 14, 30, 45, 60, or a custom number of days), and recurring or staged invoices can be configured to auto-send at a set local time so the balance invoice goes out exactly when your schedule says it should, not when you remember to send it.

Step 4: Use shareable invoice links so clients pay the moment the invoice lands

A deposit invoice that sits unread for 4 days is 4 extra days of FX exposure on your end. ZenPay generates a short shareable link for every invoice, so clients open one URL and pay, no portal account needed. QR codes on the invoice itself support bank transfer, PIX, WeChat Pay, and Alipay, covering most of your international client base.

Faster payment collection is not just a cash flow win. On a currency that is moving, four fewer days of exposure is a real number.

How to handle refunds and cancellations without the FX chaos

Cancellations are the scenario that turns FX risk from a nuisance into a genuine loss. A client books in GBP, the rate moves, and now your refund policy is being tested by a figure that looks different in your operating currency than it did at booking.

Two practices help:

1. State the refund in the original invoice currency. Your deposit invoice says "Deposit: £4,800. Non-refundable within 60 days of travel." The refund, if any, is £4,800. Not the EUR equivalent at today's rate. This eliminates a potential dispute and your own FX exposure on the refund.

2. Track partial payments against the booking, not in aggregate. If a client paid a 25% deposit and the cancellation policy returns 50% of that, you need to know exactly what was received, in what currency, and on what date. ZenPay's per-invoice payment tracking logs partial payments with dates, so you are working from a clean record, not reconstructing from bank statements.

Putting it together: a booking's FX journey

Take a €32,000 Tuscany villa group trip for 14 people. The itinerary involves a EUR-denominated villa (easy), a USD wine experience vendor, and GBP-denominated airport transfers for the UK-based group.

With a structured approach:

• Send the deposit invoice in GBP (client's currency), collect £4,000 into the GBP wallet
• Send the balance invoice in GBP 8 weeks before travel, collect £12,000 into GBP wallet
• Convert the precise USD amount needed for the wine vendor when you are ready to pay, not before
• Pay the GBP transfer company directly from GBP wallet balance: zero conversion

The EUR villa? If the client paid in EUR, pay it from the EUR wallet. If not, one conversion at a moment you choose. The point is that you are making deliberate currency decisions, not reactive ones forced by a deadline.

That is the practical answer to how to handle FX risk on client deposits when you do not have a treasury team: hold currencies longer, convert deliberately, and use tooling that shows you the exposure clearly enough to act on it.