If a transaction description on your ASN Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long, wrapped transaction descriptions are a common source of misalignment. When a single entry flows across several lines on the page, a naïve extractor often splits it into phantom rows. The engine reads the statement layout structurally, not line by line, so it recognises a wrapped description as one logical row from opening date to final amount. That single transaction arrives in the output exactly as it appears on the statement, with no fragments to rejoin and no phantom entries to delete.
If the running balance on your ASN 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. Every statement the engine processes is checked against its own printed closing balance. The figure printed on the statement is treated as the definitive endpoint. As each row is read, the running balance is recalculated and compared. If a digit is misread, or a line lands in the wrong order, the arithmetic will diverge and that exact row is flagged for review. The rest of the file remains intact. Nothing is silently adjusted and no whole file is rejected, so you can inspect the flagged row, correct it, and move to export with the reconciliation confirmed.