If a transaction description on your Aldermore statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long and wrap across multiple lines, the shape of the table can deceive simpler extraction tools. A single entry that needs three printed lines to describe a payment to a supplier can look like three separate rows if the parser only scans for line breaks. Convert·Into reads each row as the full logical record it represents, stitching wrapped lines back into a single transaction before checking the values against the running balance. Extracted data retains the complete narrative text as one field, so exports stay clean: one transaction, one row.
If your Aldermore statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that run several pages long introduce a second challenge: the running balance must be verified across page breaks. A mismatch that begins in the middle of page four can go unnoticed until the final balance is checked, by which point the cause is buried. Convert·Into simulates the bank’s own arithmetic and reconciles each line in sequence, flagging only the specific row where the figures stop adding up. Every page is treated as a continuous ledger, not a collection of disconnected tables, so the full month of activity lands in your export exactly as the statement printed it.