When your AFG Holding 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 or photographed statement documents carry the same data as a clean electronic file, but they arrive as images. The engine applies optical character recognition to find the transaction table in the image, reading each date, description, debit, credit and running balance cell. A smudge that turns a 3 into an 8 or a folded corner that clips a digit is the most common failure mode for image-based statements, so the result is never trusted blindly. Every row's running balance is recomputed from the one above it, and the final figure is compared against the closing balance printed on the statement itself. When a row does not add up, the engine flags only that row and lets you correct the one misread, rather than rejecting the whole file.
Whatever the running balance looks like on your AFG Holding statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The running balance check is the core of the conversion's accuracy guarantee. As each transaction is extracted, the engine verifies that the stated running balance matches the expected arithmetic: previous balance plus credit, minus debit. The last line's verified figure must equal the statement's own printed closing balance. A mismatch anywhere in the chain stops the review and highlights the exact row where the numbers break, so you fix one value instead of hand-auditing every line. That single reconciliation step is what lets you trust the exported Excel, CSV or QBO file without rekeying the whole statement.