When a Salt 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. Statements that run several pages long come through intact. The engine reads every page in sequence and stitches the transaction rows back into a single table, so a statement that spans three or four pages arrives as one continuous record. There is no split, no duplicate header row, and no manual splicing to do afterwards.
If the running balance on your Salt Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The running balance is verified line by line against the statement’s own printed closing figure. If a row’s computed balance does not match what the statement shows, that row is flagged. It is not discarded: you review the flagged item and correct it in place, while every proven row flows straight through. The check catches the kind of optical misread that silently breaks reconciliation.
Whether you need your Salt Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Getting the file into the exact export format needed next is the point where precision matters most. The extracted table is mapped into columns you name before the export is written: date, description, debit, credit and balance go where your downstream system expects them. You can set column order, rename headers and choose a date style that matches your ledger, then export the complete file to Excel, CSV or QBO in a single step. Nothing relies on a default layout that would still need rework later.