If a transaction description on your First Nations Bank of Canada statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long, the text on a statement document often wraps across two or three lines before the amount column appears, which confuses generic extraction tools that expect one line per row. Convert·Into reads the grid structure the issuing bank uses, not the visual line breaks, so a multi-line narration stays attached to the correct transaction and the correct amount.
When your First Nations Bank of Canada statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Statements that arrive as a scan or a phone photo carry an extra layer of risk: the raw pixels have to be interpreted before any figures can be checked. Convert·Into applies OCR to read the image, then runs the same running-balance verification it applies to every statement. A row that no longer adds up, whether because a 3 was scanned as an 8 or because a stray mark obscured a digit, is flagged for review rather than silently passed through. Once you have confirmed the figures, the clean transaction table maps into the export layout you need. Column mapping is automatic: the narration lands in the description field, the value and running balance land in their own columns, and the closing balance on the export matches the printed closing figure on the statement. Export the result as Excel, CSV or QBO and proceed to reconciliation without rekeying a single row.