If a transaction description on your Merkur Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. The engine handles transaction descriptions that wrap across several lines without splitting a single entry into multiple rows. Each line of a wrapped description is read as part of one transaction, not as a separate item. The extraction keeps every detail together under the correct date, amount and running balance column, so nothing is lost or misaligned in the converted file.
Once your Merkur Bank statement is uploaded, what you get back depends on which export format you actually need next. After verification, the statement data is mapped into a clean table and prepared for export. Columns are placed into the standard fields that Excel, CSV and QBO expect; no manual rearranging is required. You choose the format that fits your next step, and the file downloads ready to open or import. The same mapped structure is preserved across all three export options, so switching from one format to another later does not change the layout.
Whatever the running balance looks like on your Merkur Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is checked against its own printed closing balance before any export is produced. The running balance is recomputed row by row from the extracted figures; if a line does not add up, that specific row is flagged for review instead of discarding the whole file. You see exactly where the break occurs, fix the single misread, and then proceed with a fully verified table whose bottom line matches the original document.