Whichever order your Halifax statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Columns in the extracted table are mapped automatically into the standard fields of your chosen export format: transaction date, description, debit amount, credit amount and running balance. The mapping logic identifies which column in the source holds each value, so you do not need to reassign fields by hand. Debit and credit columns are preserved as separate columns in the export, keeping the original sign convention intact and avoiding the need to merge them into a single signed amount column afterwards.
Should a description on your Halifax statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description runs across multiple lines in the statement, the engine collects the full text into a single cell for that row. It does not split the entry into two false transactions, and it does not leave a blank row behind. The verification step catches any case where a wrapped line disrupts the running-balance sequence, flagging that row for review while the rest of the file remains intact and ready for export.