When a BMO 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. A statement document that runs several pages long is handled without extra steps: all pages are read together as a single continuous ledger. The extraction engine follows the transaction table across page breaks so no items are lost, and the final closing balance reflects every page.
However your BMO Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. When the transaction table is extracted, you map each column into the right place in the export once, and the engine remembers that mapping the next time a statement with the same layout arrives. Date, description, debit, credit and balance fields are aligned to the correct columns in the target format; you can reorder them, rename headings and suppress any column you do not need. The mapping is a one-time setup that does not have to be repeated for every statement batch.
Whatever the running balance looks like on your BMO Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Before the file exports, the engine verifies the running balance against the statement's own printed closing figure line by line. It recomputes the running total from the extracted amounts and compares the result at each row; any line where the calculated balance and the printed balance disagree is flagged for review instead of letting the discrepancy pass through into the final export. The check catches OCR misreads, skipped rows and transposed digits before they can propagate into your books, so you only need to inspect the rows that the statement itself says do not add up.