Whichever order your SEB Pank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is a structured step that keeps your records consistent. The engine matches the statement’s detected fields to standard accounting columns: date, description, amount, balance. You can review the mapping before export, so a memo field lands in the memo column and a reference number stays with its transaction rather than being dropped during conversion.
Should a description on your SEB Pank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statements whose transaction descriptions run long and wrap across multiple lines are reassembled into one clean row per entry. Instead of splitting a single purchase into three rows because its merchant name spilled over, the engine groups the wrapped lines back together. The result is a flat table where every transaction occupies exactly one row, ready for import into your working file without manual repair.