If the running balance on your CRDB 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 running-balance check is applied to every statement. As the engine reads each row, it verifies the printed running balance against the calculated figure derived from the transaction amount and the previous balance. Any row that does not add up is flagged with its exact line number, instead of discarding the entire file. That lets you find a single mistranscribed digit, a skipped entry, or a gap in pagination while the rest of the data is already prepared for export.
Whichever order your CRDB Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the transaction table is clear, column mapping assigns every field to its correct destination. The engine recognises what each column holds, dates, descriptions, debits, credits, and balance figures, and slots them into the matching columns of your chosen output format. You can adjust a mapping if a custom ledger template requires a different arrangement; once set, the same layout applies to every statement you upload afterward.