If a transaction description on your Advanzia Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description is long enough to wrap across two or three physical lines on a page, the resulting table grid is rarely clean. A single purchase can spread its merchant name, reference codes and date across multiple rows in the statement document. The extractor reassembles those fragments into one transaction row. It recognises continuation lines by their indentation, alignment and the absence of a new transaction date in the expected column. Once grouped, each entry carries its full description, amount and running balance in one record, so the export is ready for the ledger without pasting or retyping.
However your Advanzia Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping columns is a few clicks. The engine assigns the detected fields to the standard export columns: date, description, debit, credit and balance. You can reorder the mapping if your bookkeeping software expects a different order, and you can suppress any column you do not need in the exported file. The same mapping persists across every statement document that shares the layout, so subsequent uploads go straight through without repeating the setup.
When an Advanzia Bank 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 spans several pages is processed as one continuous record. The extractor reads from the first transaction on the first page through to the closing balance on the last. It verifies the running balance figure at every line break and page break, flagging only the rows where the arithmetic does not match the printed value. You review the flagged rows, accept or correct them, and export the complete history to Excel, CSV or QBO in a single file.