If a transaction description on your Clydesdale Bank 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 spill into a second or third printed line are treated as a single entry. The engine reads the entire block, not just the first line, and reconstructs the full narrative text so no details are lost and the value stays in its correct column.
However your Clydesdale Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is guided by the statement's own structure. The engine recognises where the date, description, amount and balance sit in the layout and fits each field into the export you have chosen. You can review the mapping before the file is built: drag a column to a different slot, split a combined field, or exclude a line you do not need. The live preview refreshes with every change, so the mapped data is always what you see.
Whether you need your Clydesdale Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Exports are plain and ready to work: clean Excel, CSV or QBO, with no locked sheets, merged cells or hidden rows. The format you pick dictates what the engine writes out: a reconciled CSV for your archive tool, a column-perfect XLSX that drops straight into your working papers, or a QBO file structured for import without remapping. Every number is verified against the statement's own closing figure, row by row, so the exported balance matches exactly.