Current conversion matrix
| Workflow | Input | Output | Status |
|---|
| QuickBooks CSV formatter | CSV, TXT, XLSX | 3- or 4-column CSV | Available locally |
| QBO to audit CSV | QBO | Audit CSV with supported transaction fields and statement metadata | Available locally; not an import guarantee |
| OFX to audit CSV | OFX | Audit CSV with supported transaction fields and statement metadata | Available locally; not an import guarantee |
| CSV to QBO | CSV, TXT, XLSX | Candidate QBO | Beta; Desktop import unverified |
| Excel to QBO | XLS, XLSX, CSV; first worksheet for workbooks | Candidate QBO | Beta; Desktop import unverified |
File and row limits
One file at a time, up to 20 MB and 50,000 transaction rows. Excel input uses the first worksheet. Large files depend on the device's available browser memory.
Date and locale boundary
Input dates can be interpreted as MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD. Numeric dates that could mean either month/day or day/month require an explicit confirmation before download. The current release targets US English and USD workflows.
Text and encoding boundary
CSV/TXT input is read with the browser text API and a leading BOM is removed. Beta QBO output declares US ASCII/Windows-1252 and replaces non-ASCII characters with ?.
QBO/OFX read boundary
The parser reads bank and credit-card transaction blocks with valid DTPOSTED and TRNAMT fields. Its audit CSV retains supported FITID, MEMO, CHECKNUM, and available account/statement fields. Investment, loan, and vendor-specific message sets are not supported.
Unsupported formats
PDF statements, images, QIF, IIF, QBW company files, payroll data, invoices, and complete ledger migrations are not supported. Renaming an extension does not convert a file.
Browser requirements
A current browser with JavaScript, File API, ArrayBuffer, and Blob download support is required. Files remain in browser memory; a desktop browser is easier to review for wide transaction tables.
What support does not mean
A browser parser result is not an endorsement by Intuit or a bank, and it does not guarantee acceptance by every QuickBooks plan, release, account state, or company file.
Report a mismatch safely
Email support@bankfilekit.com with the tool, format, rule ID, and a synthetic reproduction. Do not attach a real bank or transaction file.