If the running balance on your State Street Corporation 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 conversion engine does not assume the numbers add up. It reads the running-balance column printed on the statement and verifies it line by line against the bank’s own arithmetic. Any row where the balance does not equal the previous balance plus the transaction amount is flagged for your review before export. This check catches misreads, missing lines, and OCR errors while leaving the rest of the data intact. You get a clean file without silently inheriting a mistake.
If a transaction description on your State Street Corporation statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions often wrap into a second or third line, splitting what the bank printed as one entry into what looks like multiple rows to a simple parser. The engine detects these continuation lines and reassembles each entry into a single row, matching the statement's original record. The description stays whole, and the numbers stay on the row where they belong.
When your State Street Corporation 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. Scanned and photographed statements add noise: skewed text, spotty contrast, characters that blur into one another. The OCR engine extracts the transaction table, and then the running-balance check acts as a safety net. If a misread digit would break the balance, that row is flagged rather than exported unchecked. The result is a spreadsheet you can reconcile, not one you have to rebuild.