When a UniCredit Bulbank statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. Long statements produce identical transaction tables page after page, so nothing is missed or split across exports. The engine treats the batch as a single continuous ledger and picks up the header row wherever it reappears.
Should a description on your UniCredit Bulbank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. The engine recognises transaction-description fields that span multiple lines. It detects where a description wraps into a second or third line without a new amount column, so the text stays whole instead of being chopped at the first line break. A cell that contains several lines of merchant detail, reference codes and terminal identifiers remains a single row in the transaction table. That kept-together text carries through to the export intact, so columns align the same way as they did in the statement. You can export the final table to Excel with each transaction on its own row, to CSV with consistent column counts, or to QBO with the description field holding the full narrative. No manual joining of fragmented cells is needed before you reconcile.