When your Oschadbank 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 read with OCR. The engine processes the image, identifies the table layout, and extracts the transaction rows just as it would from a file exported directly by the bank. Any character that the scan renders ambiguously, such as a 3 that could be an 8, is flagged by the running-balance check rather than silently accepted.
When an Oschadbank 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. Multi-page statements do not require splitting or separate uploads. The engine reads through all pages as one continuous record, aligning column positions across page breaks. Headers and footers that repeat on each page are recognised and suppressed so that no duplicate rows appear in the extracted table. A statement document of any length produces a single, ordered transaction register.
However your Oschadbank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is automatic but remains under your control. The engine pairs each detected column in the statement, such as date, description, debit, credit and balance, with its counterpart in the export layout. Before you download, you can adjust the mapping or label assignment to match your firm's chart of accounts or import template. Export to Excel opens straight into your spreadsheet tool; CSV drops into any ledger or analysis pipeline; QBO files import directly without extra formatting steps.