When your Evocabank 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. Upload a scanned or photographed statement just as you would a clean electronic file. The engine applies optical character recognition to read every character on the page, then runs the standard extraction pipeline on the result. A single misread digit, like a 3 captured as an 8, will cause the running balance to break: the system flags that row for review rather than discarding the entire file. You correct the one value, and the rest of the statement proceeds normally. The approach means you can work from a phone photo of a printout without rekeying columns by hand.
When an Evocabank 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 are treated as a single continuous record. The engine reads across page breaks, carries forward the running balance, and outputs one unified table. There is no manual stitching or per-page export step. If a page break obscures a transaction or the balance restarts mid-statement for any reason, the verification step catches the inconsistency and marks the affected row. You review the flagged item, confirm the correction, and the full statement exports as one file to Excel, CSV or QBO.