Multi-Currency Expense Management: Practical Playbook for Global Teams

If your team operates in more than two currencies and you are still relying on bank-converted card statements, you are losing 2-4% of your card spend to FX markup every month, and you are reconciling against numbers nobody can audit.

The core problem

A Turkish team buys a 100 USD AWS subscription on a TL corporate card. The bank converts at the daily rate plus a markup, charges the card in TL, and the statement shows a TL number. The receipt shows USD. The vendor invoice shows USD. The GL needs both. Three sources of truth, and the bank's TL number is the one nobody can independently verify.

Now multiply by 50 vendors, 200 transactions a month, and four currencies. This is why month-end takes a week instead of a day.

The four principles of good multi-currency

1. Charge the card in the currency of the receipt. If the vendor invoices in USD, the card transaction should clear in USD, not in your local currency. This eliminates the FX conversion at swipe time. Your platform holds a USD balance and settles in USD.

2. Record at mid-market rate, mark up explicitly. If you must convert, use the published mid-market rate (ECB, OANDA, or central bank) and record the markup as a separate line item. This makes FX cost auditable. "We paid 3% above mid-market in March" is a finance KPI you can actually manage. "The bank converted at some rate" is not.

3. Hold balances in your top three currencies. Most global teams have a primary currency (TRY, EUR, GBP, AED, depending on home base) and two or three operational currencies (typically USD plus one of EUR or GBP). Hold balances in all three. The cost of carrying balances is tiny compared to the FX savings.

4. Pay vendors in their currency. Sending a wire to a US vendor in TL forces them to convert and bill you back the difference. Sending it in USD removes the round trip entirely.

The accounting problem

Even with these principles in place, the GL still needs a single reporting currency. The right pattern:

• Record transactions in their original currency (the natural transaction currency).
• Capture an FX rate at transaction date for translation.
• Translate to reporting currency for the financial statements.
• Maintain an FX gain/loss account that captures the difference between transaction-date rate and settlement-date rate.

This sounds heavy but every serious accounting system supports it. The mistake teams make is forcing every transaction into the reporting currency at the source, which destroys the original-currency audit trail.

What to look for in a platform

A multi-currency-native platform should:

• Issue cards in multiple currencies, not just convert at swipe.
• Hold balances in multiple currencies without round-trip FX.
• Show transactions in original currency by default, with translated value as metadata.
• Export GL data in both currencies for clean accounting.
• Use a published reference rate (ECB or equivalent), not a proprietary one.
• Show the FX markup explicitly per transaction.

Platforms that "support multi-currency" but secretly convert everything through a single base currency are not multi-currency native. They are single-currency with a translation layer, and they will cost you 2-3% per transaction in invisible FX.

Practical setup for a Turkish team

A typical Istanbul-based team with EU customers and US vendors should run:

• TRY primary (payroll, Turkish vendors, taxes)
• USD secondary (US SaaS, AWS, OpenAI, US travel)
• EUR tertiary (EU vendors, EU travel)

Three balances, three card products, three GL accounts. The receipts match the transactions. The accountant matches the GL. Month-end takes the same time whether you have 50 transactions or 500.

The cost of doing nothing

A 30-person SaaS team spending 25,000 USD/month on international vendors through a TL-only card loses roughly 600-1000 USD/month to FX markup. That is 7,000-12,000 USD per year of pure waste, going to the bank for a service the team did not ask for. The platform fee to fix it is typically 30-50 USD per user per month. The math is obvious.

What we recommend

Audit your last three months of card and wire transactions. For each one, find the FX markup (compare the bank's rate to the mid-market rate on the transaction date). Sum it up. If it is more than a quarter of your platform cost, switch. If it is less, you are too small for this to matter yet, but flag it in your six-month review.