Whichever order your ICR Inbursa statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before export, every column the engine extracts is mapped to a consistent output field. The transaction date, description, debit amount, credit amount and running balance each land in their own column, in the same order every time. If a statement document includes additional detail rows, sub-totals or summary lines, those are isolated so they do not merge into the transaction table. The result is a clean ledger structure that imports directly without re-sorting or manual column reordering.
If the running balance on your ICR Inbursa 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 is verified line by line against the printed closing figure on the statement. When a debit or credit does not net to the next balance shown, that row is flagged rather than the whole file being rejected. You can review the flagged entry, confirm the correct amount and continue, which means the majority of an accurate statement still exports cleanly on the first pass.