Once your BBBank statement is uploaded, what you get back depends on which export format you actually need next. The final export is a clean, structured file that slots straight into the next step in your workflow. Choose Excel when you need a familiar ledger format for manual review or sharing with a client. CSV is available for fast, lightweight import into any accounting tool that accepts plain-text transaction lists. QuickBooks Online format carries the mapped columns directly into the company file, so there is no rekeying or field matching after the conversion.
If a transaction description on your BBBank 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 wrap across multiple lines in the original document are a common source of mangled data. The engine reads the statement's native row structure and reassembles split lines into a single record per transaction, so a three-line merchant name does not produce three phantom entries. This keeps the transaction count accurate and prevents stray characters from drifting into adjacent fields during export.
However your BBBank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping gives you control over how every extracted field lands in the output. The engine identifies the debit, credit, date and description columns and then lets you confirm or redirect each one. A column that carries a running balance can be dropped entirely if your ledger does not need it, or moved into a reference column when it serves an audit trail. This mapping step runs before any file is written, so the exported spreadsheet or CSV opens with the columns in exactly the order and structure your import requires.