When a Tesco 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. When a statement runs several pages long, the converter reads all of them as one continuous set of transactions. It does not treat each page as a separate document or require you to split the file before uploading. The engine follows the table across page breaks, picking up the column structure where it left off, so a six-month statement arrives in the same export as a single month would.
However your Tesco Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Before you export the data, the converter maps each column from the extracted table into the corresponding field in your chosen output format. The date column goes to the date field; the description, debit and credit columns each land where they belong in a CSV, Excel or QBO file. You can review the mapping in a preview step and adjust it if the statement uses a non-standard column order, so the exported file matches your ledger's expected structure without manual reordering.
Whatever the running balance looks like on your Tesco Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is checked against its own printed closing balance. The converter reads the balance that appears on the original document and verifies it, row by row, against the running total it reconstructs from the extracted transactions. When a row does not add up, a scanned digit that was misread as the wrong number, for instance, that row is flagged for review rather than accepted silently. The rest of the file remains intact and usable while you correct only the flagged lines.