If the running balance on your Bank of Ireland 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 does not simply pull out a table and assume the numbers are right. It reads the closing balance printed on the statement and then verifies the running balance line by line from the first transaction to the last. If a figure has been misread, a transaction is missing, or the sign on a value is flipped, the running total will not match the printed closing figure. When that mismatch occurs, the specific row that breaks the balance is flagged for review. The rest of the file remains usable; you correct the one flagged entry rather than rechecking the entire statement.
When a Bank of Ireland 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. When a statement spans several pages, the engine reads them as one continuous record. Page breaks do not cause duplicate headers to be treated as new columns, and a table that starts on one page and finishes on the next is stitched together correctly. The closing balance from the final page is the figure used for verification. If a page is missing or out of order, the running balance will not reconcile, and the mismatch points you to the gap.
However your Bank of Ireland statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Before you export, you map each column from the statement into the fields your ledger or package expects. The date column goes to the date field. The description column goes to the memo or narration field. The debit and credit columns, if the statement uses separate money-out and money-in columns, are merged into a single signed amount column for the export. You review the mapping once, and all rows from every statement document follow the same layout. When you export, the reconciled table is delivered as a clean Excel file, a CSV, or directly into QBO, with no stray merged cells or split rows to fix.