When your Assiniboine Credit Union 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. Scanned or photographed statements bring their own set of risks: shadows on a fold, a smudge over a decimal point, or a camera that straightens a page but skews a column of figures all produce records that look right at a glance but are wrong inside. The extraction engine reads these images with OCR, then verifies every row against the statement's own printed running balance. A value that does not add up is flagged for review instead of silently accepted, so you catch the misread digit before it reaches a reconciliation.
If a transaction description on your Assiniboine Credit Union statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across several lines often fracture into orphaned fragments during extraction: a memo that belongs to one entry is treated as a separate row, splitting the table and burying the real data. The engine recognises multi-line description blocks and stitches them back into a single field before export, so the transaction table stays whole. When the file is ready, choose Excel, CSV or QBO as the output format, and the columns are mapped into the structure your workflow expects.