When your Metropolitan Bank and Trust Company 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. A statement that has been scanned or photographed begins as a picture, not as a data file. The engine reads that picture with optical character recognition, picking up every transaction row and column header it can see, and reconstructs the table underneath. Smudged digits, skewed pages, and uneven lighting are all common; the OCR runs regardless, and the result is treated like any other extraction: every number is held up against the running-balance check. A misread figure that does not add up is not hidden or smoothed over. The row is surfaced for review, flagged with the specific discrepancy, so nothing passes through silently wrong.
Whatever the running balance looks like on your Metropolitan Bank and Trust Company statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement that Convert·Into processes, regardless of how it arrived, is verified against its own printed closing balance. As each row is parsed, the engine maintains a running total; when it reaches the final figure on the statement, the two must agree. If a cell was misread, a date shifted, or a sign inverted, the numbers stop adding up at that exact point. The file is not rejected wholesale. The specific row that breaks the balance is flagged, and you correct or confirm it before export. This single check catches virtually every structural extraction error before the data ever reaches a ledger.