If a transaction description on your Chase UK statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a statement document contains transaction descriptions that run long, the text often wraps across several rows. A standard converter may treat each wrapped line as a separate row, splitting a single transaction into multiple fragments. Convert·Into reads the statement table as a whole, recognising when a description cell spans more than one line. The engine groups those lines back into a single transaction record, so the row count in the export matches the actual number of entries on the original statement.
Once your Chase UK statement is uploaded, what you get back depends on which export format you actually need next. You choose the export format that fits the next step in your workflow. Convert·Into produces a clean file in Excel, CSV or QBO, with every transaction in its own row and every value in its own column. The engine does not add or reorder columns on its own: the structure you see in the output reflects the statement table you uploaded, laid out for immediate import into your accounting software or spreadsheet.
Whichever order your Chase UK statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before the export is written, each column is mapped to a standard field so the data lands where you expect it. The date column becomes a date field, the credit and debit amounts are placed in separate signed columns, and the running balance column is preserved alongside the transaction rows. If the statement labels a column differently, the engine aligns it to the correct field automatically; you can review the mapping and adjust it before the file is created.