How does a QBO Web Connect file differ from a standard OFX file?
A QuickBooks Web Connect (.qbo) file uses the same SGML tag structure as Open Financial Exchange (OFX 1.0.2), with one critical addition: an <INTU.BID> tag inside <SONRS> that QuickBooks Desktop requires to recognize the issuing financial institution. Without that tag, QuickBooks Desktop rejects standard .ofx downloads with import errors.
If your bank already provides a raw CSV download instead of a PDF, you can skip PDF extraction and convert a bank CSV export directly into QBO Web Connect using the same OFX engine.
OFX 1.0.2 SGML structure and the Intuit bank ID (INTU.BID)
Under the Open Financial Exchange 1.0.2 Specification, every transaction is wrapped in a <STMTTRN> block containing <TRNTYPE> (DEBIT or CREDIT), <DTPOSTED>, <TRNAMT>, <FITID>, and <NAME>. The converter also attaches <LEDGERBAL> using the newest verified closing balance when available.
For QuickBooks Web Connect exports, the Intuit bank ID field defaults to 3000. If QuickBooks Desktop refuses the file due to an unsupported institution code, replace 3000 with your bank’s specific INTU.BID number.
Field length limits, ASCII charset 1252, and deterministic FITIDs
QuickBooks Web Connect parsers reject non-ASCII Unicode characters and oversized tags. To guarantee clean imports, src/lib/business/ofx.ts normalizes text to Windows-1252 ASCII, caps <NAME> at 32 characters, moves longer descriptions into <MEMO> (up to 255 characters), caps <ACCTID> at 22 characters, and normalizes <BANKID> to 9 characters.
Each transaction receives a deterministic <FITID> built from YYYYMMDD plus an 8-hex-digit FNV-1a hash (0x811c9dc5). Re-importing overlapping statement dates produces identical FITID values so QuickBooks deduplicates entries automatically.
Choosing between QBO, OFX, QuickBooks CSV, and Xero formats
While Save as starts on QBO (QuickBooks Web Connect), you can switch formats at any time without re-uploading your PDF. Different versions of QuickBooks, Xero, and Quicken prefer specific import containers as outlined in Xero Central Bank Statement Import Documentation.
QuickBooks Desktop relies on Web Connect .qbo files with an INTU.BID header, whereas QuickBooks Online and Xero accept both .qbo and standard .ofx feeds interchangeably. For spreadsheet-first workflows where you want to edit categories before importing, try our Excel and CSV bank statement converter preset.
| Export format | Extension | Best accounting target | Deduplication (FITID) |
Bank ID (INTU.BID) |
|---|---|---|---|---|
| QBO (Web Connect) | .qbo |
QuickBooks Desktop and QBO | Yes (FNV-1a hash) | Included (3000 default) |
| OFX 1.0.2 | .ofx |
Xero, QBO, Quicken, Sage | Yes (FNV-1a hash) | Not required |
| CSV for QuickBooks | .csv |
QuickBooks Online manual upload | Manual date/amount check | Not applicable |
| CSV for Xero | .csv |
Xero manual CSV mapper | Manual date/amount check | Not applicable |
| Excel workbook | .xlsx |
Reconciliation and tax review | Not applicable | Not applicable |
Configuring account types, credit card signs, and running balances
Before clicking Convert transactions, verify that the Account, Currency, and Dates in the statement selectors match your statement layout. Mismatched account types or inverted debit signs are the most common reasons imported transactions land in the wrong register column.
Setting Checking, Savings, or Credit card and 10 supported currencies
Under Account, choose Checking / current (CHECKING), Savings (SAVINGS), or Credit card (CREDITCARD). Credit card mode switches the SGML wrapper to <CREDITCARDMSGSRSV1> and <CCACCTFROM> so QuickBooks maps the feed to a liability card account.
The Currency selector supports 10 major currencies (USD, GBP, EUR, CAD, AUD, NZD, CHF, SEK, NOK, DKK). You only need the last four digits in Account number (ACCTID) to distinguish accounts inside QuickBooks.
Troubleshooting rejected INTU.BID codes and undated rows
If QuickBooks Desktop rejects a .qbo file, verify that your Intuit bank ID is numeric and test either 3000 or your bank’s listed Web Connect ID. Rows without a valid calendar date are automatically skipped from QBO/OFX output because <DTPOSTED> is mandatory; switch to CSV under IETF RFC 4180 CSV Specification rules if you need to inspect undated lines first.
If your European bank provides SWIFT MT940 text downloads instead of PDFs, you can parse structured SWIFT MT940 statements without OCR for direct extraction.
Scanned PDFs with local OCR and zero-upload browser security
Bank statements contain full account histories, vendor payments, and payroll transfers. Running extraction locally keeps sensitive financial records off third-party conversion servers.
Reading scanned statements and verifying every printed balance
When a PDF contains scanned images instead of selectable text, the loader invokes browser-based OCR automatically and flags scanned pages in a status notice. Every row’s money in and money out is reconciled against the printed running balance, highlighting discrepancies in the 300-row preview table.
For SEPA corporate accounts using ISO 20022 XML bank statements, CAMT.053 to CSV & Excel offers native XML balance reconciliation.
Tip: Check All
<N>printed balances add up in the right sidebar before clicking Convert transactions so you never import an OCR digit misread into your QuickBooks register.
Client-side FileReader execution and accounting scope
Files are read directly in browser memory using standard MDN Web Docs FileReader API Reference and Web Worker pipelines, supporting CSV inputs up to 15 MB and multi-month PDF batches. This converter formats bank statement data for operational bookkeeping convenience and does not constitute certified accounting or tax advice; always reconcile imported balances against official bank statements with a qualified accountant.