Santander UK Statements to Excel: Masked Midata CSV vs Issued PDF

Santander documents a native midata CSV for twelve months of personal current-account history. This guide covers the UK product and the task described below.

Use the native CSV only for its documented purpose

This task is for a UK current-account holder choosing a source for spreadsheet work. Santander's midata guide documents a CSV of the last twelve months of personal current-account history to help compare accounts. It masks name, address, account number and potentially sensitive transactions. That privacy design means it is not automatically an unmasked accounting dataset or a replacement for an issued statement.

The published Online Banking route is:

1. Open My Accounts and Transactions and select the current account.
2. Choose Download transactions, then Download to: midata (CSV).
3. Choose Download, review the confirmation and Continue, then save the offered CSV.
4. Preserve the original and inspect its actual fields, dates and masking before choosing it as a source.

These instructions do not establish an all-products CSV, a credit-card export or an unlimited configurable history range. No native file was authenticated-tested. A separate legacy help template lists Excel and other formats, but that is not proof of a current generic CSV menu. The strongest current CSV evidence here is specifically midata.

Compare source coverage with the issued cycle

The statement guidance ties a current-account cycle to opening/transfer date and gives an 18th–17th example. The mobile inbox demo has account, document-type and date filters; it does not establish those dates as a transaction filter inside the statement. Collect the issued PDF when its original period and complete details are what the task requires.

Consider an invented cycle from 18 August to 17 September. A 1–31 August analysis answers a calendar-month question, not that cycle's reconciliation. A movement on 19 August is in both selections; one on 10 September is in the cycle but outside August. Decide the required interval before comparing totals. This example is arithmetic reasoning, not a Santander file or layout test.

Make a checked cash table without inventing missing detail

Define positive amounts as posted deposit inflows and negative amounts as outflows. Read the date meaning from the source. Keep account alias, currency and cycle in a separate private source register, meaning a list of the original records used. Preserve any extra date or source-page reference in manual worksheet columns. A constructed example is:

date,description,amount
2026-08-19,Example receipt,250.00
2026-09-10,"Example purchase, supplies",-100.00
2026-09-12,Example fee,-10.00

These are invented fields and rows, not midata headers. Do not guess a masked merchant name or supply an unexplained balancing row. If a source does not provide sufficient detail for the task, choose a suitable original or record the unresolved limit.

Import a working CSV with Data → From Text/CSV in Excel and check delimiter, dates, decimal amounts and quoted descriptions before loading. Microsoft's import guide and RFC 4180 support those format checks. Saving XLSX happens in Excel after checking; LocalExtract exports CSV.

Compare opening plus signed movements with closing only when account, currency and complete period match and comparable endpoints exist. A correct net total still does not prove every date or description. Keep an issued original unchanged; neither a converted table nor the masked midata comparison file is automatically the original statement.

Check the method with invented records

We recomputed three deliberately constructed cases on October 11, 2026 using decimal arithmetic: complete rows, an omitted fee and a duplicated movement. The reference total and every number are invented. This checks the reconciliation method only: no bank account, real PDF, OCR result or LocalExtract output was tested. The same learning aid is used across these guides.

Illustrative units, not a real account balance.

Download the blank document checklist or synthetic check data. CSV · JSON.

Frequently Asked Questions

Does Santander UK offer any native CSV?

Yes: the documented midata export covers twelve months of personal current-account history and masks identity and potentially sensitive transactions. Its scope is account comparison.

Is midata guaranteed complete unmasked accounting data?

No. Inspect the actual fields and masking. Use a suitable issued record when the task requires details the comparison export does not supply.

Can I reconcile an 18th–17th cycle to a calendar month?

Only when the account, interval and included movements actually match; those two intervals generally answer different questions.

Can missing masked descriptions be guessed?

No. Preserve the source limitation or obtain an appropriate original; do not fabricate merchant names or balancing entries.

If PDF is the relevant source

LocalExtract processes one PDF at a time on the device and exports CSV with date,description,amount. Parsing and OCR do not require uploading the statement. This is a working table that needs comparison with the original; no bank compatibility was validated here. There is no direct XLSX, QBO or OFX export, bulk queue or automatic accounting sync. To obtain XLSX, import the checked CSV and save from Excel.

The free evaluation covers ten pages in total. Pro is USD 10/month or USD 60/year. Account, subscription, update and periodic Pro checks need network access. See downloads and product scope.

Sources and verification scope

Public official guidance checked October 11, 2026. Account controls, document availability and bank layouts were not authenticated-tested. The method exercises use invented records, not actual bank samples or measured extraction results.

• Bank guidance 1
• Bank guidance 2
• Bank guidance 3

Updated October 11, 2026: Added task-specific source decisions, date/amount examples and CSV import checks. No bank format or app output was validated.

Use midata for its documented comparison purpose, and choose complete issued records for the reconciliation detail you need. Preserve source scope and inspect the imported table before relying on totals.