If a transaction description on your Croatian Bank for Reconstruction and Development 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 and wrap across multiple lines inside a statement document, the layout detection engine reads the full-text flow rather than forcing each physical line into its own row. A wrapped description is reconstructed as a single transaction record with its original narrative intact, so no text is truncated or split across columns downstream.
However your Croatian Bank for Reconstruction and Development statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Each column detected on the statement is mapped into the appropriate field in your export. The default mapping aligns date, description, debit, credit and balance columns using the engine's layout recognition, and you can review or reorder that mapping before the file is written. The export preserves the statement's own structure, so the resulting Excel, CSV or QBO file matches the source document column for column.