When a TowneBank 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 document runs several pages long, the engine reads across page breaks without losing a row. A transaction that starts near the bottom of one page and finishes at the top of the next stays whole; nothing is split or duplicated. The full list of entries, from the opening balance to the final page, is assembled into one continuous table before any verification or export runs.
When your TowneBank statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Scanned and photographed statements are read with OCR, and the same structural rules apply as with a clean digital file. The engine isolates the transaction table region, then pulls each row's date, description, amount and balance. If a scan is faint or angled, the running-balance check becomes the backstop: any misread digit that breaks the arithmetic will be flagged, so you are not left trusting a single pass of character recognition.
Whatever the running balance looks like on your TowneBank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The running balance printed on the statement is verified line by line. Each row's balance is compared with the expected value computed from the prior balance and the current transaction amount; any row that does not add up is flagged for review. The whole file is never rejected because of one discrepancy, and the final closing figure must match the statement's own printed closing balance before you export. The export delivers a table with the date, description, amount and balance columns mapped cleanly into Excel, CSV or QBO.