Travel and vehicles

Wrong base currency in an expense app? How to rebuild in Australian dollars

If your expense app will not change base currency, here is how to export, rebuild and verify your history in Australian dollars without losing original amounts.

Editorial illustration for Wrong base currency in an expense app? How to rebuild in Australian dollars

If you chose the wrong base currency and the app will not change it, the fix is a rebuild: export your rows with their original currency and amount, set up a new workspace with the right base and re-import. The rebuild is safe only if your export keeps the original figures, so check that before you delete anything.

The example uses Australian dollars with made-up numbers and describes method, not any bank or tax rule.

Step one: look at what the export contains

Open the export in a spreadsheet. For each row you want a date, a description, an original amount, an original currency and, ideally, the converted amount and the rate. If only a converted figure is there, you cannot rebuild precisely, and you need another source, usually your bank statements.

Step two: protect the original

  • Save the export under a new name with today's date.
  • Make a second copy in a different folder.
  • Do not edit the first copy.

Step three: set up the correct base

Create a new workspace or account, choose Australian dollars as the base before adding any data and add your accounts again. This is the step you cannot undo later, so pause and check the setting before importing.

Step four: re-import and compare

Import one month first. Compare the new total against the old workspace's original-currency rows and against your statement. A small difference in converted amounts is expected, since rates may differ. A large difference means a row was missed or doubled.

CheckOld workspaceNew workspaceDifference
Rows in March84840
Total spend (A$)3,412.503,398.2014.30
Foreign-currency rows660

The 14.30 difference is 3,412.50 minus 3,398.20, and with six foreign-currency rows it can be explained by different rates. The row count matching is the stronger signal.

How do you handle the history before the rebuild?

Keep the old workspace, if the app lets you, as a read-only archive. If it does not, keep the export. You rarely need to look back at old rows, but when you do, you will be glad that the original amounts exist.

Can a spreadsheet do the same rebuild?

Yes, and it is a useful safety net. Keep a master sheet with columns for date, description, original amount, original currency, rate and base amount. The base amount is a formula: =C2*E2 if the original amount is in column C and the rate in column E. To change base in a sheet you replace the rate column and the formula recalculates every row at once. Doing this once in a spreadsheet also shows you how much a base change moves the totals before you commit to a new app setup.

How do you know the rebuild worked?

Pick three days at random from the old and new workspaces and match them row by row against your bank statement. Then compare the category totals for one month. If the categories agree within the rate differences you expect and the number of rows is identical, the rebuild is sound. If a category is off by a large amount, search for a duplicated import or a transfer between your own accounts that was counted as spending.

Rebuild checklist

  1. Export with original currency and amount.
  2. Back up the export twice.
  3. Create the new workspace with the right base.
  4. Import one month and reconcile.
  5. Import the rest.
  6. Archive the old data.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports