If the running balance on your SBAB 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 statement is checked line by line: the running balance after each transaction is recomputed independently and compared with the figure printed on the document. If a row does not add up, that specific row is flagged, but the rest of the file remains usable. This means the closing balance you see in the export is the one the statement itself attests to, not a number the extraction engine accepted without verification.
If a transaction description on your SBAB statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across several lines in the original document are reassembled into a single row before the data reaches your export. The engine recognises where a narrative continues onto the next line and stitches it together, so a single purchase with a sprawling merchant name and reference number stays in one cell rather than scattering across multiple rows. The column mapping stays intact throughout: the date, amount and running balance remain in their correct fields, ready for the output format you choose.