AI and MCP

Bank SMS alerts to expense entries: prompts that parse them

Prompts that turn pasted bank SMS debit alerts into a date, amount, merchant and mode table, with masking tips and checks against your statement.

Editorial illustration for Bank SMS alerts to expense entries: prompts that parse them

To turn bank SMS alerts into expense entries, copy a batch of debit alerts, mask the account digits, and ask an AI assistant to return a table with date, amount, merchant and payment mode. Then count the rows in and out and compare the total with your statement. This is a manual workaround; SpendixAI itself does not read SMS.

What do you do before pasting anything?

Alerts carry more than you need. Remove names, mobile numbers, links and anything that looks like a reference or account identifier. Replace the account tail with XXXX. Leave out any message that mentions an OTP, and any with a balance you do not want in a chat. Paste only debit alerts, ten to thirty at a time.

Which prompt parses them?

'Below are bank SMS debit alerts, one per message. Return a table with columns: date in DD-MM-YYYY, amount as a number, merchant or payee as written, mode (UPI, card, NEFT, IMPS, ATM or Unknown), and a Notes column. If a field is missing, write Unknown. Never guess a merchant. At the end, tell me how many alerts you read and the total of the amounts.'

Here are three invented alerts and the rows they should produce:

Alert text (masked)DateAmountMerchantMode
Rs 450.00 debited from A/c XXXX on 05-03-25 to VPA ramesh@bank, UPI05-03-2025450RameshUPI
Rs 1,299.00 spent on Card XXXX at ONLINE STORE on 06-03-2506-03-20251299Online storeCard
INR 5,000.00 withdrawn at ATM on 07-03-2507-03-20255000ATMATM

How do you check the result?

  1. Count: if you pasted 24 alerts, the table must have 24 rows.
  2. Total: add the amount column in a spreadsheet with =SUM($D$2:$D$25) and compare it with the total the assistant stated.
  3. Dates: scan for wrong years or swapped day and month; alerts often use a two-digit year.
  4. Statement: compare the total with the same dates on your bank statement. Differences point to missed alerts or non-SMS debits.

Be watchful with amounts that use commas, such as 1,299.00, because a sloppy parse can turn them into 1 or 299.

A few more parsing traps are worth knowing about. Alerts for credits, refunds and reversals often look similar to debits, so tell the assistant to keep only lines that say debited, spent or withdrawn. Merchant names can be cut off mid-word. A UPI alert may show a handle and not a business name, and then the merchant is Unknown. Finally, a single transaction sometimes triggers two messages, one from the bank and one from a payment app, so watch for the same amount appearing twice close together.

What if alerts and the statement disagree?

The statement is the record. Alerts can arrive late, be missed, or describe holds that never settled. Use alerts for same-day visibility and treat the statement as final.

Is it worth doing this at all?

For a month or two, maybe. Alerts give same-day visibility, which is handy when you are watching a tight budget or following a trip. Over a year, copying and checking messages costs more time than importing the statement once a month. Keep the habit if you enjoy seeing money move as it happens, and drop it when the checking starts to feel like a chore.

How do the rows get into your tracker?

In SpendixAI you can add expenses by hand, one or several at once, so a cleaned table of alerts can be entered in a batch. Choose one source per period: if you enter alerts for the month and then import the statement as well, the same payments exist twice. Importing the statement reviews rows before saving and flags possible duplicate imports, which helps, but it is simpler to enter alerts only as a stopgap until the statement is available.

Over time the better habit is to rely on the statement import, which brings in every debit including those you never saw a text for, and keep manual entry for cash.

SPENDIXAI JOURNAL

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

Explore your reports