If a transaction description on your DHB Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. A statement document often wraps long transaction descriptions across several lines, which can break a simple cut-and-paste into fragments. The engine reads each entry as a whole: it groups the continuation lines back under the originating row before extraction, so a three-line narrative stays together as one transaction rather than splitting into phantom entries.
If the running balance on your DHB 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. Every conversion is checked against the statement’s own printed closing balance. The engine reads the closing figure from the document, walks down the extracted rows line by line recalculating the running total, and flags the specific row where the arithmetic does not add up. You review only that row; the rest of the file proceeds to export.