If a transaction description on your Raiffeisen Albania statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines are read as a single entry. The engine groups the continuation lines together, so a long narrative or reference number stays in one cell instead of scattering into the next row.
However your Raiffeisen Albania statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping gives you control over where every piece of data lands in the export. The engine identifies the transaction table and its headers automatically; you then confirm or adjust which source column feeds into date, description, debit, credit and balance fields. That mapping is remembered for the next statement that shares the same layout, so repeat conversions are a single click. The balance column is verified against the statement's own printed closing figure before the file is released: anything that does not add up is flagged on the specific row, while the rest of the statement exports cleanly. From there, the output goes to Excel, CSV or QBO with the columns in the order you chose.
If the Raiffeisen Albania statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are processed with OCR, and the same running-balance check catches anything the scan misread. A 3 mistaken for an 8, a smudge that fuses two digits: the ledger will not balance, and the row is flagged for review rather than silently accepted. You correct the flagged entries once and export the rest without redoing the whole file.