Getting started

How to analyse your spending with Claude without a CSV export

Analyse your spending with Claude without a CSV export: three routes, what to redact first, and how to check the answers against your own statement.

Editorial illustration for How to analyse your spending with Claude without a CSV export

You have three routes. Connect your expense records to Claude through MCP so it reads them directly, paste a short block of redacted transactions into the chat, or upload the statement document itself. Each trades convenience against how much data leaves your hands, so decide what you are comfortable sharing before you pick one.

Route one: connect an app that supports MCP

MCP is a standard way for an assistant to ask another app for specific information. SpendixAI supports connecting Claude or ChatGPT this way. You choose a scope, you can start with read-only access, and you can disconnect at any time. No export file is involved, because the assistant asks the app for the figures it needs, such as last month's spending by category. This only works if your transactions are already in the app, so the one-time job is importing your statements there.

Route two: paste a small, redacted block

If you only want an answer about one month, copy about twenty to fifty rows into the chat. Before pasting, remove anything that identifies you.

  • Account numbers, card numbers and reference numbers.
  • Your name and any names of people you paid.
  • Running balances, which reveal more than you think.

Keep date, merchant text and amount. That is enough for questions like "which five merchants took the most money". Remember that anything you paste is sent to the service, so never include logins, OTPs or PINs.

Route three: upload the document

Claude is usually described as an assistant people use to analyse statements they paste or upload, and it is positioned as an online service that processes files on its servers. An uploaded PDF contains everything on the page, including names and balances. If that worries you, prefer routes one or two.

Which questions work well?

Narrow, checkable questions get reliable answers. Broad ones invite confident guesses.

  1. How much did I spend on food delivery in March, and on how many days?
  2. Which merchants appear every month with a similar amount?
  3. List any charge above ₹5,000 and the date.
  4. Compare this month's total spend to last month's by category.

How do you check the answer?

Never accept a total without testing it once. Suppose the assistant says you spent ₹7,800 on food delivery from twelve orders. Filter your own statement for the delivery merchants, add the amounts and count the rows. If your sum is ₹7,350 from eleven orders, either a row was missed or a refund was counted. Ask the assistant to list the rows it used, and compare them.

CheckHow
TotalAdd the listed rows yourself
CountCount the rows it names
DatesConfirm all fall in the period asked
RefundsAsk whether credits were netted off

What should you not expect?

An assistant does not know your intentions. It may call a transfer to a family member a shopping expense or mix up two merchants with similar names. It also is not a financial adviser, and it should not decide whether you can afford something. Use it to surface patterns, then make the decision yourself.

How much history should you share?

Start small. One month is enough to test whether the answers are useful and accurate. Increase to three months only after you have verified one total by hand. More history makes comparisons richer, but it also means more data in a service you may not control. If you connect an app through MCP rather than pasting, the assistant fetches only what each question needs, which makes it easy to keep the scope narrow.

Whatever route you take, review what you have shared every few months. Disconnect integrations you no longer use, and delete chats that contain statement excerpts if the service lets you.

A starting plan

  • Decide which route fits your comfort level.
  • Start with one month.
  • Ask three narrow questions.
  • Verify one total by hand before trusting the rest.
SPENDIXAI JOURNAL

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

Explore your reports