When a BankUnited 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, conversion does not take longer or require extra steps. The engine reads every page in the document as one continuous ledger, so the closing balance on page one flows naturally into the opening balance on page two. There is no page limit: upload a single month or a year of statements, and the extraction runs in a single pass. The only difference you may notice is a slightly longer processing wait for very large files, but the output arrives in the same structured table. Because the tool never splits pages into separate jobs, cross-page transactions are never duplicated or counted twice.
Should a description on your BankUnited 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 spill over several lines inside a statement cell are handled with the same care as single-line rows. The engine recognises that a single entry can wrap across multiple physical lines and reassembles the text into one clean record. When the description wraps, the amount and date columns stay fixed, and the running-balance check still works line by line. If a wrapped line breaks the visual layout of the statement, the extraction logic repairs the row so your exported table has exactly one committed entry per transaction. The result in Excel, CSV or QBO is a flat table with no orphaned text fragments or split amounts.