When a Tangerine 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. When a statement runs several pages, the engine treats the whole document as one continuous ledger. It reads every page, aligns columns across page breaks, and produces a single transaction table without duplicate headers or gaps from the printed footer material. The running balance is verified end to end, so a figure that drifts over a page boundary is caught and flagged before it reaches your export.
Should a description on your Tangerine statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines are kept together as one entry instead of being split into phantom rows. The engine recognises that the second line belongs to the row above it, not to a new transaction, and merges the text cleanly. That keeps your export file tidy and prevents reconciliation errors that come from orphaned description fragments in the ledger.