Getting started

Spending tracker with bank statement import: what to check

What to check before and after importing a bank statement into a spending tracker: the pre-import steps, a balance reconciliation and duplicate warning signs.

Editorial illustration for Spending tracker with bank statement import: what to check

A spending tracker with bank statement import saves you typing, but an import is only worth trusting if you check it. Before importing, choose the right account and period. After importing, reconcile: opening balance, minus debits, plus credits, should equal the closing balance. If it does, your tracker holds the same numbers as your bank.

Before you import

  1. Decide which account the file belongs to and make sure the tracker knows it. Mixing two accounts in one import hides which money moved where.
  2. Choose a date range that ends at a month boundary, so the next import does not overlap.
  3. Use the format your tracker accepts. Check what formats it lists and what it says about layouts it may not read.
  4. Keep the original file. If something looks wrong later, you can go back to it.
  5. If you have a multi-currency account, check that the tracker's base currency is set before you import, since in some tools it cannot be changed afterwards.

What should I look at in the preview?

A good import shows rows before saving. Scan the first ten and last ten. Dates should be in the right order, debits and credits should not be swapped, and amounts should not be off by a factor of ten, which happens when a comma or decimal is misread. Check any row with a very large or very small figure.

How do I reconcile after importing?

Say the statement shows an opening balance of ₹32,500, closing balance ₹27,880, and your tracker imported debits of ₹41,320 and credits of ₹36,700. Compute 32,500 − 41,320 + 36,700 = ₹27,880. It matches, so nothing is missing. If the tracker had shown debits of ₹40,820 instead, the result would be ₹28,380, ₹500 too high, and you would look for a ₹500 debit that was skipped.

MismatchCommon causeWhat to try
Total lower than bankRow skipped at a page breakCompare row counts by page
Total higher than bankRow imported twiceSort by amount and look for pairs
Debits and credits swappedSign misreadCheck the column mapping and re-import
Dates one month offDay and month swappedCheck the date format option

How do I spot duplicates?

Duplicates come from importing overlapping periods or the same file twice. Look for the same amount to the same merchant on the same or nearby days, and check the import history for repeated file names. Some tools flag possible duplicates for you, but the final decision should be yours, because two real purchases of ₹250 at the same shop on one day are possible.

What does SpendixAI do here?

In SpendixAI you pick the account first, then upload PDF, CSV or Excel files, singly or as a batch. Each transaction keeps its account, there is an import history with a status, and you get an Import failed notification if a file cannot be read. Possible duplicate imports are flagged, and a Possible duplicate charges report lists the same amount to the same merchant within two days. You review rows before they are saved, because not every layout will parse perfectly.

If the import fails altogether

If a file will not load, check three things: whether it is the right format, whether it is protected with an opening code that needs removing, and whether it is a scanned image rather than a text statement. A scan usually cannot be read as rows. In that case, download a fresh copy from your bank in another format, or enter the month by hand. Do not send your login details to anyone to get a file.

After you finish

  • Write down the reconciliation result for each month.
  • Categorise the largest uncategorised rows first.
  • Note any bank charges you did not expect and look them up in your account agreement.
SPENDIXAI JOURNAL

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

Explore your reports