If the running balance on your Newcastle Building Society statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine picks up the printed closing balance as soon as the statement is read. It steps through each transaction line, recomputing the running total independently. A mismatch on any row is flagged for your review rather than silently passed through, so you never submit a file where the numbers fail to add up.
Whichever order your Newcastle Building Society statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping gives you full control over what lands where. The engine identifies the transaction table and separates each field: date, description, money in, money out, and any supplementary reference codes present. You review the suggested column assignment on screen, drag a field to a different column if the export target demands a particular layout, and the engine remembers your choice for the rest of the file. The result is a clean ledger where every debit sits in its own column and every credit lines up exactly, ready for Excel, CSV or QBO without manual realignment.