Whichever order your First National of Nebraska statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. During export, each column from the extracted transaction table is mapped to its correct destination field. The date column becomes the transaction date, the description column becomes the payee or narration, and the debit and credit amounts populate separate columns to preserve the original sign convention. You can review the mapping before export to confirm that every column lands in the right place, keeping the structure consistent across every statement you process.
If your First National of Nebraska statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. When a statement runs across several pages, the engine reads them as one continuous record. Page breaks, repeated headers, and carried-forward subtotals are identified and stripped so that no transaction is counted twice and no gap appears in the sequence. The continuous feed means the exported Excel, CSV or QBO file contains a single, uninterrupted table regardless of how many pages the original statement document spans.
If a transaction description on your First National of Nebraska statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across two or three lines inside the statement are recombined into a single cell. The engine detects when a line belongs to the same entry rather than beginning a new one, so a multi-line narration stays together in the description field. The result is a clean table in which one row holds one transaction, even when the source layout splits the text for spacing.