Convert HSBC Statements to QuickBooks

That last point matters more than people expect. A bank feed wires QuickBooks to your live HSBC account and trickles in recent activity on its own. A file import covers everything a feed won't: statements older than the feed reaches, an account you've since closed, a backlog you're clearing, or a client who only sends you PDFs. For anything stuck in a PDF, converting and uploading is the route that actually gets it done.

What HSBC's layout does to the conversion

HSBC prints its UK statements across five columns: Date, a transaction-type code, Paid out, Paid in, and Balance on the right. That Balance column is the running balance, recalculated on every line, so each figure equals the one above it plus paid in and minus paid out. QuickBooks has no use for a running balance. It wants a single signed Amount, or a debit and a credit column. Keep HSBC's balance beside you while you convert, though — it's the only thing that proves nothing fell out along the way.

Then come the quirks that catch converters out. HSBC writes the date once per day, on that day's first transaction, and leaves the date cell empty on every row beneath. Strip the formatting carelessly and those blank cells slide a description onto the wrong day or fuse two transactions into one. HSBC also tends to drop the year, showing 14/03 rather than 14/03/2025, even though the full date sits in the statement period at the top. And the transaction column isn't plain English — it's codes: DD for Direct Debit, SO for standing order, BACS for salary and supplier runs, TRF for transfers, VIS for Visa debit spending. A clean conversion carries the day's date down every row, back-fills the year from the period header, and keeps those codes attached to the right line.

One more thing on scans. Older HSBC statements, or ones you photographed or scanned at a branch, aren't real text — they're images. Copy-paste returns nothing, so you need OCR to read the figures off the picture before any of this works.

Convert an HSBC statement to QuickBooks: the five steps

Run them in order. Each one assumes the previous step came out clean.

1. Gather your HSBC PDFs in date order, with no months missing. A gap means a missing opening balance, and the import that follows it starts from the wrong figure.
2. Convert each PDF to a spreadsheet. Pull the rows into CSV or Excel. Scanned or photographed HSBC statements go through OCR first; even text PDFs need care so the blank date cells and wrapped descriptions don't shunt rows out of place.
3. Reconcile before you reshape anything. Check that BALANCE BROUGHT FORWARD, plus everything in Paid in, minus everything in Paid out, equals BALANCE CARRIED FORWARD — line by line against the Balance column. The first row where your recomputed total stops matching HSBC's printed balance is exactly where a transaction was dropped or misread.
4. Shape the columns for QuickBooks. Cut it down to Date, Description and Amount. Either combine Paid out and Paid in into one signed Amount — paid out negative, paid in positive — or split them into separate debit and credit columns. Drop the £ sign and any thousands commas, and put the date in a format QuickBooks will take (it asks you which during import).
5. Upload it. In QuickBooks Online, open Transactions > Bank transactions, select the HSBC account, choose Upload from file, map the columns when prompted, and import. The lines arrive in the For Review tab, ready to categorise and match.

Mapping HSBC's columns to QuickBooks

QuickBooks Online's manual import expects three things per transaction: a Date, a Description and an Amount. The Amount can arrive two ways. Simplest is one signed column — paid out negative, paid in positive. The alternative is two columns, a debit for spending and a credit for receipts. Either is fine; pick one and hold it across the whole file.

A few things QuickBooks rejects outright, so clear them before uploading: currency symbols, thousands separators inside numbers, blank rows, and merged header cells. A Description that's empty on the odd row is fine. An empty Amount is not.

The running-balance check is the step most converters don't do

Pulling the figures out of an HSBC PDF is the easy half. Knowing the file is *complete* is the hard half, and it's the one most converters skip entirely. A tool can hand you a tidy CSV that's quietly short one transaction — and a tidy file that's wrong is more dangerous than an obvious mess, because you trust it and import it.

Export Bank Statement converts the HSBC PDF, scanned and photographed copies included via OCR, into clean CSV or Excel, then runs the running-balance check itself. It recomputes the totals against the printed BALANCE CARRIED FORWARD and flags any statement that doesn't reconcile, so a dropped or misread line shows up before it reaches QuickBooks rather than at quarter-end. HSBC's blank-date rows are exactly where this earns its place: I've seen a clean-looking export fail the check over two transactions on the same day collapsing into one, and the tick caught it in seconds.

It writes the export in QuickBooks' native bank-import CSV format, so the columns come over the way QuickBooks wants them. Be clear on what it is, though: convert, then upload. It does not push transactions into QuickBooks through a live bank-feed API, and it isn't a bookkeeping service — you decide what gets imported and how it's reconciled afterwards. For the QuickBooks side in detail, the import PDF statements into QuickBooks guide and the QuickBooks CSV import format walkthrough go deeper, and the HSBC UK statement page covers the format and conversion side.