Whichever order your Revolut statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the engine finishes reading the statement, it presents the detected transaction table. You can review the column mapping before export and drag any column into the correct slot if the layout requires it. The mapping screen shows exactly where each field will land in the final file, so the exported Excel, CSV or QBO matches your chart of accounts without rework.
Should a description on your Revolut 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 several lines are a common source of split rows in a manual paste. The engine recognises wrapped text and keeps the entire description in a single cell, holding the row together. The running-balance check then confirms that every line still tallies, catching any stray data that slipped into the wrong column during the wrap.