When your Sallie Mae 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. Even a photographed or scanned statement works. The engine reads the image with OCR and extracts the transaction table, so you do not need to rekey rows by hand. The scan does not have to be perfect: if a digit is misread, the running-balance check described below will flag the specific row that does not add up.
Whichever order your Sallie Mae statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column the engine finds, from date and description to debit, credit and balance, is mapped into a clean column in the export. You review the mapping once and adjust any assignment before the file is written. The export arranges the columns in a consistent order, ready for Excel, CSV or QBO, so the next statement you upload from the same layout arrives already mapped the same way.
If the running balance on your Sallie Mae 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 running balance is verified line by line against the statement's own printed closing figure. If a row's calculated balance does not match what the document shows, that row is flagged for your review: you correct the one discrepancy and the rest of the file stays intact. The check runs on every statement, however it was issued, so the exported numbers always tie back to the source.