If a transaction description on your Bank of Åland statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. If a transaction description runs long and wraps across several lines on the page, the extraction engine still keeps the whole narrative together. It recognises wrapped text as one logical row, so a payment reference that reads like a short paragraph ends up in a single cell, not spilled across two or three rows of the spreadsheet.
If the running balance on your Bank of Åland 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 put through a line-by-line running-balance verification: the engine reads the closing figure printed on the document and checks that every recorded debit and credit adds up to reach it. If the balance breaks on a particular row, that row is flagged for review. The rest of the file stays intact, so one misfeed does not force you to rebuild the entire conversion from scratch.
Whichever order your Bank of Åland statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the table is clean, you map each extracted column into the right place in the export. Drag the date field onto the date column, the narrative onto the description column, and the running total onto a dedicated reference column if your ledger or tax package expects it. Any bank-specific field that sits outside the core transaction row can be assigned to a custom column, so the exported Excel, CSV or QBO file arrives with the exact structure your reconciliation process already relies on.