When your DLR Kredit 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 or photographed documents are read with optical character recognition. The software identifies text regions, extracts the transaction table, and then verifies the running balance against the statement's own printed closing figure. A mismatch on a single row is flagged for review rather than rejecting the whole file, so a smudge or a skewed photo does not force you to start again.
Whichever order your DLR Kredit statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is automatic: the engine recognises the statement's own headers and places the data into the corresponding fields of your export. Every column you expect to see in the final file, from transaction date to running balance, is placed correctly without a template. You review the arranged columns once, make any small adjustments a particular workflow requires, and then export to Excel, CSV or QBO. The same reviewed structure is applied to every subsequent statement from the same layout, so mapping becomes faster with each upload.