When your BAWAG 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 document that was scanned or photographed rather than exported as a clean file starts as a flat image. The engine reads the transaction table with OCR, then runs the same running-balance verification it applies to any statement: every line is checked against the closing figure printed on the document. If a character was misread, the row is flagged for review instead of letting a broken balance through to the final export.
Whichever order your BAWAG statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is a step you control. The engine groups the extracted data into standard categories: date, description, debit, credit, balance. You review those groupings and confirm that the column labelled "value date" or "posting text" lands in the correct field of your output file. Once the columns are set, the export writes out to Excel, CSV or QBO in the layout your ledger expects, with every mapped column preserved and every verified row intact.