If a transaction description on your Banca Ifis statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long, it often wraps onto a second or third line inside the statement table. A generic parser treats each wrapped line as a new row, splitting one genuine movement into two or three phantom entries. The engine reads the full text block as a single description: it recognises that the line break is cosmetic, not structural, and keeps the debit, credit and date columns attached to their original row. The extracted table lands in Excel with each transaction occupying exactly one row, regardless of how many lines the description spanned on the printed page.
However your Banca Ifis statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping your columns into the export is the last step before the file is ready to use. The engine identifies the columns it found (date, description, amount, and any others present) and places each one into the corresponding field of your chosen format. You can review the mapping before the download, so a reference column that is specific to the statement layout ends up in a notes field rather than being discarded. This keeps the data tidy without throwing away anything you might need later.