When a monobank 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. A statement that runs several pages long stays one continuous record inside the tool. The engine reads across page breaks and keeps the transaction table intact, stitching rows that a page boundary would otherwise split. It does not treat each page as a separate file, so a month of transactions arrives as a single list with the correct opening and closing balances that tie the whole period together.
Once your monobank statement is uploaded, what you get back depends on which export format you actually need next. Once the data is clean, the export step formats every column for the system that consumes it next. Choose Excel when you need a workbook to review or archive; choose CSV for a lightweight import into most accounting software; choose QBO when QuickBooks Online is the target ledger. The column mapping applies the same rules to every row, so the file lands in the new format with nothing left to rekey.