How to Convert TSB Bank Statements to Excel (2026 Guide)

TSB is a major UK high-street bank serving over 5 million customers. Originally part of Lloyds Banking Group, TSB was spun off as an independent bank in 2013 following the European Commission's competition ruling — though it briefly returned to the Lloyds fold before being acquired by Banco de Sabadell in 2015. Today, TSB operates with its own distinct brand, systems, and — importantly for accountants and bookkeepers — its own unique statement format.

If you work with TSB bank statements, you'll know that converting them to Excel isn't always straightforward. Truncated transaction descriptions, unique transaction type codes, and the DD MMM YYYY date format can all trip up generic conversion tools. This guide walks through every method available in 2026, from manual approaches to AI-powered tools designed specifically for TSB's format.

If you want to skip ahead, the fastest option is the dedicated TSB Statement to Excel converter from BankScan AI, which handles all the formatting issues discussed below in under 30 seconds.

Understanding TSB Statement Formats

Before choosing a conversion method, it helps to understand what you're working with. TSB issues statements in several different formats, each with its own characteristics.

Digital PDF Statements (Downloaded from Online Banking)

These are the most common type. To download a TSB statement, log in to TSB online banking, navigate to "View statements", select the relevant account, choose your date range, and download as a PDF. The resulting document is a native PDF with selectable text — but TSB's specific formatting quirks mean extraction isn't always clean. The clean tabular layout is deceptive: it looks straightforward but contains several pitfalls for automated extraction.

Scanned Paper Statements

Older TSB statements, statements from the pre-spin-off Lloyds TSB era, or archived documents are often scanned images. These contain no selectable text — the transaction data exists only as pixels. Converting these requires OCR (optical character recognition) technology, and many generic tools fail entirely with scanned bank documents.

Multi-Page and Multi-Account Statements

TSB business and personal accounts with heavy transaction volumes often span multiple pages. Page headers and footers repeat on every page, running balances carry across page breaks, and table headers reappear mid-document. Generic converters frequently stumble on these boundaries, producing duplicate headers and broken transaction rows.

Common Issues with TSB Statement Conversions

TSB statements have a unique set of formatting characteristics that cause trouble for generic PDF extraction tools. Here are the specific issues you're likely to encounter:

Truncated Transaction Descriptions (18-Character Limit)

TSB's biggest conversion headache: the bank truncates transaction descriptions at approximately 18 characters on their PDF statements. A payment to "Sainsbury's Supermarkets Ltd London" might appear as simply "SAINSBURY'S SUPERM" — cutting off mid-word. For expenses categorisation and audit purposes, this is a real problem. Unlike some other UK banks, TSB does not wrap descriptions across multiple rows, so the description you see on the PDF is all there is. This makes merchant identification significantly more difficult than with banks that provide fuller descriptions.

DD MMM YYYY Date Format

TSB uses the DD MMM YYYY format throughout its statements (e.g., "01 MAR 2026"). This abbreviated month format is unusual among UK banks — most use DD/MM/YYYY or DD Mon YYYY. Many conversion tools, especially those built for the US market, fail to recognise "MAR" or "DEC" as valid date components and output raw text instead of properly formatted dates. This requires manual correction in Excel for every single transaction row.

Transaction Type Codes

TSB includes short transaction type codes on every line item. Common codes include:

• VIS — Visa debit card payment
• DD — Direct Debit
• SO — Standing Order
• TFR — Transfer between accounts
• FPI — Faster Payment In
• FPO — Faster Payment Out
• DEB — Debit card payment
• ATM — Cash withdrawal
• CHG — Bank charge or fee
• INT — Interest payment

These codes are useful for categorising transactions, but generic converters often merge them into the description column or drop them entirely. A good conversion tool will preserve these codes in a dedicated column for easy filtering.

Multi-Column Payment and Withdrawal Format

