Convert a Santander Statement PDF to Excel
Santander statement conversion across UK and European layouts, the decimal comma trap, and verifying the result.
Santander operates across the UK, Spain, Portugal, Poland and Latin America, and its statements differ by market in a way that causes a specific and dangerous error.
The decimal comma
A Santander UK statement writes one thousand two hundred and thirty four euros fifty six as 1,234.56. A Santander Spain statement writes the same amount as 1.234,56. The separators are reversed.
A parser that assumes the UK convention reads the Spanish 960,00 as 96000 — because it treats the comma as a thousands separator and drops it. That is a factor of one hundred, and the result looks entirely plausible sitting in a spreadsheet.
How to disambiguate reliably
Guessing from the country is fragile — a UK resident can hold a Spanish account. The robust approach is to test both interpretations against the statement's own printed closing balance and keep the one that reconciles.
That works because the balance chain is extremely sensitive to a 100x error. If the decimal convention is wrong, the chain fails on the first row that has a decimal fraction. If it is right, the chain holds across every row.
| Written as | UK reading | European reading |
|---|---|---|
| 1.234,56 | 1.23456 (nonsense) | 1,234.56 ✓ |
| 1,234.56 | 1,234.56 ✓ | 1.23456 (nonsense) |
| 960,00 | 96000 ✗ | 960.00 ✓ |
A check you can run yourself
If your converted amounts look roughly a hundred times too large, this is almost certainly the cause. Compare one row against the PDF and it will be immediately obvious.
Converting safely across markets
- Convert each statement separately Do not merge PDFs from different markets — the number conventions differ.
- Check the magnitude of one amount Against the PDF. This catches a decimal misreading in seconds.
- Walk the chain Which is the definitive test — a 100x error breaks it on the first row with a fractional amount.
- Compare the totals For completeness as well as correctness.
Why this error is worth so much attention
It is worth being explicit about why the decimal question gets a whole section rather than a footnote.
Most conversion errors are either obvious — garbled text, empty columns — or caught by a plausibility check. A 100x decimal error is neither. €96,000 sitting in a spreadsheet where €960 belonged is a well-formed number in a plausible range, and it will pass every check except the arithmetic.
It is also the error most likely to have real consequences, because it is large. A misread digit changes a figure by a few units; this changes it by two orders of magnitude.
Frequently asked questions
Which Santander markets are supported?
The reader works from the table on the page rather than from the brand name, so a Spanish or Polish statement is read the same way as a UK one. The Completeness sheet tells you whether yours came out right.
How would I notice a decimal error myself?
Compare any one amount against the PDF. If the converted value is 100x the printed one, the convention was read wrongly and the whole file is affected.
Can the converted file get a decimal comma wrong?
Not the Excel or CSV: every amount is kept exactly as printed, 960,00 included, so there is nothing in the file to misread. The risk comes back when you turn that text into numbers, so set Excel's decimal separator to match the statement first, then compare one row against the PDF.
Related posts
- Convert an HSBC UK Statement to Excel
- Convert a TSB Bank Statement to Excel
- Convert a Revolut Statement to Excel
Convert a statement now
Bank Statement PDF to Excel, or see every format. More in the guides.