Tracking net worth across currencies: the mistake that quietly corrupts every expat's number

You hold an AED salary, a USD brokerage account, a flat back home priced in GBP, and a pension in your passport country's currency. Four numbers, four currencies. Your brain wants one answer, so it adds them. That sum is not your net worth. It's four unrelated quantities stapled together, and it drifts every time an exchange rate moves. For an expat that isn't a rounding detail; it's the difference between knowing where you stand and guessing. Many tools get the headline roughly right, then quietly corrupt the number somewhere downstream.

Adding the balances is a category error

Take 100,000 AED, 200,000 USD, and 150,000 GBP. Adding them to get “450,000” is the same mistake as adding 5 metres, 3 feet, and 2 miles and writing down “10”. The units are different, so the sum means nothing. A dirham is not a dollar is not a pound.

The only meaningful total is a two-step move: pick one base currency, convert every balance into it at today's rate, then add. Everything downstream depends on that conversion happening first, consistently, on every figure. Your savings rate, your debt-to-income, how many months of expenses you hold in cash: none of them are real until the currencies are collapsed into one.

One pair makes this feel safer than it is. The dirham is pegged to the dollar at 3.6725, and has been since 1997, so the AED and USD slices of your net worth move together. Everything else floats. Sterling, rupees, euros and yen reprice against your base every trading day, which means your net worth changes on days you neither earn nor spend a thing. That movement isn't an error to scrub out. It's real currency exposure, and you want to see it clearly instead of burying it under a bad sum.

The conversion has to reach every derived number, not just the headline

The visible total is the easy part. The damage happens in the numbers built on top of it. Your debt-to-income ratio is a sum of liabilities over a sum of income, both cross-currency. Your allocation percentages, your emergency-fund coverage, your Zakat base if you calculate one: every one is an aggregate across currencies. Convert once for the big dashboard number and forget it inside the debt ratio, and you get a figure that looks plausible and is wrong by exactly the currency mix you ignored. Those errors survive precisely because nothing about them looks broken.

One more failure mode is worth naming. If a single holding is in a currency the tool can't price at that moment, a naive “add, then convert” turns the entire total into NaN: one missing rate blanks everything. The correct behaviour is to skip the item that can't be priced, keep the rest of the total intact, and tell you one line was left out. Silently showing nothing, or silently showing a wrong number, are both worse than showing a slightly incomplete one with a note attached.

The trap: a snapshot can't be re-based later

When a tool saves “your net worth on 1 March was X”, that X is a single number computed in whatever base currency you were viewing at the time. The breakdown behind it, how much was AED, how much USD, how much GBP, is not stored alongside it. It's collapsed into one scalar and discarded. That's harmless right up until the day you change your base currency.

Say you tracked everything in USD all year, then switch your display to AED. A naive tool now has a chart full of USD-era numbers, a new AED axis, and no memory of the composition behind each point. So it does the only thing it can: multiply every historical value by today's USD-to-AED rate, roughly 3.67, and redraw. Every past month is suddenly about 3.67 times larger. The chart leaps more than 260% and congratulates you on your biggest gain ever, for a change that is purely cosmetic. You didn't get richer. You changed the label on the axis.

This is the phantom gain, and it cuts both ways. Switch from a large-number currency like INR or JPY back to USD and the same tool paints a catastrophic phantom loss. Neither event happened. The composition you would need to convert those old points honestly was destroyed the moment each snapshot was saved as a lone number, and no exchange rate can reconstruct it.

The honest fix is boring: stamp it, and set aside what you can't convert

The correct design has three moving parts, and none of it is complicated.

• Stamp every snapshot with its base. A point recorded while you were viewing USD is labelled USD, permanently. The number now carries the one piece of information the naive tool threw away.
• Normalize at comparison time, not by rewriting history. When you compare this month to last, convert both endpoints back to whatever you're currently viewing, using their stamps. Change your display currency and the axis re-labels; the shape of the line stays put.
• Quarantine what genuinely can't be re-based.Old points stamped in a base you no longer use, whose composition is gone, are not force-converted onto a single-unit chart. They're set aside, not plotted, and the tool tells you some history is hidden. Showing less is correct here. Drawing a confident line through numbers you can't legitimately convert is not.

The same rule guards the celebrations. “You crossed 1,000,000” should fire only when the before and after figures were both measured in the same currency. Otherwise flipping your base from USD to AED trips a fake milestone the instant the number sails past a round threshold it never actually reached.

What to do about it

• Pick your base currency deliberately.Choose the one you genuinely plan and think in. For most UAE expats that's AED or USD, and because they're pegged, the choice between those two barely moves your headline.
• Enter each holding in its native currency.Put the GBP flat in as GBP, the US brokerage in USD. Pre-converting in your head discards the original and bakes in a stale rate you'll never remember to update.
• Distrust any chart that jumps when you change the display currency. That leap is the tell. A correct tool changes the numbers on the axis and leaves the trajectory alone. A jump means it re-based history it had no right to touch.
• Treat switching your base as a view change, not an event. You're allowed to reconsider your base currency; just know it is a change of lens. It should never register as a gain, a loss, or a milestone.

This is general education about measuring money across currencies, not investment or tax advice. The point is narrow and unglamorous: get the unit right before you trust any number built on top of it.

K25x is multi-currency native. Enter each asset in its own currency and every headline — net worth, debt-to-income, savings rate — converts to the single base you choose. Each net-worth snapshot is stamped with the base it was computed in, so changing your display currency re-labels the chart instead of inventing a gain, and any history that can't be honestly re-based is set aside rather than silently redrawn.