Whichever order your LHV Pank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled automatically. The engine reads each column header from the statement document and assigns it to the corresponding field in the export: a date column goes to the date field, a description column to the memo, an amount column to the debit or credit. You can review this mapping before export and drag any column to a different target if your import template expects a specific order or field name.
Should a description on your LHV Pank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When transaction descriptions span multiple lines inside a statement document, the engine keeps the record together as one row. It recognises that a wrapped line is a continuation of the entry above it rather than a separate transaction, so the exported file preserves both the full description text and the correct line count.