If a transaction description on your Walser Privatbank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions often wrap across several lines inside the original statement layout. Where a single transaction generates a multi-line entry in the source document, the engine reads the complete text block and ties it back to the same transaction row. A split or orphaned line that belongs elsewhere is reattached, not dropped.
However your Walser Privatbank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping places every extracted field in the correct export position. The engine identifies the statement's own columns (date, description, debit, credit, balance) and lets you confirm how they line up against the target format. Date formats are normalised automatically. Numeric fields keep their original sign and precision, and the running balance is verified against the statement's printed closing figure before export, so a mismatch is caught while you can still check the source.
Whether you need your Walser Privatbank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export to the exact format required next: a single-sheet Excel workbook with a clean table, a flat CSV for bulk processing, or a QBO file structured for direct import. Choose the format that fits the workflow. No template setup is needed, no column renaming afterwards. The file lands ready to reconcile, with every transaction in its original order and every amount exactly as the statement reports it.