If the running balance on your NBank 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 transaction row is checked against the closing balance the statement itself declares. The engine walks the running balance column from top to bottom, adding and subtracting each entry in order. If a misread, a missing row or a sign error causes the running total to diverge from the printed closing figure, that specific row is flagged for review rather than silently exported. The rest of the conversion proceeds; you inspect only the flagged item, correct it if necessary, and the whole file reconciles.
When a NBank 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. Multi-page statements are handled as one continuous set of transactions. The engine reads across page breaks and carries forward the running balance without resetting, so a statement spread over several pages produces a single, reconciled table in the export. Columns stay aligned from the first page to the last, and the closing balance verification works across the full document length, not page by page.