How does QIF parsing detect dates, splits, and transfers locally?
Every uploaded .qif or .txt file up to 25 MB runs through a state-machine parser inside an isolated Web Worker thread, keeping personal and business ledgers strictly on your computer. It recognizes !Account descriptors alongside seven ledger block types (Bank, Cash, CCard, Oth A, Oth L, Invst, and Invoice) terminated by caret ^ markers.
Running parsing inside an off-thread background context documented by MDN Web Workers API documentation prevents browser tabs from freezing on multi-year Quicken archives. Even thousand-line statement histories decode without triggering network requests or touching remote storage.
- Dates and amounts: Reads
Ddates,TorUamounts, andNcheck numbers or brokerage actions. - Payees and flags: Extracts
Ppayees,Mmemos,Ccleared flags (X/Ras Reconciled,*/Cas Cleared), andLcategories or[Transfer]accounts. - Splits and investments: Captures repeating
S,E, and$split items alongsideYsecurity names,Qshare quantities,Iunit prices, andOcommissions.
Full-ledger exports often include non-transaction QIF metadata blocks such as category trees, memorized payee templates, or class lists before actual account entries. The reader skips those structural blocks cleanly while counting them in skippedMetadataBlocks, leaving account balances focused solely on posted rows.
If your bank provides newer Open Financial Exchange downloads alongside legacy Quicken archives, open our OFX & QFX to CSV converter to parse both statement families consistently during a single bookkeeping close.
Resolving ambiguous MM/DD vs DD/MM dates and split transactions
Quicken Interchange Format files lack an internal metadata header declaring whether slash-separated dates follow month-first US rules or day-first Commonwealth conventions. Misinterpreting date tokens can silently shift January through December entries into the wrong fiscal months during accounting migration.
Auto-detecting US, UK, and apostrophe QIF dates
Before reading field tags, the parser decodes UTF-8 BOM, strict UTF-8, or Windows-1252 character bytes through the browser MDN TextDecoder encoding specification interface. Scanning transaction D lines then selects ymd for four-digit leading years, dmy if the first numeric token exceeds 12, or mdy if the second exceeds 12.
Quicken frequently writes modern two-digit years with an apostrophe, such as 03/15'26, while older archives use 11/04'98. The reader resolves two-digit years with a clean pivot (>= 70 maps to 19xx and < 70 maps to 20xx), and raises an ambiguous-date alert whenever all sample dates stay below 13 so you can switch Date order manually.
Expanding split lines and checking split imbalances
Split receipts store repeating category (S), split memo (E), and dollar ($) tags under one parent transaction, making itemized expense analysis awkward when flattened carelessly. Enabling Expand split lines into separate rows breaks each sub-allocation into its own row in CSV and Excel while marking parent entries cleanly.
If itemized $ lines disagree with the parent T or U total by more than 0.015, the converter flags a split imbalance warning so you catch rounding drift before import. Teams handling European numeric decimals such as 1.234,56, trailing minus signs, or parentheses can also convert German DATEV EXTF booking batches in parallel workflows.
Comparing Standard CSV, Excel workbook, and OFX 1.02 outputs
Modern accounting software dropped QIF support years ago, requiring teams to move legacy files into structured spreadsheets or modern bank-feed envelopes. Selecting the right target under Export format depends on whether you plan to audit rows manually or import them directly into a cloud ledger.
| Export format | Structure & sheets | Encoding & identifiers | Best target workflow |
|---|---|---|---|
| Standard CSV (.csv) | Single table, 13 columns | UTF-8 BOM, sanitized cells | General spreadsheets and script pipelines |
| Excel workbook (.xlsx) | Transactions and Accounts tabs | ISO YYYY-MM-DD dates, native numbers | Multi-account balance audit |
| Excel workbook (.xlsx) Splits | Dedicated Splits sheet included | Shown when split lines exist | Itemized receipt and tax allocation review |
| OFX 1.02 (.ofx) | SGML bank or card feed | USASCII / CP1252, deterministic FITID | QuickBooks, Xero, and Sage bank upload |
The 13-column CSV layout and multi-sheet Excel export
Standard CSV writes 13 columns (Date, Account, Account Type, Payee, Category, Memo, Check # / Action, Status, Amount, Debit, Credit, Transfer Account, Split Line) using normalized ISO 8601 dates. Selecting Excel generates Transactions and Accounts worksheets automatically, plus a third Splits tab whenever split lines are present.
Bracketed category values such as [Harbor Reserve Savings] automatically populate Transfer Account without dropping the main transfer row, making inter-account cash moves easy to audit. Organizations balancing legacy personal exports alongside European statutory ledgers can review French FEC statutory accounting exports ready for tax audit workflows as well.
Exporting QIF archives to OFX 1.02 with NFKD ASCII
Choosing OFX 1.02 (QuickBooks, Xero, Sage) reveals Currency (USD, GBP, CAD, AUD, EUR) and Account type (Checking, Savings, Credit card) selectors to build an OFXHEADER:100 SGML file. Strings undergo NFKD decomposition per Unicode Standard Annex #15 normalization forms before mapping non-ASCII glyphs cleanly for strict CHARSET:1252 readers.
Each generated <STMTTRN> block caps <NAME> at 32 characters, carries overflow descriptions in <MEMO> up to 255 characters, and computes a deterministic 32-bit FNV-1a <FITID> from date, description, amount, and occurrence index. Re-importing the same QIF conversion will therefore never duplicate ledger transactions inside QuickBooks or Xero.
Accounting migration workflow, limits, and tax record rules
Before uploading multi-year archives, click Load sample QIF (harbor-quicken-sample.qif) to see how !Account headers, apostrophe dates, bracketed transfers, and split lines behave across all four sidebar counters (Transactions, Split lines, Credits, Debits). Use Choose another file anytime to swap in your real archive up to 25 MB.
Tip: Always inspect the Date order banner right after loading a UK, Australian, or early-month QIF export, because dates where both day and month are 12 or under default to US
MM/DD/YYYYuntil explicitly switched.
Interactive table previews show up to 300 rows (Date, Account, Payee & Memo with N splits pills, Category, Amount) so dense ledgers scroll smoothly, while export buttons download 100% of parsed records. Standard CSV exports sanitize every string against spreadsheet formula injection while retaining clear schedules aligned with IRS business recordkeeping guidance for supporting documents.
Amount normalization strips currency signs ($, £, €, ¥) and resolves US 1,234.56 commas, European 1.234,56 decimal commas, trailing minus signs, and parenthesized negatives without manual spreadsheet formulas. Validating totals before export takes seconds inside the four summary metrics.
For CSV workflows needing QuickBooks Desktop .qbo output with a custom Intuit bank ID (INTU.BID), pass that exported sheet through our QuickBooks Web Connect QBO statement builder. This browser tool performs technical data translation for informational purposes only and does not constitute accounting, tax, or legal advice; verify final ledgers with a certified public accountant.