When your Bank Austria 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. A statement that arrives as a scanned image or a phone photograph is read with optical character recognition. The engine reconstructs the transaction table from what it finds on the page: it identifies columns, rows and the printed running balance even when the source is a pixel-based image rather than a clean data export. Because the running balance is verified line by line against the closing figure printed on the statement itself, any character the OCR misread, such as a 3 read as an 8, is caught immediately. A row that does not add up is flagged for review; the rest of the file is left intact so you can correct the one line and move on, instead of re-processing the entire statement.
When a Bank Austria 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. The same mechanics apply when a statement runs across several pages. The engine stitches the transaction table together across page breaks, maintaining the running-balance chain from the first page to the last. Once extraction is complete the columns are mapped into a clean ledger, ready for export. You choose the format your workflow needs: Excel, CSV or QBO. There is no template to configure and no manual column mapping to set up beforehand.