If a transaction description on your United Bank for Africa statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions often wrap across multiple lines inside a statement document. When a single entry spans several rows, the engine reads the complete text block as one transaction instead of fragmenting it into separate, unrelated lines. This keeps each entry intact, so a long narrative that breaks mid-sentence in the original file arrives in your export as a single, coherent cell.
However your United Bank for Africa statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping moves each extracted field into the correct slot in your chosen export format. The engine identifies the statement's own column headings, then assembles the output so that dates, descriptions, debits, credits and the running balance land in the columns an accountant expects. You review the alignment once, confirm the target layout, and the mapping holds for every subsequent file from that same issuing layout.