When a Nordea 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. The engine handles this correctly. A statement document that runs several pages long is read as a single continuous record. There is no need to split the file, process pages individually, or stitch tables together afterwards. The extraction runs across all pages, and the closing balance on page four is checked against the running total the engine has tracked since the opening balance on page one.
Should a description on your Nordea statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines are similarly kept whole. The engine does not treat a wrapped line as a new row; it reads the multi-line block as one description cell. This prevents the split-row errors that appear when a generic converter breaks a single transfer into two phantom entries, each missing half the text. The result is a clean table with one complete description per transaction, ready for categorisation.
Whatever the running balance looks like on your Nordea statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The running balance is verified line by line against the statement's own printed closing figure. The engine does not assume the statement is correct. It recalculates the balance from the first transaction to the last, and anything that does not add up is flagged on that row. The rest of the file is left intact, so you can review the flagged row and correct it without reprocessing the whole statement. This verification runs on every statement, regardless of length, currency, or layout.