Whichever order your Ikano Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When you map the columns, you decide exactly which fields land in which export column. The tool shows you a preview of the extracted table with every transaction in its own row. You assign each detected column, date, description, debit, credit, balance, to the corresponding export field once. That mapping is saved, so the next statement document follows the same layout without any reconfiguration. If the statement includes extra columns, reference numbers or payer details, you can include them or leave them out. The exported file keeps your column order and field names, ready for the ledger.
If the running balance on your Ikano 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. The running balance is checked against the statement's own printed closing figure, line by line. If an OCR misread on a digit breaks the tally, that row is flagged for you to review instead of the whole file being rejected. You can correct the single value on screen and confirm the fix. Only rows that actually need attention interrupt the workflow. Every row that adds up clears automatically, so you are never left wondering whether the entire statement converted cleanly.