When your Housing and Development 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 statement documents work the same as any other file. The engine reads the image with OCR, locates the transaction table, and extracts every row and column it finds. A grainy photo or a slight skew rarely stops the process; the system is trained to pull numbers from real-world scans, not just pristine digital originals. If the OCR misreads a digit, the downstream balance check will catch it, so you do not have to proof every cell by hand.
Whatever the running balance looks like on your Housing and Development Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is verified against its own printed closing balance. The engine follows the running balance column line by line, recomputing the arithmetic as it goes. A single row that does not add up is flagged for review rather than rejecting the whole file, so a stray misread in a 90-page statement does not force you to restart. You inspect the flagged row, correct it if needed, and the verification resumes from that point.