If a transaction description on your Alterna Savings 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 runs long, the issuing bank often wraps it across two or even three rows inside the table. A simple copy-paste into Excel splits a single transaction into multiple partial rows, breaking the row count and making reconciliation impossible. Convert·Into recognises wrapped lines as continuations of the parent row. It merges them back into one record before extraction, so every transaction lands on a single line in the export.
If the running balance on your Alterna Savings 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. A running balance that no longer adds up is worse than a missing row. Convert·Into verifies every line against the statement’s own printed closing figure: it re-computes each incremental balance from the deposits, withdrawals and opening amount. A row that does not add up is flagged for review. The rest of the file proceeds to export with all other correct transactions intact.
When an Alterna Savings 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. Statement documents that run several pages long introduce their own set of risks: a single file may mix portrait and landscape orientations, the header block can repeat mid-file, and the column positions can shift slightly between pages. Convert·Into processes the entire document as one continuous record. It reacquires the table grid after every page break, maps the columns into your chosen export structure and outputs a single flat table of transactions. Export to Excel, CSV or QBO, ready to import into your accounting package.