When The Royal Bank of Scotland statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. A statement document that spans several pages is read as one continuous record, not as a collection of isolated pages. The engine stitches the pages together automatically, aligning the column headers that may repeat or shift position from one page to the next. If a page break splits a transaction row across two sheets, the engine reassembles it before extraction, so no line is lost. The running balance is verified across the entire statement length; a mismatch on page three that ripples forward is caught at the point it first appears, not when the user reaches the final total manually.
When your The Royal Bank of Scotland 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. Scanned and photographed statements are processed with optical character recognition, then subjected to the same checks as a native digital file. The engine does not assume the scan is clean: every figure is verified against the statement's own printed closing balance. If a smudge turns a 5 into a 6, the arithmetic fails and the row is flagged. This is the difference between a conversion that looks right and one that actually reconciles.
If a transaction description on your The Royal Bank of Scotland statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are reassembled before column mapping begins. The engine identifies where the text block ends and the next numeric field starts, so a wrapped narrative line is not mistaken for a separate row. The output keeps the full description in a single cell, preserving the detail while separating it cleanly from the date, amount and balance columns.