When a Mirabaud Group 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 rarely arrives as a neat, single table. The engine works end-to-end across the document, joining headers, detail rows and balance columns that span page breaks into one continuous ledger. Nothing is dropped because a line happens to fall near the bottom of a page, and nothing is duplicated where a carry-forward total repeats at the top of the next leaf. The result is a single, dense transaction table that matches the paginated original exactly, ready for export.
If the running balance on your Mirabaud Group statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine verifies the running balance line by line against the statement's own printed closing figure. If a digit was misread, a column was shifted during extraction, or a stray character threw off the arithmetic, that row is flagged rather than failing the whole file. You review only the flagged rows, knowing that everything above and below them already reconciles to the cent.