When a UMB Financial Corporation 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 engine handles the entire document as a single continuous ledger. It follows the transaction table across page breaks and headers, so rows split by pagination are joined again without duplication or gaps. The running balance is recalculated from the first entry to the last, and any interruption in the sequence is flagged, no matter how many pages separate the mismatch.
However your UMB Financial Corporation statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Columns from the extracted transaction table are mapped into a clean export layout automatically. Date, description, debit, credit and balance fields are identified and placed into the correct positions for your chosen format. A row that does not contain enough data for a complete mapping, or that holds a stray label instead of a transaction, is flagged for review rather than silently dropped.
If a transaction description on your UMB Financial Corporation statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long and wrap across multiple lines, the engine recognises that the extra lines belong to the same entry and not to a new row. It reconstructs the full description as a single cell, preventing the split-row errors that fragment one transaction into several in the exported file. This keeps each record intact and ready for categorisation or reconciliation.