Getting started

Does the order you import statements in matter?

Does the order you import bank statements in matter? Mostly not for totals, but oldest-first makes balance checks and duplicate flags easier to follow.

Editorial illustration for Does the order you import statements in matter?

For your totals, the order rarely matters, because each row carries its own date and reports sort by that date, not by when you uploaded it. Importing oldest first still helps in practice: closing balances line up one after another, and possible-duplicate flags are easier to understand. If you uploaded out of order, nothing is ruined.

Why the order barely changes the numbers

A transaction is a row with a date, an amount, a description and an account. When SpendixAI imports a statement it saves those rows as they are. A report for April looks for April-dated rows, whichever file they came from and whenever you uploaded it. So uploading March before January will not turn January spending into March spending.

Two things are worth remembering: pick the right account before each upload, since every transaction keeps its account, and choose your base currency before the first import, since it cannot be changed once transactions exist.

So why bother going oldest first?

Because of how you, a person, check your work. A statement shows an opening and closing balance. The closing balance of January should be the opening balance of February. If you import in order, you can tick off each month against that chain and spot a missing statement straight away.

  • Gaps stand out. If January closes at one figure and February opens at another, a transaction or a whole statement is missing.
  • Duplicates make sense. When two statements overlap, the later one is the one flagged as repeating rows already there, which is easier to reason about.
  • Rules and history build up in time order, so your early corrections help the later months.

Three months uploaded out of order

Say you upload March first, then January, then February. These closing balances are invented for the example.

StatementOpening balanceClosing balance
January₹30,000₹42,000
February₹42,000₹35,500
March₹35,500₹48,200

Imported in the wrong order, all three still land on the right dates. Your March report shows March, and your January report shows January. The only thing you lose is the easy chain of checks while you work. Once all three are in, you can still compare each closing balance with the next opening balance on the paper or PDF statements, and everything should line up exactly as in the table: 42,000 to 42,000, and 35,500 to 35,500.

If it did not line up, say February opened at ₹41,000, you would know that ₹1,000 sits in a transaction you have not imported, or one that belongs to a different account.

What about overlapping statements?

This is where order and care matter more. If one statement covers 1 January to 15 February and another covers 1 February to 28 February, the rows for 1 to 15 February appear in both. SpendixAI flags possible duplicate imports, and import history shows each upload with its status, so you can see what came in and when. A separate report, Possible duplicate charges, lists the same amount to the same merchant within two days, which is useful for a different reason: it catches genuine double charges at the merchant, not just double uploads.

A sensible way to do it

  1. Download your statements for the period, one per account.
  2. Name or sort them so the oldest is first; batch upload lets you send several at once.
  3. Choose the account for each file before it goes in.
  4. Check the import history for anything marked failed, and look at your notifications for an Import failed message.
  5. Compare each closing balance against the next opening balance on your statements.
  6. Review the possible-duplicate flags before you start categorising.

If you have already uploaded in a muddle, do not redo it. Check the balances, look at the flags and carry on.

SPENDIXAI JOURNAL

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

Explore your reports