When an Optima 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. When a statement runs several pages long, the engine reads across page breaks as if they were not there. Header rows that repeat on every page are identified and discarded, so the transaction table is stitched into a single continuous list. The closing balance from the final page becomes the reference: every row's running total is checked against it, and any break that would otherwise go unnoticed across a page boundary is flagged the moment it appears.
Should a description on your Optima bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines can fool a naive parser into splitting one row into several. The engine detects these wrapped lines by tracking column alignment and row structure, then reassembles the text into the correct single record before extraction. The result is a clean table where the description sits in one cell, the amounts sit in their own columns, and the running‑balance check still holds because no extra phantom rows were introduced.