If a transaction description on your First Bank of Nigeria 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 run long, they often wrap across two or three physical rows on the page: one line for the merchant name, another for the reference code, a third for a branch identifier. The engine reads these as a single logical transaction rather than separate entries, so you get the full narrative without fragmented line items that break the running balance. It detects when a description continues on the next line because the date, amount and running-balance fields on that row are empty, and it stitches the text back together before extraction. No manual merging is needed before export.
However your First Bank of Nigeria statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is automatic and verified. The engine identifies which column holds the transaction date, which holds the debit and credit amounts, and which holds the description and balance fields, then places each into the correct field in the export. Date formats are standardised during export, and debit and credit amounts are signed correctly: credits positive, debits negative, so the ledger is ready for your accounting package without rekeying. Review the mapped columns once, and the same mapping applies to every statement from that layout.