When a Techcombank 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 presents no extra steps. The converter reads every page in sequence, stitches the transaction table into one continuous list, and checks the running balance across the page breaks. A balance that carries forward incorrectly, often because a page was scanned at a slight skew, is flagged on the offending row. You review the single discrepancy rather than rechecking the entire file.
Should a description on your Techcombank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description wraps across multiple lines, the default extraction in many tools merges columns or leaves partial descriptions in orphaned rows. Convert·Into recognises the full row boundary by reading the statement's own column alignment, so the wrapped text stays inside the description field where it belongs. That single description cell, however long, maps cleanly into your export schema; a split second line never becomes a ghost entry in the next row down. In the final Excel, CSV or QBO file, every transaction sits on exactly one row with the columns you chose: date, amount, balance and the complete narration kept intact.