Bank statements

Why your expense app balance does not match your bank balance

Expense app balance not matching your bank? Find the usual causes, how to reconcile line by line, and what to fix first, with a worked rupee example.

Editorial illustration for Why your expense app balance does not match your bank balance

An expense app balance rarely matches the bank because the two are counting different things: the bank counts every posted entry, while the app only knows what you imported or typed in. The usual culprits are a missing statement period, an opening balance that was never set, a duplicate row, or a transfer recorded on only one side. Reconciling takes about fifteen minutes once you know where to look.

What an expense app balance actually is

A tracker does not read your bank in the background. Its balance is a running sum: the starting figure you gave it, plus credits, minus debits, for the rows that exist inside it. If one row is absent, the total drifts by exactly that row. That is useful, because it means the gap is always explainable by specific entries.

SpendixAI works this way too. It has no bank connection and does not read SMS, so its numbers come from statements you upload as PDF, CSV or Excel and expenses you add by hand. Each transaction keeps the account you picked before importing, which is what lets you compare one account at a time.

Step-by-step: find the gap

  1. Pick one account and one closed period, for example 1 to 31 October, rather than the whole year.
  2. Note the bank's closing balance for the last day of that period from the statement itself.
  3. Note the bank's opening balance for the first day.
  4. In the app, filter the same account and the same dates and total the credits and debits separately.
  5. Check: opening balance + credits - debits should equal the closing balance. The difference is your gap.
  6. Search the statement for an entry of exactly the gap amount, or half of it, or a pair that adds up to it.

A worked example with made-up numbers

Say the statement shows an opening balance of ₹42,000 and a closing balance of ₹38,650 for October. In the app you find credits of ₹60,000 and debits of ₹63,200. Opening plus credits minus debits is 42,000 + 60,000 - 63,200 = ₹38,800. The bank says ₹38,650, so you are ₹150 apart.

Scan the statement for ₹150 and you find a debit for a small account charge posted on 31 October, after the file you imported was downloaded. Add it, or re-download the statement and import again, and the two figures agree.

The common causes, in order of how often they bite

CauseHow it shows upWhat to do
Missing periodGap equals a whole day or week of activityCheck import history for dates with no rows; upload the missing statement
Wrong opening balanceGap is constant every monthSet the starting figure once as of the first day tracked
Duplicate importGap equals a row you see twiceDelete the extra row; review the possible-duplicate flags
One-sided transferGap equals an amount moved between two of your accountsRecord both legs, one debit and one credit, on their own accounts
Cash or wallet top-upMoney left the bank but the wallet account is emptyAdd the matching entry to the wallet account

Why does the gap keep returning every month?

A gap that repeats at the same size points to the opening balance. A gap that changes each month points to rows going missing, often because a statement was cut at a date that did not match the previous one. Download statements for whole calendar months and keep a short log of which month you imported for which account.

Keeping the balance honest from now on

  • Import statements monthly, on the same day, for every account.
  • Choose the account before each import so rows land where they belong.
  • After each import, compare closing balances for that account before moving on.
  • Review rows before saving; SpendixAI lets you check imported rows first and flags possible duplicates.
  • Keep cash spends in a separate cash account so they never pollute a bank account's total.

When the difference is small, and when it is not

A gap of a few rupees is often a rounding or charge entry; a gap of thousands is almost always a missing or doubled row. Treat them differently. For a small gap, add a single adjustment entry with a clear note and move on. For a large gap, stop importing new data until you have found the cause, because every new month will inherit the error and bury it deeper.

It also helps to reconcile credit cards separately. A card's balance is what you owe, not what you hold, so the sign works the other way: purchases raise it and payments lower it. Mixing that logic with a savings account is a classic way to end up with a mismatch that is really just a sign error.

If you still cannot explain a gap after matching every row, ask the bank for a statement for that exact period and compare entry by entry. Do not chase a gap of a few rupees for hours; note it as an adjustment and carry on.

SPENDIXAI JOURNAL

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

Explore your reports