1. Read locally
The selected file is read through browser APIs. CSV/TXT uses text parsing, Excel uses an in-browser workbook parser, and QBO/OFX uses transaction-tag extraction. No file body is sent to an application server.
Conversion methodology
What the converter reads, changes, and refuses to guess.
The tools normalize file structure while keeping source rows visible. Ambiguous numeric dates require an explicit confirmation before export instead of a silent accounting assumption.
Last verified July 31, 2026 · Examples and tests use fictional data.
2. Suggest, then expose mapping
For tabular files, header names are used to suggest Date, Description, Amount, Credit, or Debit. The user can inspect and change the mapping before export.
3. Normalize dates
Dates are interpreted only after a selected convention. Invalid dates create row-level errors. Numeric dates that could mean either month/day or day/month show a row-level warning and keep export disabled until the user confirms the selected convention.
4. Normalize amounts
Currency symbols, separators, parentheses, signed values, and split debit/credit columns are converted with decimal arithmetic. The result is shown before download.
5. Preserve row accountability
Every non-empty source row should appear in the preview or produce a source-row error. The tool reports rule IDs so a problem can be reproduced with fictional data.
6. Treat duplicates as warnings
Similar dates, descriptions, and amounts can indicate a repeat or a legitimate recurring charge. BankFileKit does not automatically delete possible duplicates.
7. Generate inspectable output
CSV exports use explicit headers. QBO and OFX readers create an audit CSV that retains supported transaction fields (FITID, memo, and check number) plus available account and statement metadata. QBO beta exports use visible OFX/QBO tags. A generated file is only a candidate until the target software accepts and correctly represents it.
8. Keep product boundaries separate
Formatting does not categorize transactions, make tax decisions, reconcile an account, or verify a QuickBooks company file. BankFileKit is not affiliated with Intuit.
9. Limit analytics
Tool events use only the allow-listed tool name, input/output format, coarse file-size bucket, coarse processing-time bucket, and generic error category. File-derived text is excluded.
10. Test regressions
Automated tests cover parsing, output structure, and analytics sanitization. Production privacy acceptance uses fictional files and Network inspection to confirm that file contents do not leave the browser.