People often ask whether a connected AI assistant replaces uploading statements. It does not, and the two are better seen as different tools. Importing is how records get into SpendixAI, the expense tracker we build for India. An assistant connected over MCP is a way of asking questions about records that are already there, and, if you allow it, of adding a few more.
What import does well
You upload a bank or card statement as PDF, CSV or Excel, and SpendixAI shows the rows for review before saving. You choose the account first, so each transaction keeps its account. Batch uploads are possible, an import history shows status, and possible duplicate imports are flagged. If you use more than one currency, pick the base currency before importing, because it cannot be changed once transactions exist. Categorisation then runs in stages: your rules, your history, and an AI model only if you have it switched on.
What an assistant does well
Asking. A question such as what did I spend last month is quicker in a chat than in a report builder, and the follow-ups come naturally. On the Read only preset the assistant views transactions and reports and changes nothing. With Read and add it can also create transactions and upload documents.
Which one for which job
| Job | Better route | Why |
|---|---|---|
| Loading a year of bank statements | Import | Built for statements, with a review step and duplicate flags |
| Asking what you spent last month | Assistant | A question, not a data entry task |
| Comparing two months by category | Assistant, or a report | Either works; reports give exact figures |
| Recording five cash expenses | Either | Manual entry exists; the assistant needs Read and add |
| Spotting repeated charges | Either | A report lists same-merchant charges within two days |
| Preparing figures for an accountant | Reports and exports | Check totals in SpendixAI, not in a chat |
How they work together
A sensible pattern runs like this. Upload your statements on the import screen as usual and review the rows. Then connect an assistant on the Read only preset and use it to explore: which categories grew, which merchants repeat, where cash went. The assistant gets better material because the import step has already set accounts and categories.
Where the lines blur
With write access, an assistant can upload statements and receipts as well. That is convenient, but we have not described whether such an upload shows the same row-by-row review as the normal import, so for statements we suggest using the import screen where you can see everything before it is saved. Keep assistant uploads for small, low-risk additions, and look at the results afterwards.
Mistakes to avoid
- Pasting statement text into a chat and asking for totals. Import the statement instead, so the rows are reviewed and kept with their account.
- Treating a chat total as final. Reports are where exact figures live.
- Leaving write access on after a one-off task.
- Importing before choosing the account and base currency, since both shape every transaction that follows.
Mind the answers
The assistant's provider writes its replies, under its own terms. SpendixAI suggests checking important figures, such as anything tax related, in the matching SpendixAI report. Treat a chat answer as a first look and the report as the record, and expect to look at both.
A simple month-end routine
Many people settle into a rhythm. Early in the month, download the previous month's statement from your bank, upload it through import and review the rows. Later, open your assistant and ask how the month compared with the one before. If something looks odd, open the matching report to confirm. The import keeps your records complete, and the assistant makes them easier to explore.
Getting started
If your records are not in SpendixAI yet, begin with import and come back to MCP afterwards. If they are, connect an assistant, choose Read only on the consent screen, and disconnect from Developer → MCP connections whenever you want to stop.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

