Santander Statement to CSV: Past the 600-Transaction Cap

You need Santander transactions in a spreadsheet, and you need them complete — every direct debit, every card payment, every credit in the right direction. Maybe you are building a mortgage application, preparing a Self Assessment return, giving a bookkeeper a trading year, or reconstructing an account that has since been closed.

Santander UK will hand you a spreadsheet, but on terms: the download is capped at 600 transactions and the CSV option covers twelve months. Beyond either boundary, or without a login at all, what you have is a PDF. This guide covers both routes, the Santander-specific things that break generic converters, and how to prove your CSV matches the statement to the penny.

Quick answer

There are two ways to get Santander transactions into CSV:

1. Santander's own download. Online Banking has a Download transactions option above the transactions table. You choose either a date range (All available transactions) or Since last download, then pick a format. Santander lists Microsoft Excel, Quicken, Adobe Acrobat (PDF) and Microsoft Money — note that CSV is not among them. Separately, personal current account customers can get a midata file, which is a CSV, from the same Download transactions page.
2. Convert the PDF statement. For anything past the caps, for closed accounts, or for a statement someone emailed you, the transactions exist only inside a PDF. Upload it to a converter such as BankStatementKit, which reads the transactions out and balance-checks the result against the statement's own printed totals.

Rule of thumb: under 600 transactions and inside twelve months, take Santander's export. Everything else goes through the PDF.

Convert a Santander PDF into a verified CSV

Option 1: Santander's built-in transaction download

If you have Online Banking access and your period is modest, start here.

1. Log in to Online Banking and open My Accounts and Transactions.
2. Select the account you want and click the Download transactions link above the transactions table.
3. Choose All available transactions and set your date range, or Since last download if you export regularly.
4. Pick a format from the Download to dropdown — Microsoft Excel is the spreadsheet option; there is no CSV in this list — then click Download. If you want a CSV specifically, look for the midata file on the same page instead: it is a separate artefact, not a choice in this dropdown.

Where the built-in download stops

The export is real and it is free, and it hits walls quickly:

• 600 transactions per download. Santander states this outright. An active current account can pass 600 transactions in well under a year, at which point you are splitting the period and stitching files together by hand.
• Twelve months for midata CSV. The plain-CSV route is documented as twelve months of history on a personal current account. Anything older is not available through it.
• Excel, Quicken and Money are the alternatives. Useful, but they need converting or cleaning before most modern accounting tools will accept them, and only the midata route is CSV out of the box.
• A live login is required. Closed accounts, accounts held by someone else, and statements sent to you by a lender or solicitor cannot be exported at all.
• The statement document itself is a PDF. The formal statement — the one with the printed opening and closing balances that a lender actually wants — is a PDF, not a spreadsheet.

Every one of those cases ends in the same place: a PDF.

Option 2: Convert the Santander PDF statement to CSV

1. Find the statement PDF — downloaded from Online Banking, saved from paper-free e-documents, or sent to you by someone else.
2. Upload it. The file is processed in memory and never stored. If it asks for a password, supply it at upload.
3. The transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance — money out to Debit, money in to Credit.
4. Check the verification label, then download the CSV.

Uploads are limited to 20MB or 50 pages, and there is no per-file transaction cap, so a multi-year statement converts in a single pass. Scanned or photographed statements fall back to OCR automatically. There is more on the layout on the Santander statement converter page.

Convert a Santander statement

Why Santander PDFs trip up generic converters

A sparse layout is harder, not easier. Santander's statement design is airy — generous white space between rows and columns. That looks helpful and is actually a hazard: extraction that infers columns from where text clusters has fewer landmarks to work with, so a long description reaching towards the amount columns can be misread as sitting in one of them. Columns have to be established from the whole page geometry rather than row by row.

Card descriptions carry more than a merchant name. A card entry typically brings the merchant, a location and frequently the original transaction date, which is different from the date the entry posted. Two consequences: the description regularly needs a second printed line, so a line-by-line reader manufactures phantom rows with no amounts; and the embedded purchase date can be mistaken for the transaction date, quietly reordering the statement.

Amount direction lives in the layout, not in a sign. Money in and money out are printed as separate columns rather than one signed figure. Collapse them carelessly and every outgoing payment in the file loses its sign — an error nothing complains about until a reconciliation refuses to close.

Prove the CSV matches the statement

This is the step most people skip, and it is the one that matters. A Santander statement gives you two independent checks:

1. The running balance chain. Each row prints a balance. For every row, the previous balance minus money out plus money in must equal the printed figure. A single dropped or duplicated transaction breaks the chain at exactly the row where it went wrong, so the error is findable, not just detectable.
2. The printed opening and closing balances. The statement states where the period begins and ends. Opening balance plus total money in minus total money out must equal the closing balance. If that holds, nothing went missing in bulk.

That second check is especially worth doing on Santander because of the 600-transaction cap: if you exported in two or three chunks and stitched them, the overlap or gap at the seam is exactly what this test catches. BankStatementKit runs both checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pinpointing the row where the numbers stop reconciling.

FAQ

The bottom line

If your period fits inside 600 transactions and twelve months and you can log in, take Santander's own download — it is free and native. Past those caps, or for closed accounts and PDFs someone sent you, convert the statement PDF in one pass and insist on a conversion you can prove. The split in/out columns and the description-heavy card rows are exactly where silent errors hide.