If the running balance on your Ziraat 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 reads the printed closing balance on the last page and checks every transaction line against it. If a digit was misread somewhere in the file, the running total will not match and that specific row is surfaced for review. The rest of the statement remains intact; only the row that failed the check needs attention.
If a transaction description on your Ziraat Bank 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 two or three lines, the engine recognises the continuation and keeps it attached to the correct row. It does not split the memo into separate phantom entries, so the export reflects the full narrative exactly as it appears on the original page.
However your Ziraat Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. The extracted table is mapped into a clean set of columns: date, description, debit, credit and balance. You can reorder or rename those columns before export, and the same mapping is applied consistently whether you send the data to Excel, CSV or QBO. No columns are merged and no values are shifted out of place.