When a Frost 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. A statement that runs several pages long is read as a single continuous table, not as separate documents stitched together after the fact. The engine follows the column layout from the first page through to the last, picking up headers, transaction rows and the printed closing balance wherever they fall. Page breaks, repeated boilerplate and blank rows are stripped automatically, so the output is one clean register of every entry in order.
If the running balance on your Frost Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The running balance printed on the statement is verified line by line against the figure the engine calculates from the extracted transactions. If a debit, credit or carry-forward balance does not add up, that row is flagged in the output rather than discarded, and the rest of the file continues unaffected. The printed closing figure on the last page is always checked against the final calculated balance; a mismatch stops the export so you can review the flagged row before numbers reach the general ledger.
Whichever order your Frost Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every extracted column is mapped to the field you choose in the export layout. Date, description, debit, credit and balance are assigned automatically where the column label is unambiguous; where a header is missing or ambiguous, the mapping panel lets you drag the column into the right slot. The same mapping is applied to every page of the statement, so a multi-page file exports with consistent columns in Excel, CSV or QBO.