When a Raymond James Financial 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. Upload a statement document. The engine detects the bank that issued it and identifies the layout automatically, so there is no template to configure and no profile to select. When the statement runs across several pages the extraction stitches the transaction table together end-to-end: every row from every page is collected into one continuous set. No header row is repeated as a data line, and no page break leaves a gap. You get a single table, not a folder of per-page fragments.
Should a description on your Raymond James Financial 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 two or three lines are handled the same way. The engine recognises that a blank column on the second line is not a missing value: it is the continuation of the description above it. The row is reconstructed so the payment reference stays whole, the amount stays in its own column, and nothing is split into a phantom second row. A description that runs long does not become a sheet that runs ragged.
Whichever order your Raymond James Financial statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Columns are mapped into a clean export table: date, description, debit, credit, and the running balance. The mapping is automatic. You review it before export and can adjust any column assignment that does not suit your workflow, then export the result to Excel, CSV, or QBO. Every export carries the same verified figures: the running balance is checked line by line against the statement's own printed closing figure, and any row that does not add up is flagged rather than buried.