When your The Royal Bank of Scotland International statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. When a statement has been scanned or photographed, the image must be read with OCR before any data can be extracted. Convert·Into performs this step automatically, applying the same layout detection and running-balance verification it uses on clean digital files. The check catches misread digits: a 9 that the scan interpreted as an 8 will break the running balance, and the row is flagged for review rather than accepted silently.
Whichever order your The Royal Bank of Scotland International statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping the extracted table into a usable export means matching each source column to the right destination field. Convert·Into identifies the date, description, debit, credit and balance columns from the statement layout and places them into clean, consistent columns in the output. You can review the mapping before export and adjust any assignment directly on screen. The running-balance check is preserved through this step, so the closing figure in the exported file matches the printed closing figure on the original statement exactly. Export the result to Excel, CSV or QBO, and the column structure stays intact: no merged fields, no split rows, no manual realignment required.
Should a description on your The Royal Bank of Scotland International statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines are a common failure point in statement conversion. A description line that continues onto the next row can look like a separate transaction to a naive parser, creating phantom entries and throwing off the balance. Convert·Into detects multi-line wrapping as part of its layout analysis and reassembles the description into a single, clean field per transaction. The verification step confirms that the reconstructed rows still satisfy the running balance, so a misassembled wrap is caught the same way a misread digit would be.