If the running balance on your Internationales Bankhaus Bodensee 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. A statement document can contain a printed closing balance, and the conversion engine treats that figure as the anchor for the entire file. Every transaction row is read, and the running balance is recalculated from the first entry to the last. If the computed total at any point disagrees with the printed balance on the statement, the mismatch is flagged for review rather than silently accepted, so a single misread digit in a column does not force you to recheck the whole conversion.
If a transaction description on your Internationales Bankhaus Bodensee statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description wraps across several lines inside the statement, many tools split that text into separate rows and scatter the associated amounts. The engine groups the continuation lines back under their parent transaction, preserving the full description and keeping the debit, credit and balance columns aligned. A single entry that spans three or four printed lines stays a single row in the export, with its complete text intact and the running balance check still applied.