Upload the smallest file that does the job. For an expense tracker that means three columns: date, description and amount. Everything else on a statement, from your name to a running balance, is extra exposure with no benefit, so the safest habit is to trim before you hand anything over.
Why does a shared account change the question?
Many households here run a joint account or pay a partner back regularly. A statement then contains another person's name, and perhaps their spending habits too. You are not only deciding about your own data. A short conversation, such as asking whether they are comfortable with the file going into an app, avoids a surprise later.
What should I trim from the file?
Take a holiday month as an example. Say the statement shows €620 of travel spending: €280 of flights, €190 of hotel, €90 of food and €60 of local transport, which does add up to €620. Only those four lines matter to a tracker. Here is what goes and what stays.
| Keep | Remove or ignore |
|---|---|
| Transaction date | Account holder name and address |
| Merchant description | Full account number |
| Amount and currency | Running balance column |
| Reference for a transfer if useful | Notes written for other people |
A spreadsheet export makes this easy because you can delete columns. A PDF cannot be edited that neatly, so for a PDF the question becomes how the app treats the document after upload.
Can the app work without my bank login?
Look for one that accepts a file you chose and never asks for your banking sign-in. Giving a login to a middleman hands over far more than a statement ever would. If a screen asks you to enter a bank password or a one-time code, stop there, whatever the branding on it says.
How do I check what the AI sees?
Ask whether an AI model is involved in sorting transactions, and if so, what text is sent. The cautious design passes a cleaned merchant name and an amount range, not your name or the full document, and lets you switch the feature off or set a spending limit for it. Also ask whether an optional feature such as reading an odd layout sends the entire file, because that is a separate decision.
What is a sensible rollout?
- Export two weeks as CSV and delete the header and balance columns.
- Upload, then read every row before saving anything.
- Correct two or three categories and see whether the app remembers them.
- Remove the test data and confirm it disappears.
- Upload a full month only after that.
SpendixAI is built around India and INR and is not marketed for European accounts, but it states its design plainly: file upload, no bank login, and AI limited to a merchant name and amount band, with an off switch. That is a useful standard to hold other apps to.
What if the statement is in another language or format?
Cross-border households often hold accounts in more than one country, so layouts vary. Upload one account at a time and tell the app which account it is, so each row keeps its source. Read the first import line by line, because dates written day-first or month-first can be misread. A wrong date is a small error, but it spoils monthly totals, and catching it on a two-week test is far easier than finding it in a year of data.
Quick sanity check
- Is the file one I chose, with only needed columns?
- Does the app avoid asking for a banking sign-in?
- Do I know what the AI receives, and can I stop it?
- Have I told the other person on a joint account?
Useful ideas start with a clearer picture of your own spending.
Explore your reports


