If a transaction description on your Bradesco statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. A transaction description that wraps across two or three lines will often break a naive extraction: the second line becomes a phantom row, or the amount lands on the wrong entry. Convert·Into reads the statement layout as a whole and recognises that a line without a date and a balance is a continuation, not a new transaction, so each entry is kept intact.
However your Bradesco statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. During export, every column extracted from the statement is mapped into the correct field for your chosen format. The credit and debit columns are routed to their separate ledger positions, the running balance populates the designated balance column, and the date is normalised to a single standard. You can review the mapping before the file writes, and the same column logic applies whether you export to Excel, CSV or QBO.