Two Currencies, One Truth: Tracking Money Across Borders
Most trackers assume every number you type is rupees. So a fortnight in Bangkok, or a salary in dirhams, turns a year of careful tracking into a year of unusable averages. The fix is three decisions: one home currency, the original amount kept forever, and the rate frozen on the day you spent.
You track every rupee for eleven months. Then you spend two weeks in Vietnam, come home, open your app — and the trip shows up as ₹8,400. Not because you spent ₹8,400, but because you typed the dong amounts in as though they were rupees and the app believed you. Eleven months of honest data now sit beside two weeks of fiction, and every average you look at for the rest of the year is quietly wrong.
This is not a niche problem. Indians travel more than ever, NRIs run two lives in two currencies, freelancers invoice in dollars and pay rent in rupees, and students are billed in one currency by a family earning in another. Yet most expense trackers still make one silent assumption: that every number you type is in the same currency as every other number. The moment that stops being true, every amount needs a currency and a date attached to it — or your tracker stops being a record of anything.
Chapter 1: Why a Second Currency Breaks an Ordinary Tracker
The first failure is the assumption itself. Type 350 into a tracker in Bangkok and it stores 350 — of whatever the app has decided your money is. THB 350 is roughly ₹950, so your dinner just got recorded at a third of its cost. Do that for fourteen days and the trip looks cheaper than a week of groceries at home. Nothing warned you, because from the app's point of view nothing was wrong.
The second failure is the manual conversion most people fall back on. You do the arithmetic in your head, round it, type in the rupee figure — and the original number is gone forever. Three months later, when your card statement says ₹1,013 for that dinner and your expense tracker says ₹950, you have no way to settle which is right, because the receipt's own number — THB 350 — was never stored. You didn't record an expense; you recorded your opinion of an expense.
The third failure is the sneakiest, and it belongs to the apps that do handle currency — badly. They convert on the fly at today's rate. It looks sophisticated until you notice that your March total is a different number in May than it was in April, because the rupee moved in between. A tracker whose past totals change is not a record. It's a live quote pretending to be history. Your bank statement, your memory and your app now disagree with each other by the week. When you only need one conversion right now, a currency converter is the right tool — a tracker has the harder job, which is remembering what the rate was.
Chapter 2: Five Ways People Handle Foreign Spending (Ranked Worst to Best)
Almost everyone who has travelled with a budget app has tried one of these. Only the last one survives contact with a real trip:
- 1. Typing the foreign number as if it were rupees (fails)The most common mistake and the most damaging, because it produces data that looks perfectly fine. A ¥3,000 lunch in Tokyo becomes ₹3,000 — wrong by roughly a factor of five, and completely invisible in a list of transactions. This doesn't only get the trip wrong; it poisons every category average the trip touches.
- 2. Not tracking at all while travelling (fails differently)"I'll take a break from tracking on holiday" is understandable and completely backwards. Travel weeks are usually the highest-spending weeks of your year, so switching the tracker off blanks out exactly the data you most need to plan the next trip. The spending doesn't disappear with the record — it reappears later as a credit-card bill you can't explain.
- 3. Mental conversion at a round rate (survives a day, not a fortnight)Deciding that ฿1 ≈ ₹2.5 and converting on the fly is fine for a coffee and hopeless for two weeks. Rounded rates drift, tired travellers do bad arithmetic, and the original amount still vanishes. It gets the order of magnitude right, which beats method one — and that is the most that can be said for it.
- 4. A separate spreadsheet for the trip (accurate but siloed)Meticulous travellers keep a sheet with local amounts, rates and rupee equivalents. The maths is sound. The problem is that it never rejoins the rest of your money: your annual food total, your savings rate and your category trends all still behave as though the trip never happened. Two truths, no picture.
- 5. One tracker, one home currency, rate frozen per transaction (best)A single app holds everything. Each expense keeps the amount you actually paid in the currency you actually paid it in, converts once at the rate on that date, and stores both numbers permanently. The trip reads correctly in the trip view and correctly in the annual view, and neither number ever moves again.
Chapter 3: The System — Home Currency, Original Amounts, Frozen Rates
Multi-currency tracking stops being complicated once three decisions are made. Make them once, and every foreign expense afterwards is as routine as a UPI payment at home.
Choose one home currency and never change it
Your home currency is the one your budgets, goals and salary planning live in — for most readers, the rupee. Every total, chart and budget line reports in it, no matter where the money was spent. Pick the currency you actually plan your life in, not the one you happen to be standing in.
For NRIs that usually means the currency you're paid in and pay rent in, with money sent to India treated as a transfer rather than an expense. If your long-term goals sit in India, keep a rupee view alongside — but only one currency gets to be home.
Keep the original amount on every expense
THB 350 must stay THB 350 in your records forever, with the converted ₹952 sitting beside it — not instead of it. The original amount is the only number that matches your receipt, your card statement and your memory. The conversion is a view of an expense; the original amount is the expense. Any tracker that throws the original away has destroyed evidence you may need months later.
Freeze the rate on the day you spent
The correct rate for a 14 March expense is the 14 March rate, captured once and stored on the transaction itself. Not today's rate. Not the trip's average. Once stored it never recalculates, so the March total you saw in March is still the March total in December. A month that has ended should never change its number again.
Record the rate you actually got, not the mid-market one
Google's rate is not your rate. Your card added a markup, the ATM charged a fee, the exchange counter took a spread — the real landed cost of ฿1,000 might be ₹2,680, not ₹2,600. Where your statement tells you the true cost, use that number. And always decline the shop's offer to bill you in rupees. That is dynamic currency conversion, and its rate is one of the worst you will ever be handed. Pay in the local currency, every time.
Give the trip its own space, then let it roll up
Log the trip in a dedicated trip space so you can see what the holiday itself cost, in both currencies, without hunting through a year of transactions. Those expenses still roll into your annual categories, so nothing is hidden — you simply get a clean answer to "what did Vietnam cost?" alongside "what did I spend on food this year?"
If you're splitting costs with the people you travelled with, the same principles apply to who owes whom — see our guide to splitting bills without ruining friendships.
Chapter 4: Three Rules for Cross-Currency Data You Can Trust
The system above only holds if you defend it. These three rules are what stop two currencies from becoming two versions of the truth. All of them work on the free tier — see what each plan includes if you want trips, family spaces and detailed reports on top.
1. Never re-convert history
Once an expense has a stored rate, it is finished. Bulk-updating old transactions to today's rate feels tidy and destroys the one property that makes a ledger useful — that it agrees with itself over time. If the rupee weakens next month, your past spending did not become more expensive. It already happened, at a rate that is now a historical fact.
2. Budget in your home currency, cap in the local one
Set the trip budget in rupees, because that is where the money came from. Then convert it once into a daily cap in the local currency — "฿2,500 a day" — because that is the number you can actually use at a counter without doing arithmetic. One budget, two units: rupees for the plan, local money for the decisions.
3. Flag travel months instead of hiding them
Two weeks abroad will spike your food and transport averages, and a spike you can explain is far better than one you can't. Tag the travel period so your analytics can show your baseline and your true spending side by side. The goal is not a flattering average — it is knowing which months were your normal life and which were not.
Two Currencies, One Set of Numbers
Home currency, original amounts, rates frozen on the day.
Nami keeps the amount you actually paid next to the converted figure, freezes the rate on the date of the expense, and rolls foreign spending into the same categories, budgets and reports as everything else. Log a meal in Bangkok by voice, fly home, and the year still adds up.
Conclusion
Multi-currency tracking sounds like an accounting problem and is really a memory problem. The receipt in your hand knows exactly what you paid; every step after that is a chance to lose it. Keep the original number, freeze the rate on the day it happened, and report everything in the one currency you plan your life in — and a trip abroad becomes just another fortnight in your data instead of a hole in it. Do it once and you will never again open your app in January wondering what those two weeks actually cost.