Getting started

A checklist for reviewing rows before saving a statement import

A two-minute checklist for reviewing transactions before saving an import: date range, row count, first and last rows, signs, junk rows, account, currency.

Editorial illustration for A checklist for reviewing rows before saving a statement import

Before you save a statement import, run a two-minute pass: confirm the date range, count the rows, look at the first and last rows, check the signs, remove obvious junk, and confirm the account and currency. Each check takes seconds and spares you a clean-up that can take an hour later.

Why review at all?

A tool that reads a file can be wrong in small ways: a swapped date, a total row mistaken for a transaction, an amount marked the wrong way. In SpendixAI you review the rows before they are saved, so this is the cheapest moment to fix them. After saving, every error has already flowed into your reports and budgets.

The checklist

  1. Date range: the earliest and latest dates should match the period you downloaded.
  2. Row count: compare with the number of entries on the statement, if it prints one.
  3. First row and last row: they should be the first and last transactions of the file.
  4. Signs: salary and refunds should be money in, and bills and shopping should be money out.
  5. Junk rows: remove headings, totals, balance lines and repeated page headers.
  6. Account: confirm the right bank, card or wallet is selected.
  7. Currency: confirm the base and row currency are what you expect.

What does each check catch?

CheckProblem it catchesTime it takes
Date rangeWrong month, swapped day and month10 seconds
Row countSkipped or doubled rows20 seconds
First and last rowsCut-off periods and carry-over lines10 seconds
SignsDebits shown as credits15 seconds
Junk rowsTotals counted as spending20 seconds
Account and currencyCard spending in a savings account, wrong currency15 seconds

Is the account and currency check really needed?

Yes, because these two are the hardest to see afterwards. Each transaction keeps its account, so a card statement saved into a savings account gives wrong balances and a muddled card report. Currency matters too: you choose a base currency before importing, and once transactions exist it cannot be changed. A foreign purchase should keep its own currency while the totals use a base.

What should I look at in the first and last rows?

These two rows are the edges of the file. The first row should be the earliest transaction of the period, and the last row the latest. If the first row is dated before the period, it is probably a carry-over from the previous statement and may already exist in your tracker. If the last row is an opening or closing balance, remove it.

A tiny worked pass

Say you imported a February file with 52 rows. The statement says February, but your first row is dated 31 January and the last row is a footer reading Total debits. That is two rows to leave out, so 52 - 2 = 50 real transactions. Your statement printed 50 entries, so the count agrees once the carry-over and the footer are gone.

Make it a habit

The checklist works best when it is the same every time. Keep it somewhere you will see it, such as a note on your phone, and tick through the seven points in order. Over a few imports you will find that you can see most problems at a glance: dates out of order, a suspicious row at the bottom, a salary marked as spending. If you share the task with a family member who also uploads statements, show them the list so both of you check the same things. Consistency matters more than speed, because the errors it catches are the ones that are hardest to find later.

Spending two minutes here is worth more than any later tidy-up. If you are loading many months, do the same pass on every file, and keep a note of the periods you have already imported so the same dates do not come in twice.

SPENDIXAI JOURNAL

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

Explore your reports