If a transaction description on your Envision Financial statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions wrap across multiple lines, the converter reads them as a single record. It follows the statement's own row structure to rebuild split lines before extraction, so long descriptions stay attached to the right transaction.
Once your Envision Financial statement is uploaded, what you get back depends on which export format you actually need next. Once the transactions are extracted and verified, you choose the export format that fits your workflow. Export to Excel for a full spreadsheet ready to review, edit or archive. Export to CSV when you need a lightweight file that imports cleanly into any ledger or reporting tool. Export to QBO to move the data directly into QuickBooks Online. Every format carries the same verified figures; the choice depends on where the numbers go next.
Whichever order your Envision Financial statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is configurable so each field lands in the right place. The default mapping aligns with the exported file's expected layout, but you can adjust it: point the statement's payee column at a contact field, direct the transaction amount at a debit or credit column, and confirm the date format before export completes. The mapping step runs after extraction and balance verification, so every column you assign is already backed by a reconciled row.