When a Customers Bancorp 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 stitches the transaction table together automatically, so page breaks do not become gaps in the data. The running balance is verified line by line across the full document, and any figure that does not carry forward correctly from the previous page is flagged for review.
Should a description on your Customers Bancorp statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. If transaction descriptions wrap across multiple lines on the statement, the extractor groups the continuation lines under the same row rather than splitting them into separate ghost entries. The resulting table preserves one transaction per row, which keeps the debit, credit and balance columns aligned for import.
If the Customers Bancorp statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. For statement documents that were scanned or photographed, the engine reads the image with OCR and applies the same layout detection and arithmetic checks it uses for digital files. The running-balance verification is especially useful here: if a smudged character or shadow misleads the reader into a transposed digit, the discrepancy is caught before the data reaches your ledger.