Getting started

PocketGuard not working: when the numbers are wrong, check this first

PocketGuard not working or showing a balance that looks wrong? Reconcile the app against your bank statement and use the size of the gap to find the cause.

Editorial illustration for PocketGuard not working: when the numbers are wrong, check this first

Reconcile a figure that looks wrong in a budgeting app like PocketGuard instead of trusting it or ignoring it. Open your bank statement, compute the balance yourself, and compare. The size of the difference usually points to the cause, and you can tell the app's support exactly what is off.

Step one: your own balance, from the statement

Take the opening balance for a period, add every credit, subtract every debit, and you should land on the closing balance printed on the statement. If your bank statement does not agree with itself, contact the bank. If it does, you have a number you can trust.

Step two: compare it with the app

Say the app shows ₹18,400 available, while your statement's balance minus a bill you know is due says ₹17,150. The difference is 18,400 minus 17,150, which is ₹1,250. Now use the size of the gap.

The gap looks likeLikely causeTry
Exactly one transactionA pending or recent item not countedFind that amount on the statement
Exactly double a transactionA duplicate in the appSearch for two identical rows
Equal to a transfer between your accountsTransfer counted as spending or incomeCheck how the app treats transfers
A round amount like ₹1,000A manual adjustmentLook for manual entries
Unexplained and growingSync stopped some time agoCheck the last updated date

In the example, the ₹1,250 could be one card payment that has not been counted yet. Search your statement for 1,250 and see.

Step three: is it the data or the settings?

  • Look at the last time the app updated and compare it with your latest statement line.
  • Check that every account you use is included.
  • Look for rows in an uncategorised bucket that may be skewing a category.
  • Check whether recurring bills are counted twice, once as a bill and once as a payment.
  • Look at the app's help for how it defines the number it is showing, since the definition may differ from your bank's balance.

What to tell support

  1. The figure the app shows and the figure you calculated.
  2. The date and statement line you used.
  3. The gap in rupees and what you tried.
  4. A screenshot of the app screen.

Why bring a statement into the picture

A statement is the one document you can check without trusting any app. SpendixAI is built around that. You upload a statement as PDF, CSV or Excel, choose the account first, and review the rows before they are saved, so every number in your totals can be traced to a line. It does not connect to your bank, so it can only be as current as the statement you upload. Reports are estimates, particularly for GST inside spending, so confirm with invoices and a CA.

When is a small gap normal?

A gap of a few rupees can come from rounding, or from a charge that was shown as a tiny pending amount before it settled. A gap that is the size of a whole bill is different and worth chasing the same day. Whatever the size, write it down with the date, so that if it grows you can see when it started.

If you have more than one account, reconcile each one separately. A mismatch hidden in a savings account can look like a spending problem in the total, and checking account by account shows you straight away which one is out.

A quick routine

  • Once a month, compute opening plus credits minus debits.
  • Compare against the closing balance on the statement.
  • Compare against the app and write down any gap.
  • Chase any gap bigger than a few rupees the same day.
  • Do not delete data to make a number fit.
SPENDIXAI JOURNAL

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

Explore your reports