When your ABN AMRO MeesPierson 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 arrives as a scan or a photograph rather than as a clean file exported from a banking portal, the conversion needs to work from pixels, not from text layers. The engine reads the document with OCR, locates the transaction table among everything else on the page, and extracts the rows and columns. A smudge on the paper or a shadow across a phone photo can turn a figure into something the OCR misreads, so every extracted row is checked against the statement’s own printed running balance. A single mismatched entry is flagged for review instead of being silently accepted, and the rest of the file stays intact.
When an ABN AMRO MeesPierson 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 that runs several pages long often repeats headers, carries forward subtotals, or wraps a single transaction description across a line break. The engine stitches the pages together into one continuous table, suppressing duplicate column headings and joining rows that belong to the same entry. The running-balance check runs across the full stitched ledger, so a carry-forward error that only shows up on page four is caught the same way an error on page one would be.