If the running balance on your Banco Azteca statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every figure extracted from the statement is checked against the printed closing balance. A line-by-line verification confirms the running total adds up, so a single misread digit will not go unnoticed. The file is not rejected when a mismatch is found; only the specific row that breaks the total is flagged, letting you review it in isolation while the rest of the data remains ready to use.
If the Banco Azteca statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR and receive the same verification treatment. The engine detects the layout, extracts the transaction table, and then maps the recognised columns into your chosen export structure. Whether the original was a clean digital file or a paper statement captured by camera, the closing-balance check acts as a safety net: anything the scan misread is caught at the row level, so you can correct a single entry and export the rest without redoing the work.