AI summaries often overstate spending because a refund, a failed UPI reversal or a cashback appears as a separate credit, and nothing tells the assistant it cancels an earlier debit. The fix is to link each credit to the spend it undoes, so net spending shows what you really paid. A prompt, a rule and a quick manual match will cover most cases.
How do refunds distort a total?
Say you buy a pair of shoes for ₹3,200 and return them. Your bank statement shows a debit of ₹3,200 and, days later, a credit of ₹3,200. If the summary only adds up debits, it reports ₹3,200 spent. The real figure is zero. If it treats the credit as income, your income looks higher too. Either way, the picture is wrong.
Which kinds of credits cause trouble?
| Type of credit | What it looks like | What it should do |
|---|---|---|
| Product refund | Credit from the merchant, often days later | Reduce the original category |
| Failed UPI payment reversal | Debit and credit of the same amount, close in time | Net to zero |
| Cashback or reward | Small credit labelled cashback | Reduce spending in that category, or be shown separately |
| Chargeback or dispute credit | Credit after a complaint | Reduce the original spend |
| Refund after cancelling a booking | Part of the amount returned | Reduce spending by the part returned |
Why does an assistant miss them?
It reads each row on its own. A credit with the narration Refund has no category of its own and no obvious partner. It may be called Income, Other or Miscellaneous. A failed UPI payment is the hardest case, because the debit and credit can have different reference numbers and may even sit on different dates. Unless the assistant is told to look for pairs, it does not.
How do I match them to the original spend?
- Look for credits whose narration includes words such as refund, reversal, revoked, cashback or returned.
- For each one, search for a debit with the same amount in the previous few days to weeks, from the same merchant if the name is available.
- Give the credit the same category as that debit, so it cancels out in the category total.
- For a partial refund, apply it to the same category and check that the remaining amount is what you actually paid.
- Keep any unmatched credit in a separate category, such as Refunds to check, until you can find its partner.
For an assistant, a prompt along these lines works well: if a credit looks like a refund or reversal, find the earlier debit with the same amount and merchant, give it the same category with a negative effect on spending, and list any credits you could not match.
What about cashback?
Cashback is a small reward, so treat it consistently. Either reduce the spending category it relates to, or keep a separate category called Cashback and rewards and report it on its own. Mixing both approaches makes monthly comparisons confusing.
How can a tracker help with this?
Where a tracker lets you set rules, a rule for narrations containing refund or reversal can give those credits a consistent category, which you then review. SpendixAI also has a Possible duplicate charges report that lists the same amount to the same merchant within two days, which is useful when a failed payment and a retry both show up. Still check refunds yourself, because they are the rows where a quick look matters most.
A monthly check
- List all credits that are not salary or income.
- Match each to a debit, or note it as unmatched.
- Confirm net spending in the affected categories.
- Re-check unmatched credits next month, since some refunds arrive late.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

