When your Volksbank Stuttgart 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. If a statement was not exported to a clean file but instead arrives as a scan or a photograph, the engine still reads every transaction row. Optical character recognition extracts the figures from the image, and the running-balance verification catches any digit the scan misread: a 3 rendered as an 8, a decimal that blurred into a comma. Layout detection works on the image the same way it works on a native file. The result is a transaction table whose closing balance matches the figure printed on the original page, which means you are not left guessing whether a fuzzy scan produced usable data.
Whether you need your Volksbank Stuttgart statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export the extracted table to the exact format your workflow expects: Excel for your reconciliation workbook, CSV for bulk import, or QBO for direct upload. The same mapped columns appear in whichever format you choose, date to date, description to description, amount to amount. No rekeying of the statement's own figures enters the chain. The engine organises the rows as it found them, so what arrives in your ledger is what the statement printed.
If the running balance on your Volksbank Stuttgart 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 balance. The engine reads the closing figure directly from the document, then tests whether the running total computed from the extracted transactions adds up to that number. A row that does not reconcile is flagged, not dropped; the rest of the file stays intact. You see exactly where the discrepancy sits while you still hold the original statement in front of you.