HSBC statement to Excel. Money in, money out, and a balance chain that has been walked.
UK statements often print Money In and Money Out as two positive columns, which means the sign never appears on the page at all. Collapse them carelessly and every withdrawal becomes income. The reading taken here is stated on screen, the running balance is re-added, and the first row that fails is named with the exact gap.
Drop a HSBC statement here
Or click to pick the file. It opens in the same page you would have used anyway — the balance chain starts re-adding on the next screen.
Three files free, 60 pages in total, no card needed. Paid plans are priced by the page — one page of the original is one page, up to 500 pages in a single file.
The date is the trap, not the numbers
UK statements print day first. 03/04/2026 is 3 April in London and 4 March in New York, and both readings produce a plausible ledger — which is exactly why this is dangerous rather than merely annoying. The export order is stated in the interface, and a date that could be read either way is flagged rather than resolved silently.
What gets checked before you download
Every line below is arithmetic on the paper you sent — not a supplier's claim about how good its reading is. Where the arithmetic fails, you get the row and the exact difference, and the statement is not called balanced.
Which order the dates are in
The day-first reading is asserted from the statement itself and shown. Where a cell is genuinely ambiguous, it is flagged instead of being chosen for you.
Money In and Money Out, not a signed column
Two positive columns are reconstructed into one signed movement, and the mapping is visible rather than implicit.
Opening + in − out = closing
The header figures are compared with the register. A failure is reported in pence, not rounded to the nearest pound.
Statement periods that do not align to months
An HSBC statement period can start mid-month. The period is read from the statement and stated, so a ledger is never silently assumed to be calendar-month.
Where a HSBC statement goes wrong quietly
None of these announce themselves. Each one produces a file that looks correct.
One account, several currencies
A statement can carry more than one currency. Amounts are never added across currencies; the currency is part of the row, and sums stay within it.
Interest and charges printed as a block
A charges summary is a claim about the period, not a transaction. It is checked against the register rather than added to it.
Fractional pence on FX lines
A converted amount can print more decimal places than the account currency. The printed figure is preserved exactly — it is not rounded to two places on the way out.
What we will not claim
We have no HSBC template and are not building one. When a page defeats the reader you get the page number and an honest gap, not a plausible substitute.
The same goes for the arithmetic: a clean run means the checks we ran found nothing to flag. It does not mean the document is correct — it means nothing in it failed the checks listed above.
How it runs
Upload the statement
A native PDF, a scan, or a phone photo of the HSBC statement. No bank connection, no credentials, nothing to authorise.
The ledger is rebuilt and walked
Rows are put back in the order the statement prints them, page furniture is removed, and the balance chain is re-added line by line.
Check the flags, then export
Anything that did not add up is listed first, with its page and exact difference. Then take the Excel file, the other export shapes, and the review sheet.
What lands on your disk
- The .XLSX register — one row per transaction, no merged cells, amounts as numbers
- A Review sheet: who confirmed or corrected which cell, and what it said before
- Plain CSV, Xero-shaped CSV, and QuickBooks .QBO with unique transaction IDs
- A check report stating the rows printed, the rows exported, and every difference found
- Every cell still clickable back to the page and region it was read from
- Files are read, then destroyed — a second upload is a second read
Questions
Does this handle a statement covering more than one currency?+
It reads them, and it keeps them apart. Totals are never taken across currencies, and the currency is carried on the row so a downstream system cannot add pounds to dollars by accident.
Will the dates come out the UK way?+
They come out as ISO dates (2026-04-03), which is unambiguous everywhere. The original printed string stays attached to the cell for anyone who needs to look at it as printed.
What if my client's statement is a printed scan?+
That is the case this is built for. A scanned figure is the one most likely to be doubtful, so it is flagged more readily — the flags are a reading order for your review, not a verdict.
What does it cost?+
Three files are free, 60 pages in total, with no card and no account needed to try. Paid plans are sold by the page — $19 a month buys 1,000 pages — and a page is one page of the original document.
For the file that has to import cleanly somewhere else.
The same checks, without naming a bank — including the ones whose layouts we do not recognise.
A .QBO with the institution, the account and a transaction ID per row, so a re-import is refused.