This guide covers TSB Bank in the UK. If your account is with Permanent TSB in Ireland, a different bank with different systems, see the guide to Permanent TSB statements in Ireland.
For paperless customers, TSB issues statements as PDFs in the Digital Inbox and keeps them there for as long as the account stays open. In the TSB app, tap the profile icon, then Inbox, open the statement and tap the download icon. Once an account is closed, its Inbox can only be seen if the customer still has another open TSB account. For anyone who doesn't, TSB will send the account's transaction history on paper, free, if it is asked for within five years of closing.
TSB's own pages name no spreadsheet format for exporting transactions, so to get a TSB bank statement to Excel, the PDF statement is the place to start. Converting the Inbox PDFs, or a scan of the paper history, into one row per transaction gives an Excel or CSV file you can filter, total and reconcile.
The routes TSB offers, side by side:
| Route | Who gets it | What you get | How far back |
|---|---|---|---|
| Digital Inbox statements, in the app | Customers on paperless statements | PDFs that look exactly like the paper versions | From the date the account went paperless, for as long as the account is open |
| Closed-account transaction history | Anyone, for five years after closing an account | A paper copy by post or in branch, free, within ten working days of ID being confirmed | The account's transaction history, which can run to 60 pages or more |
| Business Internet Banking | Business customers, at every user level including Delegate View Only | Transactions on screen, a print-friendly view, and a download into a financial software package | At least the last 13 months |
| Ordered duplicate statements | Any customer | Formal paper statements, for a fee | Not stated by TSB |
One more fact affects anyone keeping TSB records for the coming year: Santander UK now owns TSB, and TSB's business is planned to transfer to Santander UK plc on 22 March 2027, subject to the court.
What the Digital Inbox holds, and what it doesn't
A paperless TSB statement is the same document a paper customer gets in the post. TSB's paperless banking page says its paperless documents "will be in PDF format and they'll look exactly the same as the paper versions", and its Digital Banking terms promise: "We won't change or delete them for as long as you have your account." For a live account, then, the Inbox is a complete and stable archive of every statement sent there.
The words that matter are sent there. The Inbox holds only what TSB delivered to it, so statement periods from before the customer switched to paperless are not in it. A client who went paperless two years ago and needs four years of history has two years in the Inbox and two years on paper, wherever they kept it. Ordering duplicates from TSB costs money, which makes the Inbox copies the free source for everything they cover.
To download a statement in the app:
- Tap the profile icon.
- Tap Inbox.
- Open the statement you want.
- Tap the download icon and save the PDF.
TSB adds that the download "may look and work differently depending on your device and operating system", so the last step can differ from phone to phone. Rename each file as it lands, with the account and the statement period (TSB current 2025-04.pdf, for instance), so that every file in a year's batch says which statement it is.
What about exporting transactions from the screen instead? TSB's help pages name no file format, no date range and no transaction limit for a personal export. The third-party guides that describe one disagree with each other about what it covers, none of them is TSB's, and what an on-screen export covers is set by TSB. The Inbox PDF has no such question attached: for each statement period it covers, it is the formal and complete record.
So when you ask a TSB client for statements, ask for two things:
- Every Inbox PDF for the period, downloaded and sent as files rather than screenshots.
- The paper statements for any months before they went paperless, scanned or photographed page by page.
Closing a TSB account: save the Inbox first, then ask for the history on paper
TSB's Digital Banking terms put the key word in capitals: "Save or print any documents you want to keep BEFORE closing your account." After closure, the statements for that account can be seen only by a customer who still has another open TSB account. A client who switches everything to another bank loses sight of the Inbox on the day the account closes.
The practical rule for anyone about to close a TSB account, or advising a client who is: download every Inbox PDF first, for every account being closed, and keep them with the year's records.
If that didn't happen, TSB's transaction history service fills the gap. Its FAQ says a customer is "entitled to copy statements (your transaction history) after you have closed your account" and can ask "at any time during the next five years". The terms of the service:
- Format: "in paper format for now". There is no PDF and no download.
- Cost: free.
- Timing: within ten working days of TSB confirming the customer's identification.
- How: by post or in branch.
- Length: TSB warns it can run to 60 pages, and more for accounts with high transaction levels.
TSB confirms the account holder's identification before sending it, so the client makes the request, not the bookkeeper.
For spreadsheet work the consequence is plain. Unless the client still has another TSB account, a closed account leaves no file to export and nothing to log into, only a stack of printed pages. Those pages have to be scanned, or photographed one by one, before they can become rows, and the worked example at the end of this guide takes exactly that case. Other banks handle closure differently: Monzo, for instance, emails a single PDF of the full history when an account closes, as the guide to Monzo statements for closed accounts explains.
TSB Business Internet Banking: 13 months on screen, downloads for every user level
Business customers have a route personal customers don't. TSB's business help page says Business Internet Banking lets you "View transactions on your account for at least the last 13 months" and "Print your statement or download it into a financial software package".
The useful detail for bookkeepers is in TSB's Ways to Bank User Guide (TSB13051). It lists three user levels, and "Download statements into a financial software package" is available at all three, Delegate View Only included. TSB describes the Delegate View Only level as viewing balances, transactions and Direct Debits. So a bookkeeper whose client has set them up with view-only access can pull the transactions for a VAT quarter or a year-end without waiting for the client to do it.
Two limits shape what that download is good for:
- It is not a formal statement. Printing from Internet Banking gives a "print-friendly format, rather than formal statement form", in the guide's words. Formal statements ordered from TSB are charged. Where a lender or an auditor wants the bank's statement, the formal statement, the Inbox PDF or the paper original, is the document to send.
- It reaches back at least 13 months, and TSB promises no further. That covers a year's VAT quarters, or one set of annual accounts if the transactions are pulled soon after the year-end: leave it six months and the start of the year has already gone. A catch-up job on two or three years of unfiled accounts runs well past it. For anything older, the PDF statements are the source, converted as shown further down.
TSB doesn't name the file format of the download on any of its business pages, so check what your accounting software accepts by trying a short date range first.
Sole traders and landlords who run their business through a personal TSB account should know one of TSB's terms. Its personal Digital Banking terms say the services "are for your personal use only. Business use is not allowed." That is TSB's term for personal accounts, and how it applies to a particular client is between the client and TSB. It also means that client has no Business Internet Banking: their history comes from the Inbox PDFs and, for older periods, paper.
TSB under Santander: what changes on statements, and when
Santander UK completed its acquisition of TSB on 30 April 2026, and the next step now has dates.
According to TSB's regulatory announcement of the transfer scheme, TSB and Santander UK applied to the High Court on 30 October 2026 for a banking business transfer scheme under Part VII of the Financial Services and Markets Act 2000, to move substantially all of TSB's business to Santander UK. The application was announced on 10 November. The court hearing is set for 15 February 2027, and the transfer is proposed to take effect on 22 March 2027. Both dates are plans: the transfer happens only if the court sanctions it.
What TSB and Santander have published about the customer's side:
- Account numbers, cards and PINs stay the same.
- "No immediate changes to the way TSB customers bank."
- Statements change name. From the transfer, Santander says, "In documents such as bank statements and terms and conditions, 'TSB Bank PLC' will change to 'Santander UK plc'. TSB won't replace your existing documents, but any new documents you receive will include this change."
- Access changes later. TSB says there will be "some changes ... to how TSB customers can use, access and manage their accounts as they migrate to Santander UK systems, platforms and channels in the second half of 2027".
For a bookkeeper, the name change has one direct consequence. If the transfer goes ahead on 22 March 2027, a client's statements for the 2026/27 tax year will say TSB Bank PLC up to the transfer and Santander UK plc on any issued after it. Finding both names on one account's year of statements is expected, not a sign of a second account: the account number, which TSB says stays the same, is what ties them together.
What no TSB or Santander page says is what happens to Digital Inbox statements, closed-account history requests or Internet Banking downloads when accounts move onto Santander's systems in the second half of 2027. Nothing has been published either way. The careful step costs a few minutes: download and keep the Inbox PDFs that you or your client need, for every year still open for tax or accounts, before then.
Santander UK's own statements, and the transaction export it gives its existing customers, are the other half of the group: see the guide to converting Santander UK statements to Excel.
Converting TSB Inbox PDFs and scanned statements to Excel or CSV
By this point the files tend to be a mix: a year of Inbox PDFs, a few older paper statements scanned on a phone, perhaps a printed closed-account history. With Invoice Data Extraction you can convert TSB statements to Excel or CSV as one job. The downloaded PDFs, scanned PDFs and photos of pages (JPG or PNG) go into the same task, which takes up to 6,000 files, and a single PDF can run to 5,000 pages, so a scanned 60-page history goes in whole.
You say what the spreadsheet should look like in plain words. The ready-made bank statement prompt asks for one row per transaction, and you can add to it whatever the job needs:
- The statement period on every row, so each transaction can be traced back to the statement it was printed on.
- The running balance, so the balances can be checked against the statements page by page.
- A category column, for VAT, Self Assessment, MTD for Income Tax records or year-end work.
- A Bank column reading TSB Bank PLC or Santander UK plc as each statement shows it, if a year straddles the transfer.
The download is Excel, CSV or JSON. In Excel, amounts come through as numbers and dates as dates, so totals, filters and pivot tables work straight away. CSV and JSON carry every value as text.
Two columns follow the ones you asked for. Source File gives the file and page each row came from. Review Needed flags a value or a row the panel of AI agents cannot agree on, with what to check, so you check the flagged values rather than every row of the sheet. A page that cannot be processed is reported, never skipped in silence, and you are not charged for it, which matters on a history where one missing page means a month of missing transactions.
Clients rarely bank in one place. A sole trader with a TSB current account and a savings account elsewhere can send both banks' statements into the same task. Whether the other bank's statements need converting at all depends on its own export rules: see Nationwide's statement and CSV limits and the guide to Lloyds bank statement to Excel.
Worked example: a client's printed TSB history for a Self Assessment catch-up
A self-employed plasterer moved his banking from TSB to another bank in June 2025 and closed the TSB account without downloading anything from the Inbox. He has not filed Self Assessment for 2023/24 or 2024/25, and his accountant needs both years of trading transactions. He asks TSB for his transaction history, and within the ten working days TSB allows, 48 printed pages arrive in the post.
The accountant scans the pages into one PDF on the office scanner (a phone photo of each page would work too) and runs it as one task with this prompt:
One row per transaction. Date as DD/MM/YYYY, description, paid in, paid out, balance. Add a Statement Period column with the date range printed on the page the transaction is on. Add a Tax Year column: 2023/24 for dates from 6 April 2023 to 5 April 2024, 2024/25 for dates from 6 April 2024 to 5 April 2025. Keep the rows in the order they appear in the history.
An invented extract of the rows that come back, either side of the tax-year boundary:
| Date | Description | Paid in | Paid out | Balance | Statement Period | Tax Year |
|---|---|---|---|---|---|---|
| 28/03/2024 | CARD PAYMENT SCREWFIX | 84.20 | 2,315.60 | 15/03/2024 to 14/04/2024 | 2023/24 | |
| 02/04/2024 | FASTER PAYMENT R HOLLIS | 950.00 | 3,265.60 | 15/03/2024 to 14/04/2024 | 2023/24 | |
| 05/04/2024 | DIRECT DEBIT VODAFONE | 32.00 | 3,233.60 | 15/03/2024 to 14/04/2024 | 2023/24 | |
| 08/04/2024 | CARD PAYMENT TOOLSTATION | 146.75 | 3,086.85 | 15/03/2024 to 14/04/2024 | 2024/25 | |
| 12/04/2024 | FASTER PAYMENT K OKAFOR | 1,200.00 | 4,286.85 | 15/03/2024 to 14/04/2024 | 2024/25 | |
| 16/04/2024 | STANDING ORDER VAN FINANCE | 289.00 | 3,997.85 | 15/04/2024 to 14/05/2024 | 2024/25 |
The Source File and Review Needed columns follow these, with the page number of the scan on every row.
Check the balances before anything else. On a printed history, the running balance is the proof that nothing is missing. With paid in, paid out and balance in columns C, D and E, put this in row 3 of the first empty column to the right of the data (J3, after Source File and Review Needed) and fill it down:
=ROUND(E2+C3-D3-E3,2)
Every row should show 0. A non-zero result means the row above it and this row don't connect: either a value was misread, or transactions are missing between them. Where the non-zero row is the first on a new page, a page of the history is probably missing from the scan. The Source File column names the page to look at, so the fix is a rescan of one sheet of paper, not a search through 48. Work through any Review Needed rows first, since those are the values the panel of AI agents could not agree on and the warning says what to check. Keep the rows in their extracted order while checking: sorting by date can reorder transactions on the same day and break the chain.
Then split the years. Filter the Tax Year column to 2023/24 and the trading income and expenses for that return are in front of you; categorise the rows, total them and move on to 2024/25. The boundary rows in the extract show why the column is worth having: the 8 April Toolstation payment sits on a statement that began in March 2024, but it belongs to the 2024/25 return.
Keep the scan with the sheet. HMRC expects the self-employed to keep their records for at least five years after the 31 January submission deadline of the tax year they belong to. TSB's offer of a copy history runs for five years from closure. For the 2024/25 year, whose deadline is 31 January 2026, HMRC's period outlasts TSB's, so the scanned PDF and the spreadsheet built from it are the records to keep.