When a DSK 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 biggest risk is that a page break lands in the middle of a transaction, splitting the description or the amount across two pages. Convert·Into treats the whole document as one continuous stream of data, stitching split rows back together so the output file is clean and each transaction occupies a single row. There is no page limit: the engine reads the entire statement at once, applies its layout model, and produces one complete transaction table regardless of how many pages the original had.
If the running balance on your DSK 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. Every statement is verified by the running balance it prints. The engine reads the closing figure directly from the statement, then steps through every transaction line and recomputes the balance itself. If a row does not add up the engine flags only that row; it does not reject the whole file. That means a single misread digit in a long statement does not block your export. The flagged row stays visible, and you can correct it before finalising the QBO, CSV or Excel output.
If a transaction description on your DSK Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Statements whose transaction descriptions run long and wrap across multiple lines are common. Convert·Into recognises wrapped text and keeps the description attached to its transaction row, rather than treating the second line as a new, empty row. The extracted table maps the full description into a single field, and the column stays ready for export without you having to rejoin split cells by hand.