When a Nexent 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. Statements that span several pages are handled as one continuous record. Merge or stitch nothing by hand: the engine links the pages of a single statement document into a single transaction table before extraction begins, so the running balance carries across page breaks without interruption.
Should a description on your Nexent Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description wraps across multiple lines, the engine recognises the continuation and keeps the payee, reference and narrative together. Row splitting caused by line-wrap is reversed during extraction; each transaction stays whole in the output, and no phantom rows appear from mid-description line breaks.
Whichever order your Nexent Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is automatic, and you review the result before export. The engine identifies the statement's columns, aligns date, description, debit, credit and balance fields, and shows you a preview with the mapping applied. You can adjust how a column maps if a field is placed differently from what you expect. When you export to Excel, CSV or QBO, every column lands in the correct position, ready for your ledger, and the closing balance in the export matches the closing balance printed on the statement.