Convert HSBC Statements to Xero

One thing has to be right before you import, and it's specific to how HSBC prints things. Every transaction needs to reconcile against the running balance. If a converted HSBC statement doesn't balance, a line was misread or dropped — and importing it means fixing your books later instead of catching the gap now.

Why HSBC's layout makes the reconciliation check matter

Most converters extract an HSBC statement and hand you a grid. You're left trusting that everything came across. HSBC makes that a genuine risk because of one habit: the bank prints the date only on the first transaction of each day. Every row below it leaves the date cell blank.

A careless extractor reads those blanks badly. It can shunt a description onto the wrong line, misalign a column, or merge two payments that happen to share a date. You'd never spot it by eye — your closing figure would just quietly be wrong. So before you download anything, the conversion checks the maths. HSBC labels its opening line BALANCE BROUGHT FORWARD and its closing line BALANCE CARRIED FORWARD, and those two figures work as a checksum. Opening balance, plus everything in Paid In, minus everything in Paid Out, has to equal the carried-forward total. Tie out, and you get a tick. Off by a penny, and the statement is flagged. Most converters don't do this, and on HSBC's date-blanking format it earns its place more than almost anywhere.

How an HSBC statement is laid out

Knowing the shape of the page helps you see when an extraction has slipped. An HSBC statement runs five columns: Date, a transaction-type code, Paid Out, Paid In, then Balance down the right-hand side. The balance recalculates on every line, the brought-forward figure sits at the top, the carried-forward figure at the foot. Note the wording — HSBC says *Paid In* and *Paid Out* where some banks say money in and money out. Same idea, different labels.

The type column is a set of short codes. You'll know them after one read:

• DD — Direct Debit
• SO — standing order
• BACS — salary and supplier payments
• TRF — transfers between accounts
• VIS — Visa debit card spending
• ATM — cash withdrawals
• CHQ — cheques, with CR and DR marking credits and debits

Those codes are worth keeping in the Description when you convert, because in Xero they make a line far easier to recognise weeks later. A row that just reads "£82.40" tells you nothing; "DD — British Gas" tells you everything.

Convert the HSBC PDF to a Xero-ready CSV

Here's the path, start to finish:

1. Upload the HSBC PDF to Export Bank Statement. Text-based exports work, and so do older scanned or photographed copies — scans go through OCR first.
2. Let it read every line. It pulls the date, the type code and description, Paid Out, Paid In and Balance for each transaction, and carries blank-date rows down to the correct day.
3. Check the reconciliation result. It verifies the running balance from brought forward to carried forward. Agree, and you get a clear tick; disagree, and the statement is flagged before you download.
4. Download the CSV in Xero's native bank-import layout, ready to import.

The reconciliation step is the half most converters skip. Pulling text out of a PDF is the easy part. Knowing you pulled out *all* of it is the part that protects your numbers. Catching a misread "£1,180.00" that should read "£1,780.00" while you're still converting costs nothing. Chasing that £600 hole through a reconciled month a fortnight later costs you an afternoon.

What Xero wants in the CSV

Open Import a Statement in Xero and it asks you to map your file's columns. The fields it works with are Date, Amount, Payee and Description, plus an optional Reference. Two details catch people out on HSBC files:

• Date format. Match what you tell Xero on the import screen. HSBC UK statements run DD/MM/YYYY, so set that format when you map — a March date read as a different month is the kind of quiet error you only notice at year-end.
• Signed amount versus separate debit and credit. Xero takes either one Amount column, where money out is negative and money in is positive, or two columns for debit and credit. HSBC prints separate Paid Out and Paid In columns, so a Xero-ready CSV either keeps that split or folds it into a single signed Amount. Both import fine — the one mistake to avoid is mapping a Paid Out figure as a positive amount, which inflates your balance.

Map it once and Xero remembers the layout for that bank account, so the next HSBC import goes faster.

Import the CSV and reconcile in Xero

Go to your HSBC account in Xero, choose Import a Statement, upload the CSV, confirm the column mapping and the date format, then import. The transactions land as statement lines, the same way a feed would deliver them, ready to match against your bills, invoices and existing entries.

Reconciling before you import is what keeps this tidy. If the CSV already balances brought forward to carried forward, you know the month is complete and you're matching a full set of lines, not hunting a phantom that never crossed a page break. Loading several past months at once? The historical-import approach covers ordering and overlaps. Still unsure whether Xero takes a PDF at all? The short answer is in can Xero import PDF bank statements.

An honest note, because it matters: Export Bank Statement converts and verifies; Xero imports. There's no certified bank-feed push forcing HSBC transactions into your ledger from a PDF. If a tool promises one-click API sync straight from a statement file, treat it warily — the file route is the one that holds up.