Whichever order your VBU Volksbank im Unterland eG statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. During export, the platform maps each extracted column to the correct field in your chosen output format. The date lands in the date column, the description stays in the memo field, and debits and credits are routed to separate amount columns so nothing ends up in the wrong place. This mapping logic uses the layout the engine already identified, which keeps the export structure consistent across every statement in a batch.
When your VBU Volksbank im Unterland eG 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 optical character recognition before the transaction table is built. The engine then verifies the running balance line by line against the statement's own closing figure. When a character is misread, a 3 taken for an 8 for example, that row's balance will not add up; the platform flags the row and surfaces the discrepancy instead of quietly baking the error into the export. You can correct the flagged amount and re-verify the file without reprocessing the whole document.
When a VBU Volksbank im Unterland eG 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 runs several pages, the engine stitches the transaction table together into a single continuous ledger. Pagination artefacts, repeated headers and carried-forward sub-totals are identified from the detected layout and stripped out so the export contains one clean list of transactions. The running-balance check spans the full statement length, confirming that the final balance on the last page matches the closing figure printed in the document, regardless of how many pages were processed.