When a United Bank of Albania 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. Statements that run several pages long are handled as a single continuous record. The engine reads across page breaks and merges the transaction table automatically, so a thirty-page file produces one clean ledger. There is no need to split the document or stitch exports together by hand: the conversion runs end to end, preserving every row in order. If a page carries forward a running balance, that figure is checked against the next page to confirm nothing was dropped in the gap.
Should a description on your United Bank of Albania statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When transaction descriptions run long and wrap across multiple lines on the original document, the engine reassembles them into a single cell. The line breaks are recognised as belonging to one entry rather than separate rows, so a multi-line narration or reference number lands intact in the correct description field. This keeps memos and payment details readable in the exported file without manual repair.
Whichever order your United Bank of Albania statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export follows the layout the engine has already identified. Transaction date, value date, description, debit, credit and running balance are aligned to the matching headers in Excel, CSV or QBO output. You can review the mapping before export and adjust it if your chart of accounts uses a different column order; the default assignment reflects the statement's own structure.