To add five expenses by chatting, connect your tracker to Claude or ChatGPT through MCP with permission to create entries, then send one clear message listing the five items with date, amount, merchant and category. Ask the assistant to show what it will create before it creates anything. That one habit prevents most mistakes.
What you need in place first
- A tracker that can be connected to the assistant, with a scope you choose (SpendixAI offers this through MCP and lets you start read-only)
- A wider scope that allows creating entries, switched on only for this task
- A base currency and an account chosen for each payment
- A list of your category names so the assistant uses yours rather than inventing new ones
A prompt pattern that works
Write the items as a compact list and state your assumptions. Here is a hypothetical Saturday for a developer working from home.
| Item | Amount | Account | Category |
|---|---|---|---|
| Metro card top-up | ₹500 | UPI wallet | Transport |
| Filter coffee and idli | ₹180 | Cash | Food |
| Domain renewal | ₹1,150 | Credit card | Work tools |
| Auto to the co-working space | ₹240 | Cash | Transport |
| Charger cable | ₹650 | Credit card | Electronics |
The five add up to ₹2,720 (500 plus 180 plus 1,150 plus 240 plus 650). Before confirming, ask the assistant to read the list back with the total. If it says ₹2,720, proceed. If it says anything else, one row was misread, and it is cheaper to fix it in the draft than in the ledger.
Why ask for a dry run?
Language models are good at structure and weak at silent consequences. A dry run turns a vague promise into a checkable list. It also gives you a chance to catch the usual slips: a date taken as today instead of Saturday, an amount with a rupee sign read as text, a cash item filed under the card.
What can go wrong, and the fix
- Wrong year or month on a date: always state the full date, not just the day
- Duplicate entries after a retry: look at the possible duplicates report and delete one
- New category names invented by the assistant: paste your list and say use only these
- Foreign-currency items: say the currency explicitly so the base-currency total uses the saved rate
- Partial success: count the rows afterwards and compare with five
Where this stops being the right tool
Chatting suits a handful of entries. For a month of card transactions, uploading the statement is faster and exact, and SpendixAI lets you review rows before saving. It has no bank sync and does not read SMS, and Pro covers one personal workspace with 2,000 transactions a month. Deleted entries go to a recycle bin for 30 days, which is a useful safety net for experiments.
How do you write the instructions once and reuse them?
Save a short standing instruction in your assistant: use only these categories, always show a list with a total before creating, state the date in full, and never edit or delete existing entries. Then each Saturday's message only needs the five items. The standing text is where your safety lives, so keep it plain and review it whenever you change your category names.
A few sentences that save cleanup
- Use today's date only if you really mean today; otherwise write 14 November 2026 in full
- Put the account at the end of each line, so the assistant never guesses cash versus card
- Ask it to list anything it is unsure about instead of choosing silently
- Tell it to stop after the list and wait for the word confirm
These four lines take ten seconds to type and prevent the majority of corrections you would otherwise make by hand later.
A closing checklist
- Scope widened only for this session
- Dry run read back with the total
- Row count verified
- Scope returned to read-only
- Any test entries deleted
Useful ideas start with a clearer picture of your own spending.
Explore your reports

