When your Rentenbank 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 statements are not a clean data source, but they do not need to be retyped. The engine reads these documents with optical character recognition and then checks every figure against the statement's own printed closing balance. Any misread digit that throws the balance off is flagged, so a speck of dust or a skewed photograph does not leave a silent error in the final file.
If a transaction description on your Rentenbank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that run long and wrap across several lines on the statement are automatically gathered back together into a single row. The engine knows that line breaks in a description do not mark a new transaction, so a wrapped memo stays with its date and amount rather than splitting into fragments that misalign the data.
However your Rentenbank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. During export, every column extracted from the statement is mapped to its correct place in the target file. The transaction date becomes the date column, the credit and debit amounts are split into separate fields, and the running balance is placed in its own column so the reconciliation chain remains visible in Excel or QuickBooks. If the statement uses a layout where an opening balance sits above the table or a closing balance sits below it, those figures are carried into dedicated fields in the output rather than being dropped. The result is a clean, flat table ready for import, with no need to drag formulas or restructure columns in the spreadsheet afterwards.