If the running balance on your HYPO Steiermark statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every transaction row is checked against the statement's own printed closing figure. The engine recalculates the running balance line by line, comparing its computed balance to the one printed on the page. If a row does not add up, the file is not rejected. That specific row is flagged for review, and the rows that do reconcile remain intact and ready for export.
Whichever order your HYPO Steiermark statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Each column from the extracted table is mapped into the correct field in the export. The engine identifies headers like booking date, value date, description and amount, then places them into the corresponding columns of the output file. You can review and adjust the column mapping before the export runs, so the final CSV, Excel or QBO file arrives structured to match your ledger.
When your HYPO Steiermark 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 before extraction begins, so paper records are treated with the same care as a digital file. The running-balance check described above becomes especially valuable here: if a smudge or a slight skew causes a misread, a number that breaks the running balance pinpoints the error for you. The export is not blocked; only the suspicious row is flagged, and everything else processes normally.