If a transaction description on your QNB Group statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across several lines can confuse extraction engines that assume every row is exactly one line. Convert·Into reads the document as a whole, identifying which lines belong together so that a single transaction with a four-line description is captured as one complete record. When a line break happens inside the description field rather than at a genuine row boundary, the engine preserves the full text without splitting it into phantom transactions.
However your QNB Group statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. The service maps the extracted columns into your chosen export layout so that dates fall under the date column, debits and credits appear in the right fields, and the closing balance is placed where your ledger expects it. You review the mapping before the export is built, which means you can correct any column assignment the moment you spot it instead of finding the mistake days later. The same mapping logic applies whether you download the file as an Excel workbook, a CSV file, or a QBO payload: every format gets a properly aligned set of columns.