When an SFIL SA 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 run on for several pages are handled in a single pass. The engine reads every page of the document together, so a transaction that is split across a page break is reassembled into one row. You do not need to scan sections separately, merge files by hand, or worry that a page turn cut a figure in half.
Should a description on your SFIL SA statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statements where a single transaction's description wraps across multiple lines of text are a frequent source of misalignment in manual conversion. The engine reads the full cell, not just the first visible line, and keeps the description together when it builds the table. If a long description line-breaks oddly in the original statement and collides with the next column, the engine tests the column alignment against the running-balance check. A row whose figures do not reconcile with the printed closing balance is flagged for review instead of being discarded. Every column is available for mapping into the export layout you choose: Excel, CSV, or QBO. You decide which fields land in which columns, and the export preserves the categorised data without flattening multi-line transaction details into a single garbled cell.