If a transaction description on your BluOr 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 wrap across several lines in the original document are kept intact. The engine recognises when a description continues on the next line and merges the text into a single cell, so a split narrative row does not become a broken one in the export. No manual splicing or copy-and-paste repair is needed; the multi-line text arrives as one coherent field, ready for your records.
Once your BluOr Bank statement is uploaded, what you get back depends on which export format you actually need next. The converted data leaves the tool in the exact format your workflow requires. Export options include Excel for spreadsheet review, CSV for direct import into accounting suites, and QBO for QuickBooks Online. Choose the format that fits the next step in your reconciliation process, and the file is ready immediately, with no intermediate cleanup or reformatting step to add.
Whichever order your BluOr Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is direct and stays under your control. The engine identifies the natural columns in the transaction table, from date and description to debits and credits, and you assign each one to its proper place in the export template. If the statement uses an uncommon column order, you reposition the fields once; the mapping remembers your layout for subsequent files, so the same arrangement is applied automatically the next time.