You should not hand Claude your net-banking login, and with SpendixAI you never need to. The route is to upload your bank or card statements into your own workspace, review the rows, and then connect Claude to that workspace through MCP, choosing a scope and starting read-only. Claude then works with the records you chose to put there, not with your bank account.
What does connecting actually mean here?
SpendixAI has no bank connection and never asks for net-banking logins. It does not read your SMS either. Your records come from statements you upload as PDF, CSV or Excel, plus expenses you add by hand. The Claude connection sits on top of that workspace: you choose a scope, you can begin with read-only access, and you can disconnect whenever you like.
So the phrase 'connect Claude to my bank data' really means 'let Claude read the tidy copy of my transactions that I built myself'. That difference matters for safety and for accuracy.
Steps from statement to Claude
- Pick the account (bank, card or wallet) in the app before importing, so every transaction keeps its account.
- Upload the statement and review the rows before saving. Fix anything that looks wrong; no tool reads every layout perfectly.
- Check the categories. Correct the few that are off, because corrections become history for future imports.
- Open the Claude connection option from the app's MCP feature page and follow the on-screen steps in Claude.
- Choose a scope. Start with read-only if you are offered the choice.
- Test with one narrow question before asking anything broad.
What can I ask once it is connected?
- Total spent on a category in a given month
- Which merchants appear most often
- Whether any charge looks repeated
- A plain-language summary of a month, which you then compare with the app's own reports
Treat every answer as a draft to verify. Say Claude reports ₹14,200 on food delivery for October, and your Report builder view shows ₹13,700. The gap is ₹500. Look for one refund, a split bill or an uncategorised row; usually the explanation is a single item. Reports in the app are your reference; the assistant is a convenient reader.
Is read-only access enough for most questions?
Yes for summaries, comparisons and 'what changed' questions. Writing actions are different: if a wider scope is available, ask yourself whether you would be comfortable checking every change afterwards. Many people keep read-only and make edits themselves.
What if I only want Claude to look at one statement?
You can also open a chat in Claude and paste or attach a single statement yourself. That is your choice and it sends that document to the assistant you are using, so first remove account numbers, your name and anything you would not show a stranger. The MCP route keeps the data in your workspace and lets you set the scope instead.
What should I do if the answers look off?
Go back to the source. Open the same month in the app's own report and compare the total and the number of transactions. If the assistant included a transfer between your own accounts, or skipped a row you never categorised, the fix is in the workspace, not in the chat. Correct the row, ask again, and note how the answer changed. After two or three rounds you will know which questions it handles well and which you should simply read from a report.
A quick checklist
- No bank password anywhere in this process
- Statements uploaded and rows reviewed
- Read-only scope to start
- One test question whose answer you already know
- Know where to disconnect
When you want the full picture of what leaves your workspace and what does not, read the privacy page before you connect, and disconnect any time the connection stops being useful.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

