If a transaction description on your LGT Group statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are common. The extraction engine reads each row in context, linking continuation lines back to their original transaction so nothing is orphaned or misaligned. A wrapped memo column stays attached to its parent record rather than breaking into a stray row that would need manual repair.
However your LGT Group statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping columns into the right place in the export is the step that turns raw data into usable ledger entries. Date, description, debit, credit and balance are identified automatically and assigned to the corresponding field in the chosen output format. You can review and adjust the mapping before export: drag a column to a different destination, or leave a column unmapped if the export does not need it. Every column that is mapped appears in the exported file exactly as assigned, and the final closing balance is verified against the statement one last time. When the file is ready, export to Excel, CSV or QBO in a few clicks.