Whichever order your Conexus Credit Union statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine maps every column it extracts into a standardised structure, preserving the original headers and data types. You choose which columns to keep and where they go in the final file. Numeric columns stay numeric; text columns stay text. This mapping runs the same way no matter which bank issued the statement, so the export lands with columns in a consistent order across statements from different institutions.
Once your Conexus Credit Union statement is uploaded, what you get back depends on which export format you actually need next. Exporting the file is a single step. Once the statement is uploaded and the running balance verified, you pick the format your workflow demands: Excel, CSV, or QBO. The engine handles the translation from what it read on the page into a clean, structured ledger. There is no intermediate editing required and no template to maintain; the same engine that identified the layout also writes the export.
If the Conexus Credit Union statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements pass through OCR before extraction begins. The running-balance check then works as a hard guardrail: every line's arithmetic is verified against the statement's own printed closing figure. If a smudge or a skew misreads a character and the numbers no longer add up, that row is flagged for review rather than silently accepted. The rest of the file remains intact and ready for export.