Whichever order your Sense Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine learns the layout during extraction and maps each column into the right place in the export automatically. Date, description, debit, credit, and balance fields are identified by their content and position, not by a fixed label, so the same mapping works even when the statement's column order or header wording has shifted between issues. This removes the need to copy and paste columns one by one, and it keeps every transaction row aligned under the correct heading. When a column is ambiguous, the mapping heuristics prefer the interpretation that keeps the running balance intact, because a debit wrongly placed in the credit column is easier to catch before the numbers leave the page.
If the running balance on your Sense 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 processed by the engine is verified line by line against its own printed closing figure. Each row's running balance is recomputed from the declared opening balance and the transaction amounts; if the arithmetic does not match the figure printed on the statement, that row is flagged. The engine does not reject the file or refuse to export it. A flag means the rest of the statement is still extracted, and the specific row that broke the sequence is highlighted for review before the data moves into a general ledger. This per-line check catches misreads caused by scan artefacts, blurred digits, or a number that shifted during conversion, all before the discrepancy can reach a reconciliation.
Whether you need your Sense Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Once the statement has been extracted and verified, the file can be taken into the exact format the next step requires. Exports are available as Excel for manual review and adjustment, as CSV for ingestion into a database or a custom script, and as QBO for direct import into QuickBooks. The export preserves the column mapping and the results of the running-balance verification, so the ledger receives the same structure that was checked on screen, with no silent reformatting applied during the save.