If the running balance on your Bigbank 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 running balance printed on the statement is checked against the extracted transactions line by line. Each row must carry forward the prior balance, add or subtract the transaction amount, and arrive at the stated figure. Where the numbers do not reconcile, the single row is flagged so that the rest of the file remains usable and nothing passes through silently.
Whichever order your Bigbank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the data is ready for export, each source column is mapped to the correct target field. The date, description, credit, debit and balance columns are placed where the accounting package expects them, and the export keeps the same structure whether you choose Excel, CSV or QBO. No manual column shuffling is needed after the file lands.