When a Maybank 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. Statements that span multiple pages do not require any extra work on your side. Upload the file as it is. The engine reads every page in sequence, stitching the transaction table together across page breaks without duplicating or dropping a row. The running balance is verified continuously from the first line of the statement to the last, so a mismatch on page three is caught just as reliably as a mismatch on page one. A statement that runs thirty pages receives the same line-by-line check as one that fits on a single sheet.
However your Maybank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping happens once the transaction table is extracted and verified. The engine assigns each field (date, description, debit, credit, balance) to a sensible default column in the export format you choose. You can review and adjust those assignments before the file is written, moving a column into the position that your accounting software expects. That review step means every export lands in a consistent shape, ready to import without reordering columns afterwards.