Whichever order your ICA Banken statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The tool maps each column into the right place in the export automatically. It uses a layout engine that recognises where the date, description, debit, credit and balance fields sit on the page, even when the statement’s column order differs from one year or account type to the next. You review the mapping once; the export repeats it exactly for every subsequent file from the same source. If a column holds a mixed value such as a combined debit/credit indicator in a single field, the engine splits it cleanly so your ledger receives separate amounts.
Should a description on your ICA Banken statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When transaction descriptions run long and wrap across multiple lines, the extraction logic stitches them back into a single row. It does not treat every visual line as a new transaction, so a three-line merchant name plus reference code stays with its own date and amount. The running-balance check catches any break where the wrap was misinterpreted, flagging only the affected row instead of rejecting the entire file. You can correct that one entry and proceed, keeping the rest of the statement intact.
Whether you need your ICA Banken statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Getting the file into the exact export format needed next is a single step. Select Excel, CSV or QBO from the export menu and the engine writes columns, number formats and date conventions to match. There is no intermediate clean-up spreadsheet to maintain and no formula that needs stripping before the data reaches your accounting package. The exported file carries the same verified closing balance as the statement, so you can import it straight into reconciliation.