If a transaction description on your Delen Private Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that run long and wrap across multiple lines are kept together as a single entry, not split into separate rows. The engine reads the statement's own structure to recognise where a description ends and the next row begins, so a multi-line narrative stays attached to the right transaction.
If the running balance on your Delen Private Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every statement is verified against its own printed closing figure. The engine recalculates the running balance line by line, checking that each carry-forward matches what the document shows. A row whose balance does not add up is flagged individually; the rest of the file remains intact and ready for review.
Whether you need your Delen Private Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Column mapping puts every field where you need it. The engine identifies the statement's table structure automatically, then lets you confirm which columns map to which fields in the export. You can reorder, rename or omit columns before exporting, and the same mapping is reused the next time a similar layout is uploaded. The converted data exports directly to Excel, CSV or QBO: no intermediate cleanup step, no template to maintain, just the format your next workflow expects.