When a Fransabank statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. The engine handles statements that run several pages long as a single connected document. Each page is analysed in sequence, and the transaction table is reassembled across page breaks so that a single entry split by a footer or header line is not broken into two fragments. The running balance verification is applied to the full extracted table, and any discrepancy that surfaces after the pages are joined is flagged in the row where the arithmetic no longer holds. The export reflects the same continuous list, with no extra header rows inserted at page boundaries and no gaps where a page break fell.
However your Fransabank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping organises the extracted data into the correct fields for your export. The engine identifies the standard columns from the statement layout, and you can review how each column is assigned before you download the file. If a statement includes entries split across debit and credit columns in its own layout, the engine consolidates them into a single signed amount column by default, and you can adjust that mapping if your ledger expects separate columns. The mapped structure is carried into the Excel, CSV or QBO output exactly as it appears in the preview.