If the running balance on your Vancity 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. Every transaction row is verified against the statement's own printed closing figure. The engine reads each row's running balance and checks that it follows from the previous row's balance and the current row's transaction amount. If a row does not add up, say because a digit was misread during extraction, that row is flagged for review rather than discarded. The rest of the file remains intact, so you do not lose a whole batch of work over a single questionable entry. You see the flagged row, check it against the original statement document, and correct it before export. The result is a transaction list whose ending balance matches the figure printed on the statement, confirming that nothing was dropped or mangled along the way.
When a Vancity 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. Multi-page statements are handled as a single continuous extract. The engine processes all pages in one pass and stitches the transaction table together across page breaks, so a line that wraps from the bottom of page three onto page four appears as one unbroken row in the output. Running-balance verification works across the full length of the statement, catching mismatches regardless of which page they fall on. There is no page limit and no need to split the statement document before uploading.
Once your Vancity statement is uploaded, what you get back depends on which export format you actually need next. Once the data is verified, map the columns into the layout your workflow expects and export. Choose Excel, CSV, or QBO. The export carries over the transaction table as you arranged it, with dates, descriptions, amounts and the reconciled running balance all preserved in the format your next tool needs. No template is required, and there is no intermediate clean-up step after export to strip out stray markup or page artefacts.