If a transaction description on your Wells Fargo 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 multiple lines inside a statement document, the extraction engine does not treat each new line as a separate row. It reads the full block of text as a single record, preserving the complete description in one cell. That keeps your export clean: no split rows, no orphaned amounts, no follow-up fix-up needed.
When your Wells Fargo statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. The engine processes photographed and scanned statements the same way it handles a cleanly exported document. It applies OCR to lift the table off the image, then runs the same row-by-row verification it would on a digital original. If a smudge or shadow causes a misread, the balance check flags the affected row. You review that one row rather than rechecking the whole file.
Whatever the running balance looks like on your Wells Fargo statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is verified against the closing figure printed on the document. The engine reconstructs the running balance line by line, comparing its own total to the statement's declared final number. If the two do not match, the row where the balance breaks is flagged so you can correct it before the data goes any further. Nothing is rejected outright: a single mismatch stops only the affected row, not the whole conversion.