If a transaction description on your OakNorth Bank 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 engine reads the table structure, not the visual line breaks. A single row that happens to break onto the next printed line is recognised as one transaction. The extraction keeps the description, date, amount and balance together in their correct columns.
If the running balance on your OakNorth Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine checks the running balance against the statement's own printed closing figure. It recalculates the balance line by line from the first entry to the last. If a row does not add up, that row is flagged for review while the rest of the converted file remains intact. You can still export the verified transactions to Excel, CSV or QBO, and you know exactly which item needs attention.