If a transaction description on your Merrill 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 a statement document, the engine preserves the entire text as one record. It reads the statement layout and recognizes where a single entry continues, so a long narrative field does not split into separate rows and break your ledger.
If the running balance on your Merrill 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 file is reconciled against the printed closing figure shown on the statement itself. The system traces the running balance line by line; if any row does not add up, that row is flagged for review. The rest of the extracted data stays intact, letting you correct one discrepancy without rebuilding the whole export.