TSB displays debits and credits in separate columns rather than a single amount column with a sign indicator. This two-column "money out / money in" layout is common across UK banks, but it means the converter must correctly identify which column contains the transaction amount and preserve the distinction. Generic tools often collapse both into a single column, losing the payment/withdrawal distinction.

Method 1: Convert TSB Statements with BankScan AI (Recommended)

BankScan AI's TSB converter is purpose-built to handle every TSB formatting issue described above. The AI understands TSB's specific statement structure, so it correctly parses DD MMM YYYY dates, preserves transaction type codes in a dedicated column, handles truncated descriptions as-is while enriching where possible, and maintains the payment/withdrawal column separation.

Here is the step-by-step process:

1. Upload your TSB statement — Drag and drop your PDF (digital or scanned) onto the BankScan AI dashboard. You can upload multiple statements at once for bulk processing.
2. Choose your output format — Select Excel (.xlsx), CSV, or Google Sheets depending on your needs.
3. Review and download — The AI extracts all transactions within seconds. Review the preview, then download your clean spreadsheet with properly separated date, transaction type, description, payment, receipt, and balance columns.

For accountants who need to push data directly into accounting software, BankScan AI also offers dedicated TSB to Xero and TSB to QuickBooks conversion tools that format the output specifically for each platform's import requirements.

Best for: Anyone who regularly converts TSB statements — accountants, bookkeepers, mortgage brokers, and business owners.

Method 2: Manual Copy-Paste into Excel

Open the TSB PDF in a viewer, select the transaction table, copy it, and paste it into Excel. The clean tabular layout means the data will probably paste as a reasonable table structure — better than some other banks — but you'll face several issues. The DD MMM YYYY dates (e.g., "01 MAR 2026") may paste as text rather than Excel dates, requiring manual conversion. Transaction type codes may merge into the description column. And if your statement includes separate payment and receipt columns, you'll need to verify they're correctly aligned.

For scanned TSB statements, copy-paste simply does not work at all — there is no text to select. This method is only viable for digital PDFs, and even then, cross-checking the converted totals against the closing balance is essential.

Best for: One-off situations with a short, simple digital TSB statement and zero budget.

Method 3: Adobe Acrobat Export

Adobe Acrobat Pro's "Export PDF to Spreadsheet" feature handles TSB's clean table layout reasonably well compared to more complex bank formats. However, the DD MMM YYYY date format still causes issues — Acrobat often exports these as plain text strings that Excel won't recognise as dates. Transaction type codes may be misaligned, and multi-page statements often produce duplicated headers at page breaks. At £15.17/month for an Adobe subscription, it's a partial solution at best.

Best for: Users who already have an Adobe subscription and handle TSB conversions infrequently.

Method 4: Free Online PDF-to-Excel Converters

Tools like Smallpdf, ILovePDF, and PDF2Go offer generic PDF-to-Excel conversion. Because TSB's table layout is relatively clean, these tools may produce superficially decent output. But the deeper problems remain: DD MMM YYYY dates will be treated as text, transaction type codes may disappear or merge, and there is no handling of the two-column payment/withdrawal structure.

Best for: Non-sensitive, personal use only. Not recommended for client work or business accounts.

Comparison: TSB Statement Conversion Methods

Which Output Format Should You Choose?

When converting TSB statements, you'll typically have a choice between several output formats. Here's when to use each:

Excel (.xlsx)

Best for reviewing and annotating data, running formulas, creating pivot tables, or sharing with colleagues who use Microsoft Office. TSB's transaction type codes are particularly useful in Excel, as you can filter by "DD" to isolate direct debits or "SO" to review standing orders. Use the TSB to Excel converter for this format.

CSV (.csv)

The universal interchange format. CSV files can be imported into virtually any accounting software, database, or spreadsheet application. If you're importing TSB data into Xero, Sage, FreeAgent, or QuickBooks, CSV is usually the safest choice. CSV is particularly useful for TSB statements because the transaction type codes are preserved as a separate column that most accounting platforms can map during import.

