When a K&H Bank 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 processes statement documents of any length identically, whether the document runs a single page or several dozen. Upload the file; every page is read in sequence, and the transaction table that begins on page one is picked up again wherever it continues across page breaks. Headers and footers that repeat on each page are identified once and stripped automatically, so the converted data contains the transaction rows only, never duplicated column labels or running-balance carry-over lines. The running balance is verified against the statement's own printed closing figure for the document as a whole, not page by page, so a break across pages does not create a false mismatch.
Should a description on your K&H Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines and spill onto a second row are a common cause of misaligned columns in manual copy-paste workflows. The engine recognises that the extra line belongs to the cell above rather than starting a new transaction, and it merges the wrapped text back into a single row before any column mapping begins. A line-broken narration in the payee field, a split reference number, or a continuation of the memo text is all handled the same way; the row stays whole, and the rest of the columns remain in their correct positions for export.