Whichever order your Erste Group statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Upload the statement document and the engine identifies the layout and extracts the transaction table on its own.
When your Erste Group 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. Every column the engine finds is mapped into the export automatically: date, description, debit, credit and balance land in the correct fields so you do not have to drag or relabel anything. If the statement uses different column headings or a non-standard order, the mapping adjusts to match what is actually on the page. The output is a flat table with one row per transaction, ready to open in Excel, import into CSV-based tools or push into QBO.
When an Erste Group 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 has been scanned or photographed rather than saved as a clean export, the engine reads it with OCR and runs the same extraction and balance check it would on a born-digital file. A crease, skew or uneven lighting can cause a misread on a single digit, so the running-balance verification catches anything that does not add up. A row that breaks the balance is flagged rather than dropped, letting you correct the one misread value instead of losing the whole transaction.