Bank statements

Is it safe to upload bank statements to an expense app? A UK guide

Thinking of uploading bank statements to an expense app in the UK? Use these ten due-diligence questions, plus a safe first test with a single week of data.

Editorial illustration for Is it safe to upload bank statements to an expense app? A UK guide

Safe enough is a judgement you can make in about twenty minutes. Instead of trusting a logo, put ten plain questions to the app, and upload nothing until you have answers. Start with a small file, because the cheapest way to test any app is to give it very little.

Which questions should I ask first?

Treat the app like a contractor you are about to give a spare key. Here are the questions, in the order we would ask them.

  1. Does it fetch data by asking for my online banking login, or do I upload a file myself?
  2. Which file types does it take, and can I use a CSV so I control the columns?
  3. Who can see my records inside the account, and is access role-based?
  4. Does it use AI, and exactly what text goes to the model?
  5. Can I turn AI off or cap it?
  6. How long are uploaded documents kept, and can I choose?
  7. Can I delete one transaction, one document, or everything?
  8. Is there a grace period if I schedule full deletion?
  9. Does the company say it does not sell personal information?
  10. Can I export my data before I leave?

If an answer is vague, write it down as a vague answer. Several of those in a row is information too.

Why start with a one-week test?

Say your current account shows £1,850 spent in a month, and you take only the last seven days, which come to about £430. You expose less than a quarter of the month, you see how rows are read, and you find out whether categories land sensibly. Mistakes are cheap at that size.

StageWhat you uploadWhat you learn
Test 1Seven days, CSV, three columnsHow rows are shown and corrected
Test 2One full monthWhether duplicates are flagged
Full useSeveral accounts, monthsWhether history improves guesses

What about the personal details on the file?

Statements often carry your name, address and account details in the header, and payee names for friends you have paid. Open the file first. Delete the header rows if it is a spreadsheet. For a PDF, you may have no choice but to upload it whole, so judge the app on how it treats uploaded documents and not on the hope that nothing sensitive is inside.

Is the AI part the risky bit?

It is the part that deserves a question mark, not an alarm. A reasonable design uses your own rules first, then your past choices, and only asks a model about whatever remains, sending a cleaned merchant name and a rough amount band. If you can turn that stage off, unmatched rows simply wait for you. That is slower but keeps everything on your side of the line.

Can I check any of this against a real product?

Yes. SpendixAI describes exactly this pattern: upload only, no bank connection, AI that receives a normalised merchant name and an amount band, and a switch to disable it. It is built around India and rupees, so it is not offered for UK accounts, but it makes a decent benchmark when you read other apps' privacy pages.

What should I do after the test?

  • Delete the test data and see how the app confirms it.
  • Keep the original statement in your own storage.
  • Note the date you uploaded, so you can revisit the retention setting.
  • Decide whether to go on, using the ten answers rather than how the screen looks.

Rules and consumer protections differ by provider, so for questions about your bank's terms, ask the bank.

SPENDIXAI JOURNAL

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

Explore your reports