Whichever order your The Co-operative Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export means a statement lands in your accounting tool with every field already aligned to your chart of accounts. The engine identifies the date, description, credit, debit and balance columns from the document's own structure, then fits them into the destination's expected order. You review the mapping once; the engine remembers it for future uploads. If the statement includes a supplementary column such as a transaction type code, it stays available in the output rather than being discarded during conversion.
Should a description on your The Co-operative Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statements whose transaction descriptions run long and wrap across multiple lines can confuse tools that expect one row per entry. Convert·Into reassembles broken lines by reading the document's row positions and indentation, so a description that spills onto a second line is merged back before the row is written to the export. You never need to edit stray line fragments out of the finished file by hand.
Whatever the running balance looks like on your The Co-operative Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Verifying the running balance against the statement's own printed closing figure catches errors that a column-by-column extraction might miss. The engine recalculates the running total from the extracted transactions and checks it against the closing balance shown on the document. If a row does not add up, it is flagged for review rather than silently accepted. You can inspect the flagged item and correct or confirm it before exporting, so the finished file matches the statement exactly.