When a Rahn & Bodmer 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. A statement that runs several pages long poses no extra difficulty. The engine processes the entire document as a single continuous ledger, stitching the transaction table across page breaks so that every debit, credit and balance figure stays in its correct row. The running-balance check is applied to the full sequence: the closing balance printed on the final page must match the sum of every line, and a break between pages does not interrupt that verification.
However your Rahn & Bodmer statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. When the table is extracted, the engine maps each column into the right place in the export automatically. The date, description, debit, credit and balance columns are identified and aligned without a manual template. If a column is present on the statement but not needed in the export, it is simply excluded; every column that the target format requires is populated with the correct data from the statement.
Whether you need your Rahn & Bodmer statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Once the data is verified, the file is delivered in the exact export format needed next. Choose Excel for a full workbook you can edit, CSV for a plain-text feed into another system, or QBO for a direct import into QuickBooks. The conversion runs the same way regardless of the output format: the extraction and running-balance check are completed first, and only then is the result written into the chosen file structure.