If you split a trip across borders, the first thing that breaks in most expense apps is currency. You paid for the hotel in lira, your friend covered the flights in dollars, and the group settles up in euros. The question people actually type into a search box is simple: does Splitwise handle multiple currencies, and does it do it correctly?
Short answer: it handles them, but with two catches that matter more than the marketing implies. This is a fact-based walkthrough of what Splitwise does with foreign currencies, what it costs in 2026, where the math quietly goes wrong, and what a correct multi-currency split looks like.
Yes, Splitwise supports multiple currencies — with an asterisk
You can log an expense in any currency Splitwise supports, and the app will store it in that currency. So far so good. The two asterisks:
1. Automatic conversion is a Pro feature. On the free tier you can record an expense in USD and another in TRY, but Splitwise won't convert them into a single group currency for you — you see a list of balances in mixed currencies. To get one consolidated number ("you owe €240"), you need Splitwise Pro (≈$3/month or ~$30/year as of 2026). Currency conversion sits behind the same paywall that arrived alongside daily expense limits and banner ads.
2. It converts at the rate when you look, not the rate when you paid. This is the subtle one. When Splitwise does convert, it tends to apply a current exchange rate rather than locking the rate to the date of each expense. Open the group next week and the FX market has moved, so the converted totals drift even though nobody spent anything new.
That second point is where money silently leaks, so it's worth slowing down on.
Why "convert at today's rate" is the wrong rule for splitting
There are two moments you could convert a foreign expense:
- At the date of the expense — the rate the day the money actually left someone's account.
- At settlement (or every time the app renders) — a later, different rate.
Only the first is fair. Here's the failure case in numbers:
| Expense | Date | Original | Rate that day | Fair base (EUR) | | --- | --- | --- | --- | --- | | Hotel Istanbul | Jun 14 | 8,400 TRY | 35.0 TRY/EUR | 240.00 | | Re-converted Jun 28 | — | 8,400 TRY | 36.2 TRY/EUR | 232.04 |
The friend who fronted 8,400 TRY paid the equivalent of €240 on the day. If the app re-converts at settlement (36.2), the group only pays them back €232 — they eat the €8 FX move through no fault of their own. Multiply that across a dozen cross-border expenses and the person who fronted the most foreign spend systematically loses money. Nobody is cheating; the tool is just using the wrong rule.
The correct rule, the one accountants use: convert each expense at the reference rate on the day it occurred, store both the original and converted amounts, and never re-convert. We unpack the full system in multi-currency budgeting on the road — the same per-date rule applies whether you're budgeting solo or splitting with a group.
What this costs you in practice
Two real costs stack up when you split a multi-currency trip on Splitwise's free tier:
- The paywall. No automatic conversion without Pro. For a one-week trip, paying for a subscription to do basic math feels backwards.
- The FX drift. Even on Pro, re-conversion at the current rate means whoever fronts foreign charges absorbs the currency risk.
For a group that crosses one border, this is annoying. For digital nomads rotating through three or four currencies a month, it's a recurring source of "wait, that doesn't add up" — exactly the friction expense apps are supposed to remove.
What a correct multi-currency split looks like
A tool built for cross-currency groups should do four things by default, with no upgrade:
- Pin the rate per expense. Convert each entry at the ECB reference rate for that date and freeze it. The free Frankfurter API exposes those rates back to 1999 — there's no reason to charge for this.
- Show both amounts. The original (what was actually paid) survives any dispute; the base (converted) lets the group sum across currencies.
- Settle in one base currency. Pick the group's home currency once; every balance resolves to it.
- Simplify the debts. Net the tangle of who-owes-who down to the fewest transfers — see settle a group trip in the fewest payments.
This is exactly the gap we built NomadCrew around. Multi-currency is free on day one — 38 currencies, per-date rates, both amounts stored, no daily limit, no ads. You log the hotel in lira, the flights in dollars, and the group sees one honest number in euros. For the broader field, see Splitwise alternatives in 2026, and if you specifically want the two-app showdown, Splitwise vs Tricount.
FAQ
Does Splitwise convert currencies automatically? Only on Splitwise Pro. The free tier stores expenses in mixed currencies without consolidating them into one balance.
What exchange rate does Splitwise use? It applies a current market rate at the time of conversion rather than locking the rate to the date of each expense, so consolidated balances can drift as FX moves.
Is there a free way to split expenses across multiple currencies? Yes. Apps built for travel — NomadCrew among them — convert at the per-date reference rate and consolidate balances without a paywall. See the step-by-step method.
Which rate is "fair" for a group? The rate on the day the expense was paid. Re-converting at settlement shifts FX risk onto whoever fronted the most foreign spending.