If a transaction description on your Laurentian Bank of Canada statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a statement document has transaction descriptions that run long and wrap across multiple lines, the engine reads the full text as one record, not as separate row fragments. It identifies where a single transaction ends by tracking the running balance column and the date pattern, so a payee name split over three lines stays correctly attached to the one debit or credit it belongs to.
However your Laurentian Bank of Canada statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping puts each figure where you need it: the date into one column, the narration into another, the debit and credit amounts separated cleanly. The engine recognises the statement layout without a template, then places every field into its own column so there are no merged cells, no offset rows and no values split across two fields. You review the column assignments once and adjust any mapping before export; the same choices apply to every page and every statement from that layout.
Whether you need your Laurentian Bank of Canada statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. For export, choose the format that matches the next step in your workflow. Excel preserves the table structure and column order for immediate filtering and pivot work, CSV strips everything down to plain text for fast import into any ledger system, and QBO formatting maps the transaction table directly into QuickBooks so the file slots straight into the reconciliation queue. The closing balance on the export matches the printed closing figure on the statement, so the file is ready for the next stage without rekeying.