An AI assistant can read your statement rows and list transactions that look different from your usual pattern, such as a merchant seen for the first time or a large round-number transfer. It cannot tell you whether any of them is fraud. Treat its answer as an ask-me-about-these list, and take anything you do not recognise to your bank, which can see what really happened.
What can an assistant honestly tell you about a transaction?
It can notice patterns in the text you pasted: this narration has not appeared before, this amount is far above the usual debits, this payment is exactly ₹50,000 while your other transfers are odd figures. It cannot see the other side of the payment, the device used, or whether you agreed to it. That is why the output should be questions for you, not conclusions about the payee.
Which prompts produce a useful list?
Paste three to six months of rows without your name, account number or balances, then try these.
- 'List every merchant or payee that appears only once in these rows and was not in the earlier months. Show date, narration and amount. Call this list First-time payees.'
- 'List debits that are exact multiples of 1,000 and above 10,000. Call this list Round transfers.'
- 'For each of my regular merchants, tell me the usual range of the amount, and list any debit that is more than double the top of that range.'
- 'If the rows have a time, list debits between midnight and 5 am. If they have no time, say so plainly instead of guessing.'
- 'Write each list as questions addressed to me, such as Do you remember paying this? Do not label anything as fraud, suspicious or safe.'
The fourth prompt matters because most statements show only a date, so the assistant must admit when it has nothing to go on.
How do you read the list it gives back?
| Signal | Common innocent reason | What to check first |
|---|---|---|
| First-time merchant | A new shop, an online order, a one-off bill | Your order emails and payment-app history |
| Round-number transfer | Rent, a loan repaid to a friend, a deposit | Your own notes or chat with the person |
| Amount far above usual | Annual renewal, a festival purchase, a bill with arrears | The bill or invoice for that month |
| Late-night debit | A late online order or an auto-renewal that runs overnight | The merchant's own order or renewal record |
What should you do about an unrecognised debit?
- Search the narration and the amount in your email, messages and payment apps; family members often explain half of these.
- Check whether the payee is a person or a business by looking at the name in your payment app's history, not by guessing from the narration.
- If you still cannot place it, contact your bank right away through the helpline or app route on your card or in your own banking app, and ask what their process is for a debit you do not recognise.
- Keep the date, amount, narration and reference number together while you wait.
What if the account is shared with family?
Joint accounts and family cards produce many first-time payees that are simply someone else's purchase. Before you treat anything as unusual, ask the other users to look at the list too. A short message with the date, amount and narration is usually enough, and it clears most items in minutes. Do not forward the whole statement; send only the lines you are asking about.
How often is it worth running this?
Monthly is enough for most people, right after the statement arrives, because early notice makes a query simpler to raise. If you keep your transactions in SpendixAI, a Possible duplicate charges report is one more list of candidates that costs no prompt-writing, though it covers only repeated charges, not first-time payees.
Keep a short note of anything you asked about and how it ended. In a few months you will know your own regular payees so well that the first-time list becomes short and quick to clear.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

