Whichever order your Ardshinbank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The tool identifies each column in the extracted transaction table: date, description, debit, credit, and the running balance. The mapping engine places each column into the correct field in the export layout so that dates land in the date column and amounts sit in the debit or credit column without manual reordering. The preview lets you verify the column placement before the file is generated, and the export keeps the structure intact for Excel, CSV, and QBO formats.
Should a description on your Ardshinbank 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 several lines, the extraction engine reads the full narrative block and keeps it attached to the correct single row. The running-balance check still verifies every line against the statement’s own printed closing figure; a wrapped description never breaks the reconciliation because the engine treats the multi-line text as one logical record before validating the numbers.