When an ABN AMRO 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 document runs several pages long, the table rows do not always align the same way from page to page. The engine reads across page breaks as a continuous set, so transactions are never duplicated or dropped at the boundary.
If the running balance on your ABN AMRO 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. A running-balance column is verified against the printed closing figure that appears at the foot of the statement. The system steps through each row in order and recomputes the balance: a deposit that is read as a withdrawal, or a figure whose digits were transposed, will break that chain. When a row does not add up, it is flagged for review rather than quietly accepted. The rest of the file remains intact, and the closing balance must match the source document before any export proceeds.
If a transaction description on your ABN AMRO statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction description lines that wrap across several rows in the original document are reconstructed into a single record. The engine detects when a new row is a continuation of the previous description rather than a fresh transaction, and joins that text before mapping columns. The output file places the reconciled transaction table into clean columns, ready for export to Excel, CSV or QBO.