If a transaction description on your Desjardins Group statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long description lines that wrap onto a second row are treated as part of the same transaction, not a separate entry. The engine looks at the transaction date and the running balance to stitch the lines back together, so a multi-line narrative stays attached to its own row.
Once your Desjardins Group statement is uploaded, what you get back depends on which export format you actually need next. A single export step writes every extracted field into the format your workflow needs. You choose the target columns, the date order, and which details travel into the output. Export to Excel for a full workbook you can filter and pivot. Export to CSV for a lightweight file that imports into almost any ledger or analysis tool. Export to QBO and the data maps into the fields QuickBooks expects, with the opening and closing balances included. The row that failed the running-balance check is flagged in the export, not stripped: you decide how to handle it while every clean row moves through.