If the running balance on your Bank Audi 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 statement’s printed closing balance is the reference point. Every row in the transaction table is reconciled against that figure. If a line breaks the running total, it is flagged for review rather than buried in the export. You see the discrepancy at the row level, so a single misread digit does not force you to reprocess the entire file.
If the Bank Audi 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 or photographed statement documents are read with OCR before the engine extracts the transaction table. The same balance check applies: the engine sums the extracted rows and compares the result against the printed closing figure. A smudge on the page or a shadow across a number can cause a mismatch, and the flagged row lets you correct it before the data reaches your ledger. Once any flagged rows are resolved, map the columns to your export layout and download the file as Excel, CSV or a QBO-ready format.