When your Oberbank 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. OCR reads scanned and photographed statements, lifting the date, description, amount and running balance from every row. Smudged digits, skew and uneven lighting are common in paper captures, so the extracted figures are cross-checked against the running balance printed on the statement itself. A line whose numbers do not tally is flagged for review instead of being silently let through: you see exactly which row needs attention, and the rest of the file remains intact and exportable.
When an Oberbank 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. When a statement runs several pages, the engine stitches them together into one continuous transaction table. Page headers, repeated column labels and carry-forward balances are identified and stripped, so the export begins with the earliest entry and ends with the latest, with no duplicate rows or mid-file summaries left behind. The closing balance across all pages must match the statement’s own printed closing figure; if it does not, the discrepancy is flagged before you export to Excel, CSV or QBO.