If the running balance on your RBC Bank 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. A statement document carries its own audit trail inside the printed closing figure. Convert·Into reads every row, recomputes the running balance line by line, and compares the result against that printed figure. When a mismatch is detected, the specific row is flagged for review rather than rejecting the whole file, so you can isolate and correct the outlier while trusting the rest of the data.
If the RBC Bank 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. Statements that arrive as scans or photographs introduce a different set of risks: skewed text, faint ink, or a 3 misread as an 8. Convert·Into reads these files with OCR, then subjects every extracted number to the same running-balance check. A mismatch is raised just as with a clean digital statement, catching what the scan misread so you can verify that row and keep the conversion moving. The column mapping and export to Excel, CSV or QBO follow the same path regardless of whether the source was a native file or a photograph, so your workflow stays uniform across every statement that arrives.