When an HSBC Bank USA 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 file is still a single document. Convert·Into reads it as one continuous table. Page breaks, repeated headers, and page-number inserts are recognised and removed so the transaction list stays whole. No manual merging is needed before upload, and the export lines up one row per transaction from first page to last.
Should a description on your HSBC Bank USA statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines inside a statement cell are kept in one cell in the output. The engine detects multi-line text blocks, even when descenders or narrow columns push a single description onto three or four printed lines. Splitting a description mid-word into separate rows is one of the hardest things to fix by hand; keeping it together in the export preserves the original record and saves revision time.
Whichever order your HSBC Bank USA statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column in the statement is mapped to the export you choose. The date column lands in the date column, the credit and debit amounts each go to their own field, and the running balance is recorded as extracted so it can be cross-checked against the statement's printed closing figure. If a column does not have a natural home (an internal reference code, for instance), it is still exported and labelled clearly, so nothing is left behind. You decide whether to include or drop that extra column in your final workbook, but the raw extraction keeps it available.