Whichever order your Banque de la Réunion statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Columns are mapped to the export layout automatically. The date, description, debit, credit and running balance fields land in the correct position without manual dragging or renaming. You can review the mapping before you export and adjust any assignment if your workflow uses a different column order.
If the running balance on your Banque de la Réunion 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. Every statement is verified against its own printed closing balance. The engine reads the figure the bank declared on the final page, then re-adds every transaction line in sequence. If a running total diverges from what the statement reports, the row where the break occurred is flagged. You see exactly which entry does not reconcile, rather than losing the whole file to an unexplained rejection. This check catches OCR misreads, truncated amounts and layout shifts before the data reaches your ledger.
If a transaction description on your Banque de la Réunion statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are consolidated into a single row per entry. The engine identifies where a line break belongs to the previous record rather than starting a new transaction, so a supplier name split over two printed lines stays in one cell. The closing balance verification confirms that nothing was duplicated or dropped during that reassembly, giving you a clean, row-per-transaction table ready for export.