When a Citibank 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 document that runs several pages long is no different from a single-page file to the engine. It reads every page in sequence, stitches the transaction table across page breaks and carries forward the column mapping without interruption. The extracted data arrives as one continuous table in the export, with no duplicate headers and no missing rows where the page turned.
If the running balance on your Citibank 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 statement is checked against its own printed closing balance. The engine reads the declared figure from the statement, recomputes the running balance row by row, and flags any line where the two diverge. A flagged row stays in the export for review rather than causing the whole file to be rejected, so you can inspect the discrepancy, correct it in place and move on.