Once your Hancock Whitney statement is uploaded, what you get back depends on which export format you actually need next. The engine maps the extracted data into the export format you select, preserving the original columns so nothing is rearranged or reinterpreted. Choose Excel for a clean, filterable table ready for pivot work, CSV when you need a flat file to feed a script or a legacy system, or QBO to import directly into QuickBooks Online without rekeying a single row. The export runs the whole statement in one pass; you get back one complete file, not a batch of partial ones that must be stitched together later.
When a Hancock Whitney 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 a single document, not a series of disconnected snapshots. The engine reads across page breaks and continues the same transaction table, so a row that spans two pages appears as one entry in the output. A running-balance check is applied end to end, comparing each calculated balance against the printed figure on the statement. When a mismatch is found, that specific row is flagged for review while the rest of the file remains intact and exportable.
However your Hancock Whitney statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping respects the layout the engine detected during extraction: the date column lands in the date field, the description in the description field, the debit and credit amounts each go where they belong, and the balance runs down its own column. Nothing is merged, split, or guessed. If the export destination expects a particular column order or naming convention, the default mapping produces exactly that; you review the alignment once, then rely on it for every subsequent statement.