When your USAA 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. If the statement document was scanned or photographed rather than delivered as a clean digital file, the engine applies OCR to interpret the image. Every line of the transaction table is then checked against the statement's own printed closing balance. A digit that the scan misread causes a mismatch, and that row alone is flagged for review rather than forcing the whole file to be re-uploaded.
Whatever the running balance looks like on your USAA statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. A running-balance check runs against every row after extraction. The engine reads the total the statement itself declares and compares it to the calculated running total from the extracted transactions. When the two figures diverge, the specific row where the balance stopped adding up is highlighted, so you review one entry rather than hunting through the entire document.
If your USAA statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Documents that span several pages are handled without splitting or pre-processing. The engine reads the transaction table across page breaks, reassembles the running balance continuously, and presents the full statement as a single table. Export the verified data as Excel, CSV or QBO, with columns mapped to match your ledger's structure.