Whichever order your Nurol Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Each column in the transaction table is mapped into the correct field in the export. The engine identifies date, description, debit, credit and balance columns by their content and position, not by their printed headings, so the mapping stays accurate even when the statement layout changes. You can review the column assignments before export and adjust any mapping if needed, then save the configuration for future statements.
If the running balance on your Nurol Bank 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. The running balance is verified line by line against the statement's own printed closing figure. Every row is checked: the balance after a transaction must equal the previous balance plus the credit or minus the debit. If a row does not add up, that row is flagged for your review rather than rejecting the whole file. This lets you correct a single misread while keeping the rest of the conversion intact.
When a Nurol 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 engine stitches the tables together into one continuous transaction list. Page headers, repeated column headings and summary balances that appear mid-file are stripped away automatically. The full transaction history lands in a single, unbroken table, ready for export without manual splicing.