If a transaction description on your BGL BNP Paribas statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Upload the statement document. The engine identifies its layout and begins extracting the transaction table immediately.
However your BGL BNP Paribas statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. When transaction descriptions span several lines, the engine reads them as a single record rather than splitting the text into separate, broken rows. This keeps each entry whole, so a charge described over three lines still lands in one cell in your export. Multi-line narratives are common in statement documents; the extraction logic treats the description column boundaries as the record boundary, grouping continuation lines together automatically. The result is a clean table where nothing is orphaned in the wrong row.