Whichever order your Säästöpankki Group statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before you export, you can map each column into the right place in the export file. The tool shows a preview where the date, description, debit, credit and balance fields are aligned to their standard positions. You can drag any column into a different slot, and you can choose to drop a column entirely if it is not needed downstream. The mapping is saved for the next statement you upload from the same layout, so you set it once and it stays correct.
If the running balance on your Säästöpankki Group 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 that passes through the engine is checked against its own printed closing figure, line by line. The running balance is recalculated from the first transaction to the last, and the final computed figure is compared to the one printed on the statement. If those two numbers match, the file is reconciled. If they do not, the engine flags the discrepant row for review: a single misread digit is isolated rather than having the whole file rejected, so you can fix the one problem and trust the rest.
If a transaction description on your Säästöpankki Group statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long and wraps across multiple lines in the statement, a naive extractor will split one entry into several separate rows. The engine reads the document layout, not just the text, and recognises that the wrapped lines belong together as a single record. The description is assembled back into one cell in the output table, and the transaction keeps its correct date, amount and balance, so you are not left stitching fragmented rows together manually.