If a transaction description on your Butterfield Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description wraps across multiple lines inside a statement document, the lines are kept together as a single record. The engine recognises that a second row without its own date or amount is a continuation of the cell above, not a separate transaction. The result is one clean row per transaction, with the full description intact and no split entries that would throw off totals.
However your Butterfield Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is handled so that each field lands in the correct export column. The engine identifies the date, description, debit, credit and balance columns in the statement and lines them up with the matching headers in the output. You review a preview before the export runs: any column that needs a different destination can be reassigned in one click.