When an Ameriabank 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, the engine treats the entire document as one continuous ledger. It reads across page breaks and carries column positions forward so that the transaction table remains unbroken. Header rows that repeat on each new page are identified and discarded once, leaving a single clean table. The extraction order follows the original document flow, and every line is kept in sequence so that the chronological order of transactions is preserved.
If the running balance on your Ameriabank 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. Every converted statement goes through a running-balance check against the printed closing figure shown on the document itself. The engine recalculates the balance line by line from the first transaction to the last; if any row causes the total to drift from the statement's own reported number, that specific row is flagged for review. The rest of the file remains intact and usable. This check catches digit-level misreads, line skips and column shifts before the data reaches your working file.