When an Andbank 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. When a statement runs several pages long, the engine handles it as one continuous ledger rather than a set of disconnected snapshots. Page breaks, repeated headers, and continuation labels are recognised and removed so that the transaction table stays whole from the first entry on the first page to the closing balance on the last. The running balance is verified across page boundaries: a carry-forward total that does not align with the next page’s opening figure is flagged on the offending row, not buried as a silent mismatch. Multi-page statements export to a single sheet, with columns that stay uniform from top to bottom, so there is no manual splice step in Excel afterwards.
However your Andbank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. During export, each source column from the statement is placed into the correct target field in the output. Debits land in the debit column, credits land in the credit column, and a separate balance column holds the running total exactly as it was verified against the statement’s printed closing figure. Dates, descriptions, and reference numbers stay in their own columns, aligned the same way across every row. You review the mapping once, adjust any assignment if needed, and then export the full file to Excel, CSV, or QBO. The final output preserves the original data without merged cells, split figures, or formatting that would break a formula or import.