When your Ostsächsische Sparkasse Dresden 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 brings its own set of challenges. The text on the page is an image of numbers, not a machine-readable table. Convert·Into applies optical character recognition to read that image and reconstruct a complete transaction table from it. The running balance is then verified line by line against the statement's own printed closing figure. A single misread digit, such as a 3 recognised as an 8, will cause that row to fail the check. The row is flagged for review rather than rejecting the whole file, so you can correct the one discrepancy and keep every other correctly read transaction.
Whether you need your Ostsächsische Sparkasse Dresden statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The export step is designed to produce a file you can work with immediately. Convert·Into writes to Excel, CSV or QBO. No further cleanup routine is required inside the output itself because the extraction engine preserves the original date, narrative and amount columns without merging or splitting cells. You choose the format that matches your next workflow: a spreadsheet for manual review, a CSV for import into another system, or a QBO file for direct upload to QuickBooks Online.
However your Ostsächsische Sparkasse Dresden statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping puts each extracted field into the right place in the export, using a predictable assignment that matches standard ledger expectations. The transaction date, description, debit amount, credit amount and running balance are each identified during extraction and placed into their own column in the output. If a statement uses a single amount column with a sign to indicate direction, the engine separates debit and credit entries before the file is written. The mapping is applied automatically; there is no template to configure, and the result is a clean table ready for reconciliation or import.