Google Sheets

Ideal for collaborative work. If your team needs to review TSB transactions together in real time, or if you use Google Workspace as your primary office suite, exporting directly to Google Sheets saves you the intermediate step of uploading a file.

OFX / QIF

Specialised banking formats designed for direct import into financial software. These carry additional metadata that CSV does not, such as transaction types and bank identifiers. If your accounting software supports these formats, they can retain the transaction type codes (VIS, DD, SO, etc.) natively.

TSB Statement Conversion Use Cases

Tax Returns and HMRC Submissions

Self-employed individuals and limited company directors often need to provide transaction-level bank data to their accountant or include it in self-assessment returns. Converting TSB statements to Excel allows you to categorise income and expenses using the transaction type codes as a starting point — filtering by "FPO" for outgoings and "FPI" for income, for example. Accuracy is critical here; date errors from mishandled DD MMM YYYY formatting can cause serious problems during tax preparation.

Mortgage Applications

Lenders typically require three to six months of bank statements to verify income and spending patterns. Converting TSB statements for mortgage applications ensures the data is clean, complete, and easy for underwriters to review. The transaction type codes are particularly helpful for underwriters who want to quickly identify recurring commitments like direct debits and standing orders.

Bookkeeping and Reconciliation

For accountants managing TSB clients, monthly statement conversion is a recurring task. Having a reliable, fast conversion process that preserves transaction type codes and handles DD MMM YYYY dates correctly means less time on data entry and more time on advisory work. Bulk upload features become essential when handling dozens of client statements each month.

Importing into Accounting Software

Whether you use Xero, QuickBooks, Sage, or FreeAgent, getting TSB data into your accounting package accurately is the first step in any reconciliation workflow. TSB's CSV export option through online banking is limited in date range and doesn't always include full transaction details, so converting from PDF often yields more complete data.

Frequently Asked Questions

Can I convert a scanned TSB bank statement to Excel?

Yes, but you need a tool with OCR (optical character recognition). Standard copy-paste and most free online converters cannot read scanned documents. BankScan AI uses AI-powered OCR to extract transaction data from scanned TSB statements, including older printed statements that have been photographed or scanned. For best results, scans should be at 300 DPI or higher.

Why are TSB transaction descriptions so short?

TSB truncates transaction descriptions at approximately 18 characters on their PDF statements. This is a limitation of TSB's statement generation system, which allocates a fixed-width column for descriptions. A payment to "Tesco Stores Ltd London" may appear as simply "TESCO STORES LTD" or even shorter. Unlike HSBC, which wraps descriptions across multiple rows (creating its own set of problems), TSB simply cuts them off. BankScan AI preserves the full description text as it appears on the statement and, where possible, cross-references transaction type codes and amounts to help identify the merchant.

What's the fastest way to convert a year's worth of TSB statements?

The fastest method is to use a tool that supports bulk upload of multiple PDFs. BankScan AI allows you to drag and drop an entire folder of TSB statements and process them in a single batch, outputting one consolidated spreadsheet or individual files per statement. A full year of TSB statements (typically 12 monthly PDFs) can be converted to a single Excel workbook in under two minutes. Manual copy-paste would take several hours for the same volume, and you'd still need to fix the DD MMM YYYY dates manually on every row.

Does TSB provide CSV downloads of statements?

Yes, TSB does offer CSV downloads through their online banking portal, but with important limitations. The CSV export is only available for the current statement period and some recent history — older statements, archived periods, or statements from historical accounts are only available as PDFs. Additionally, TSB's CSV format often omits the full transaction description and merchant codes that appear on the PDF. For thorough bookkeeping and audit purposes, converting the PDF statement often yields more complete data than relying on the native CSV export. A tool like BankScan AI bridges this gap by extracting the richer data from the PDF.

Last updated: 10 May 2026. Have a question about converting TSB statements? Visit BankScan AI or read our other guides for UK accountants.