Whichever order your WaFd Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before the file exports, you map each column into its target position. The transaction table from the statement document is presented as preview columns, and you tell the engine which one holds the date, the description, the debit, the credit and the balance. The mapping step works the same for any layout: select the column from the list, and the export builder aligns it to your ledger's format. Any column that does not serve your reconciliation, such as a running serial number, stays unmapped and is left out of the final file.
If the running balance on your WaFd Bank 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 statement that passes through the engine is verified against its own printed closing figure. The software reads the closing balance exactly as it appears on the statement document and then checks the running balance of the extracted transaction list, line by line, to confirm the two agree. When a row does not add up, the engine flags that specific row for your review instead of discarding the whole extraction. This check is automatic; it runs for every statement, whether the document was a digitally generated file or a scan read with OCR, because reconciliation that traces back to a verifiable number on the original page is the only kind you can trust.