When a Bank of Cyprus 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 conversion engine does not treat each page as a separate document. It reads across page breaks and assembles a single continuous transaction table. Columns stay aligned from the first row of the first page to the last row of the last page; no row is dropped at the boundary where one scanned page ends and the next begins. The running-balance check is applied to the full assembled statement, so a carry-over error that first appears on page three is still caught and flagged.
Should a description on your Bank of Cyprus statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines in the original statement are collapsed into one row per transaction. The engine identifies where a description continues on a second or third line instead of starting a new transaction, so a supplier name, reference number or payment memo stays attached to its own amount, date and running balance. When the statement uses fixed-width columns, the logic is the same: the engine reads the line breaks as formatting, not as separate entries, and reconstructs the single-row transaction for export.