When a BNP Paribas 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. Statement documents that run several pages long are read in full. The engine joins tables that continue across page breaks, so a single transaction that spills from the foot of one page to the top of the next stays intact as one row.
If the running balance on your BNP Paribas 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 printed on the statement is verified line by line. Each transaction's resulting balance is compared against the figure shown on the document; a discrepancy flags only the affected row for review rather than halting the whole file, so you can check a single anomaly without redoing the full conversion.
Whichever order your BNP Paribas statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is automatic: dates are recognised and placed into a proper date column, debit and credit amounts are separated, and narrative text is assigned to a description field. You review the mapping once before export, then save the layout for subsequent statements so the same columns land in the same place every time. The final file exports to Excel, CSV or QBO with the headings you expect, ready for the ledger.