Post metadata

Full draft below.

Full draft

Multicurrency Budgeting Without a Home Currency: How to Actually Do It

Every budgeting app starts with the same question: What is your home currency?

It sounds reasonable. But if you earn in dollars, pay rent in euros, keep savings in dirhams, and have a Bybit account in USDT, there is no correct answer. Pick dollars and every European expense gets distorted by whatever EUR/USD happened to be that morning. Pick euros and your income looks different every month based on nothing you actually did. Pick "none" -- and most apps either crash or push you toward a workaround that falls apart within a week.

This is the no-base-currency problem. It is not exotic. It is the daily reality for tens of millions of people who happen to live outside the geographic slice where Mint, YNAB, and Monarch Money were designed to work.

Here is how to actually think about it -- and what to look for in tools that will not fight you on it.

Why "home currency" thinking breaks your budget

The traditional model assumes one ground truth: one currency you earn in, one you spend in, one that means something to you. You make $5,000 a month. You spend $4,200. You saved $800. Clean.

That model collapses in three common situations.

1. Income and expenses are in different currencies. You earn in USD but live in a country where daily life runs in local currency. Forcing everything through a dollar conversion produces monthly budget numbers that swing with the exchange rate, not your actual behavior. You did not overspend on groceries this month -- the local currency weakened. Those are different problems requiring different responses.

2. You are tracking multiple pots that should stay separate. A savings account in EUR for a property purchase. A USD account for freelance income. A USDT wallet for crypto. Converting everything into one number loses the information you actually need. Knowing your "net worth is $84,000" tells you nothing about whether you can cover rent in euros next week.

3. You live in a high-inflation country. Pick local currency as your base and the graph on your savings looks fine in nominal terms -- until it suddenly is not. Pick a hard currency as base and half your transactions look like exchange-rate noise. Neither view tells you the thing you need to know: are your real-terms expenses under control?

The apps that handle this well separate two concepts that most tools conflate: reference currency (what you display summaries in) and base currency (the structural unit your budgets are enforced in). Changing your display currency should not rewrite your history. Sadly, it usually does.

Three approaches that actually work

1. Per-account currency, no forced consolidation

The cleanest model: each account holds its own currency and you track balances per account rather than rolling everything into a single number. Budgets are set per currency, not cross-currency. You have a EUR grocery budget, a USD subscription budget, a USDT savings target. Net worth can be shown in any reference currency you choose -- but that is a display choice, not a structural one. Changing it does not change your data.

This requires an app that genuinely separates reference currency from structural base. Most do not.

2. Parallel ledgers

Keep a separate budget view for each economic context. Your UAE life runs in a dirham budget. Your European travel is tracked in EUR. Crypto is recorded in USD. These do not merge -- they run in parallel. You cross-reference manually when you need a full picture, or the app shows a net worth roll-up clearly labeled as approximate.

More overhead, but honest about the approximation. The number you see is not hiding behind a misleading false precision.

3. Transaction-level currency with preserved historical rates

Every transaction is recorded in its actual currency at the actual rate on the day it happened. That historical rate is locked -- you do not retroactively reprice a 2023 euro expense at today's EUR/USD. Summaries can be displayed in any reference currency, but the underlying data is always the real-world amount in the real-world currency.

This is the most powerful approach if the app supports it correctly. My honest take: most do not bother.

What to actually look for in an app

The marketing language around multicurrency is vague enough to mislead. "Supports multiple currencies" can mean anything from "you can log a transaction in USD" to full per-account currency isolation with historical rate preservation. A few questions that cut through it:

Can you set a budget in EUR without it being a conversion of a USD budget? If yes, you have real per-currency budgets. If no, you have a single-currency budgeting engine with a cosmetic wrapper.

Does changing your display currency rewrite historical data? If your expense history from last year changes when you flip from EUR to USD, the app is repricing history. That means the historical numbers are meaningless -- they shift with today's exchange rates, not the rates that existed when you spent the money.

What happens with accounts that do not fit traditional currency slots? A USDT balance is not quite a currency in the traditional sense. Does the app handle this gracefully, or does it force you to pick a proxy and pretend?

Where does your transaction data come from? Apps that require live bank login credentials (Plaid, Open Banking) are limited to countries where those aggregators operate. If your bank is not on the list, you simply do not exist. Apps that accept PDF statements, CSV exports, or forwarded bank emails work with any bank in any country -- including the ones that will never be added to an aggregator's partner network.

One honest answer

I built WIMM (wimm.my) because I spent too long fighting apps that were not built for how I actually live.

No bank login. Ever. You feed it PDF statements, CSV exports, forwarded bank emails, or receipt photos -- the AI parses them and you review every import before it touches your ledger. Each account holds its own currency. Net worth is displayable in any of 50+ currencies, including BTC and ETH. Budgets can be set per currency without forcing a conversion to a single base.

For logging expenses without opening a laptop: there is a Telegram bot. Text it what you spent -- or send a voice note -- and it lands in your ledger with the right category. If you use Bybit, you can connect it via read-only API keys so your exchange balance shows alongside your bank accounts. WIMM can never move your funds. Binance and OKX connections are coming.

The whole thing runs on Hetzner servers in Finland. There is a free tier, and a free trial if you want to see how it fits before committing. No credit card required to start.

It will not suit everyone. If you are a single-country household with Plaid-supported banks and one currency, there are cheaper, more polished tools built exactly for that setup. WIMM is for the people those tools left behind.

Bottom line

The "home currency" question is not neutral -- it bakes in an assumption that your financial life has one gravitational center. For a growing number of people, it does not. The apps that handle this well treat currency as a property of accounts and transactions, not as a global setting you pick once and live with forever.

Ask the questions above before committing to any tool. And if you find yourself faking a base currency just to make the numbers work -- that is not a you problem. That is the app's architecture showing its limits.

Claims lint (pre-file check)

All items pass. Risk rating: Claims/Money -- product capabilities are stated.

Why this / what to look for

Why this topic now: Every competitor ranking for "multicurrency budgeting" (Lunch Money, PocketSmith, Toshl) assumes the reader has a home currency and just wants to convert into it. None of them address the structural problem: what do you do when there is no single base? That gap is exactly WIMM's strongest differentiator. This post names the problem the reader already feels, explains the mechanics, and positions WIMM as one honest answer -- without overselling.

What to look for when reviewing:

1. The three approaches section -- do these match how WIMM actually works internally? If "per-account currency, no forced consolidation" is not quite accurate to the current build, flag it and I will revise.
2. The Bybit section -- stated as live with read-only API. Binance/OKX stated as "coming." Correct per the Claims Register; adjust if the product state has changed.
3. The CTA tone -- the "one honest answer" section opens with "I built WIMM" in first-person founder voice per the Voice Guide. If the GM prefers a softer or harder sell, indicate.
4. Length -- 1,050 words in the body. Within 800-1500 target.

Dedupe note

Checked against 9 prior SCRIBE Approval Queue items (Landing copy, Email sequence, vc.ru story, Founder Voice Guide, Why finance apps fail outside the US, Telegram expense logger, YNAB alternative for expats, Finance apps for Germany, Digital nomad finance setup) + 5 non-Idea/Brief Content Calendar rows (same five published posts). The keyword "multicurrency budgeting" and the angle of budgeting without a base currency are new -- not covered by any prior item in any status.