When your Vista Bank 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 arrive as fixed images rather than as machine-readable data tables. Convert·Into applies optical character recognition to lift the transaction rows, columns and printed figures from the image, then reconstructs the statement as structured rows inside a table. The engine reads what is actually on the page and does not guess; a smudged 8 misread as a 3, or a folded corner that crops a date, creates a mismatch that the verification step will catch. Standalone OCR tools stop at raw text, which leaves you to re-align columns, reconcile the balance and rekey anything the scan missed. Convert·Into runs the extracted table through the same checks it applies to a native file, so the output is ready to export, not ready to fix.
Whatever the running balance looks like on your Vista Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement processed by Convert·Into is verified against its own printed closing balance. The engine sums the extracted transaction amounts line by line and compares the computed balance to the figure printed on the statement. A mismatch does not reject the whole file; it flags only the row or rows where the arithmetic breaks, so the rest of the statement stays intact and exportable. This single check catches OCR errors, misaligned columns and stray characters in one pass, and it runs on every statement without configuration.
Should a description on your Vista Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statements whose transaction descriptions run long enough to wrap across multiple lines often confound a converter that reads one line per record. Convert·Into detects multi-line descriptions by reading the layout structure rather than relying on a fixed row count per entry, so a wrapped "Payment to Supplier with Reference INV-0047821 Q1 Settlement" remains a single transaction in the output, not two fractured rows. The export preserves the full description in one cell, with columns, dates and amounts kept aligned to the correct record.