Whichever order your Bank of Scotland statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Once the transaction table is extracted, you map each column to its correct destination in the export file. The mapping is straightforward: date, description, debit, credit and balance are identified automatically and placed into their own columns. You review the assignments in a preview split-screen, where the original statement sits alongside the mapped version. If a column needs a different label to match your ledger or accounting package, you rename it with a click. The column order is also adjustable: drag the description column ahead of the amounts, for instance, if your reconciliation workflow expects it there. No hidden fields are introduced and no extra worksheet tabs appear; what you see in the preview is exactly what you get in the downloaded file.
Should a description on your Bank of Scotland statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that span two or more printed lines are a common source of split-row errors in casual converters. Convert·Into detects these wrapped lines during extraction and merges the continuation text back into a single cell for that transaction. The original multi-line appearance is preserved nowhere in the export: each row represents exactly one transaction, with its full description contained in one cell, keeping the debit and credit columns aligned and the running balance continuous.
If the Bank of Scotland statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. A scanned or photographed statement introduces noise: skewed text, uneven lighting, compressed artefacts that degrade character shapes. Convert·Into reads these with OCR and then subjects every extracted figure to the same running-balance check applied to digital files. If a 5 is misread as a 6 or a decimal point is missed entirely, the balance on that row will not reconcile with the next, and the row is flagged. You review only the flagged items; the rest of the file passes through cleanly, with every verified row exactly as the bank printed it.