If the running balance on your BAC Credomatic 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. The conversion engine reads every transaction line and the running balance printed beside it, then reconciles that sequence against the closing figure on the statement. If a row's arithmetic does not add up, it is flagged for review rather than rejected outright, so one discrepancy does not block the rest of the file.
If the BAC Credomatic 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. A photographed or flatbed-scanned statement is handled the same way as a clean export: the engine applies OCR to pull the transaction table from the image and then runs the same line-by-line balance verification, so a digit misread in the scan is likely to be caught when the running balance breaks.
If your BAC Credomatic statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. For statements that span many pages, the engine stitches the transaction table across page breaks into a single continuous ledger. Columns are mapped into the export format automatically, with every date, description, debit, credit and balance field placed in its correct column, whether the output is a spreadsheet, a CSV file or a QBO file ready for import.