When a Consorsbank 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 without a problem. Every page of the document is read in sequence, and the transaction table is reassembled into a single continuous list. There is no page limit, and no extra step to split or merge files before upload. The extraction treats the multi-page document as one source, so a transaction that wraps across a page break stays in its correct row rather than splitting into two.
However your Consorsbank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping each column into the right place in the export is a short, deliberate step. The engine proposes a default mapping for the transaction date, description, debit, credit and balance columns, but you can review and adjust the pairing before the file writes out. That one-time check means the exported CSV, Excel or QBO file arrives with data aligned to the format your ledger expects, without post-export column shuffling.