When your HSBC statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. A statement document that was printed, scanned or photographed begins as a picture of ink on paper. The engine applies OCR to recover every character, then runs its standard extraction pipeline on the result. Because the running balance is verified line by line against the statement's own printed closing figure, any misread digit is caught at the point where the numbers stop adding up, long before the data reaches your ledger.
If a transaction description on your HSBC statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across multiple lines can fool tools that treat each line as a separate row. The engine reads the layout of the table, not just the text, so it recognises a wrapped description as a single cell and keeps the date, amount and running balance aligned on the correct row.
If your HSBC statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that span many pages are handled in a single pass. The engine stitches the transaction table across page breaks, skips repeated headers and blank separator rows, and produces one continuous export. You review the reconciliation, then choose Excel, CSV or QBO as the output format. Column mapping is automatic: the date column goes to the date field, the description to the memo, the amount to the debit or credit, and the running balance to its own dedicated column, with every row cross-checked against the closing figure printed on the statement.