Whichever order your Bank OZK statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When mapping columns into the export, the engine assigns each field to its correct destination without manual dragging or renaming. The date column lands in the date field, the credit and debit amounts split into their own columns, and the description stays intact. Because the export schema is fixed and predictable, the same mapping is applied consistently to every statement you process, so the output is ready for your ledger as soon as the file finishes converting. Any column arrangement the issuing bank uses is handled the same way: the engine recognises the layout and routes each value to the right place.
Should a description on your Bank OZK statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines are reassembled into a single cell before the export is written. The same line count that makes a printed statement hard to paste into Excel is handled automatically during extraction, without trimming or truncating the text. You get the full description the bank printed, preserved in one row per transaction.