If a transaction description on your Ziraat Katılım 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 runs long, the statement may print it over two or three lines while still expecting the reader to treat it as a single row. Convert·Into recognises these wrapped rows during extraction and groups the lines back into one transaction, so a split description does not create phantom entries or misalign the debit and credit columns. The column mapping stays intact, and the exported file shows one clean row per transaction, exactly as the statement intends.
If the running balance on your Ziraat Katılım 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 ends with a line-by-line running-balance check. Convert·Into recalculates the balance after each transaction using the extracted amounts and compares the final figure against the printed closing balance on the statement. A mismatch is flagged for review instead of being silently accepted, so a single misread digit, a stray character from a scan, or a skipped line cannot propagate into the ledger unnoticed.