Choose the base currency by asking which currency your next year of statements will be in, not which currency feels like home. Once the app has stored transactions, changing the base is often impossible, so a careful choice on day one is worth more than a clever workaround on day four hundred.
The worked examples are in euros and entirely invented. They show a method; they say nothing about any country's banking or tax rules.
What question should you ask before you commit?
- Which currency will most of my imported statements be in?
- Which currency do I use when I judge whether I can afford something?
- Am I likely to change my main bank account's currency in the next year?
If the answers disagree, the second question decides. Your judgement of affordability is the thing the app's totals are for.
What if you are about to move abroad?
Suppose you will relocate to a country with another currency in six months. The temptation is to set the future currency now. A better plan is to start with the base that matches today's statements, then, on the day your main account changes, open a new workspace in the new base. Your old workspace remains a record of the earlier life, and the new one starts clean.
What do you lose by keeping two workspaces?
You lose a single continuous chart. You gain accuracy, because no row is converted purely to fit the new base. If you need a combined view, export both and join them in a spreadsheet with one agreed rate for the old period, noting that it is an approximation.
A small example
| Row | Original | Base (€) |
|---|---|---|
| Monthly rent | €650 | 650.00 |
| Online course | $80 | 73.60 |
| Flight | £120 | 138.00 |
| Total | - | 861.60 |
With the assumed rates of 0.92 euros per dollar and 1.15 euros per pound, the dollar course becomes 80 times 0.92, or 73.60, and the pound flight becomes 120 times 1.15, or 138.00. The total is 650 plus 73.60 plus 138, which is 861.60 euros. Notice the euro base keeps rent exact; had you chosen pounds, rent would carry a conversion difference every month.
How does SpendixAI handle it?
SpendixAI asks you to choose the base currency before importing, and it cannot be changed once transactions exist. It is built around India and INR, so it is not a promise of availability in euro countries; the rule is shown here only because it illustrates why the choice needs thought.
What if the app lets you change the base?
Then you have more freedom, but the same questions apply. Find out whether past rows are recalculated at their original rates or at one new rate, because the two methods give different histories. If an app recalculates everything at today's rate, last year's spending will move whenever the rate moves. A stable record needs a rate fixed at the time of each transaction. Ask the app's help pages, or test with two sample rows, before you trust the result.
Does a joint household change the answer?
If two people share an account and one of you earns in another currency, the base should still follow the account that pays the household bills. The person with the foreign income enters it as foreign-currency rows. This avoids the awkward situation where half the household reads totals in a currency it never spends. Agree the base together, write it down, and revisit it only when the main account itself changes, not when a single payment arrives in a different currency.
Before you start entering data
- Write the base currency and the reason in one line.
- Add three sample rows in different currencies.
- Check the totals by hand.
- Save an export of the original rows.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

