# Converted QBO File Rejected by QuickBooks? Check This - Author: SimpleBankConvert (https://www.simplebankconvert.com) - Published: 2026-04-03 - Updated: 2026-04-03 - Category: Import errors - Canonical: https://www.simplebankconvert.com/blog/converted-qbo-file-rejected-by-quickbooks > Why a converted QBO file is rejected by QuickBooks: bank ID, account type, date and amount fields, and how to test a converted file before you import. A converted QBO file is rejected by QuickBooks when the converter got one of four things wrong: the bank ID lines, the account type, the date and amount fields, or the transaction IDs. QuickBooks checks all of these before it imports a line. Open the file, check each area, and test it in a spare company first. ## Why does QuickBooks reject a converted QBO file? QuickBooks rejects a converted QBO file when the file doesn't look like a Web Connect download from a bank it knows. A converter rebuilds that download from a CSV or a PDF statement, and any gap in what it writes, such as an empty bank line or a date in the wrong form, gives QuickBooks a reason to stop. The errors you see are mostly the same ones a bank file can raise. Intuit's guide to [fixing Web Connect import errors in QuickBooks Desktop](https://quickbooks.intuit.com/learn-support/en-us/help-article/bank-connectivity/fix-web-connect-import-errors/L8o5eQjO4_US_en_US) lists messages such as "We can't read the file", "Your data was not imported into QuickBooks" and "QuickBooks is unable to verify the Financial Institution information for this download". With a converted file, the bank can't help you; the fix is in the file or the tool that made it. A converted file goes through more hands than a bank download, which gives it more ways to break: - The source CSV or PDF had a fault the converter copied faithfully. - The converter filled in bank details from a template that doesn't fit your bank. - Someone opened the result in Excel or Word and saved it. - The file was renamed from .ofx or .qfx to .qbo without its contents being changed. Work through the four areas below in order. The first two stop a file outright; the last two let it import badly. ## Bank ID lines in a converted QBO file The bank ID lines in a converted QBO file tell QuickBooks which financial institution sent it. QuickBooks reads them before any transaction, and if they are missing, empty or unknown, it refuses the whole file. Converters have to write these lines themselves, because the source CSV or PDF never contained them. Open a copy of the file in a text editor and look near the top for three lines: ORG and FID inside an FI block, and INTU.BID after it. The [OFX 2.2 specification from the Financial Data Exchange](https://financialdataexchange.org/wp-content/uploads/2025/12/OFX-2.2.pdf) defines ORG as the organization defining the institution's name space and FID as the institution's ID within it. INTU.BID is Intuit's own addition; [the bank ID line that makes QBO files picky](/blog/qbo-files-explained#the-bank-id-line-that-makes-qbo-files-picky) explains how QuickBooks uses it. What to look for: - **INTU.BID missing.** Some converters only write the plain OFX parts. The file may be fine as OFX and still fail as QBO. - **Placeholder values.** Numbers such as 0000 or 99999 copied from a sample. - **A bank ID from a different bank.** If the converter picked a default bank, your account in QuickBooks can end up tied to it. ## Does the converted QBO account type match the QuickBooks account? The account type in a converted QBO file has to match the kind of account you import it into. A checking statement should arrive as a bank account and a card statement as a credit card account. When the two disagree, QuickBooks warns, refuses, or brings in every line with the wrong meaning. The OFX specification uses two different account blocks. Bank accounts sit in BANKACCTFROM, with an ACCTTYPE of CHECKING, SAVINGS, MONEYMRKT, CREDITLINE or CD. Credit cards sit in CCACCTFROM, which has an account number but no account type. A converter that writes a card statement as CHECKING has made a bank file out of a card statement. Check: 1. The block type: BANKACCTFROM for bank accounts, CCACCTFROM for cards. 2. ACCTTYPE, for bank accounts, matches the real account. 3. ACCTID holds the right account number. A wrong number can create a new account link instead of adding to the one you meant. Mismatches between file and account have their own guide: [QBO account type mismatches between card and bank files](/blog/qbo-file-account-type-mismatch). ## Date and amount fields a converted QBO file must get right A converted QBO file has to carry dates and amounts in the forms the OFX standard sets out, or QuickBooks reads them wrongly or not at all. Dates are digits only, year first. Amounts are plain numbers with a minus sign for money going out. The source statement used neither form, so the converter must translate both. ### Dates The OFX specification sets one date form: YYYYMMDDHHMMSS.XXX, with an optional time zone, and lets fields be dropped from the right. So 20260314 is a valid posting date for March 14, 2026. Dates written as 03/14/2026 or 2026-03-14 inside DTPOSTED are not the OFX form. Check the statement period dates too, DTSTART and DTEND, which should cover every transaction in the file. Statements that print dates without the year are a known trap for converters, especially across December and January. A transaction on 12/30 in a January statement belongs to the previous year. ### Amounts TRNAMT holds each transaction's amount. The specification says increases and decreases are shown by its sign, and that amounts are signed from the customer's point of view: a card purchase is negative and a card payment is positive. Look out for: - Currency symbols or thousands separators inside TRNAMT. - Every amount positive, which turns withdrawals into deposits. - Signs flipped on a card file, so purchases reduce the balance owed. Compare the file's total against the statement: opening balance plus the sum of every TRNAMT should equal the closing balance. ## Converted QBO transaction IDs that import nothing A converted QBO file can import without an error and still add nothing, because of its transaction IDs. Every transaction carries a FITID, and QuickBooks skips any transaction whose ID it has already recorded for that account. A converter that reuses IDs, or numbers every file from 1, makes new lines look like old ones. Intuit explains the rule in its QuickBooks for Mac article on the [Nothing imported, account up to date error](https://quickbooks.intuit.com/learn-support/en-us/help-article/banking/error-nothing-imported-importing-web-connect-qbo/L305hwiMp_US_en_US): each account and transaction in a Web Connect file has a unique ID, and QuickBooks will not import a transaction with the same ID twice. The OFX specification adds that FITIDs must be unique within an account. Two patterns to look for: - **IDs repeat across months.** January and February both start at FITID 1. February then imports nothing, or only the lines past January's count. - **IDs repeat within the file.** Two different transactions share an ID, and one is skipped. The reverse is just as bad. A converter that makes up fresh IDs each time you rerun it will bring the same transactions in twice. A file that QuickBooks Online reports as empty has a separate checklist in [No Transactions Found in File, fixed for QuickBooks Online](/blog/no-transactions-found-in-file-quickbooks-online). ## Testing a converted QBO file before the real import Test a converted QBO file in a spare company before you import it into your real books. A test company takes a few minutes to set up, and anything that goes wrong there costs nothing. Intuit's Web Connect guide suggests the same test for telling a file problem from a company file problem. ### Pre-import checklist Work through this on a copy of the file: 1. The file opens in a plain text editor and the tags are intact, start to end. 2. The extension is .qbo, and the contents are QBO, not a renamed CSV. 3. ORG, FID and INTU.BID are present and not placeholders. 4. The account block type and ACCTTYPE match the account you will import into. 5. ACCTID is the right account number. 6. Every DTPOSTED is digits only, year first, inside DTSTART and DTEND. 7. TRNAMT values are plain numbers with minus signs for money out. 8. Every transaction has a FITID and none repeat, here or in files you imported before. 9. Opening balance plus the sum of the amounts equals the closing balance. 10. Imported into a test company, the line count and total match the statement. If the test company import hangs rather than failing, the issue may be QuickBooks itself. [QuickBooks Desktop freezing during a Web Connect import](/blog/quickbooks-desktop-freezes-during-web-connect-import) covers what to try. Back up the real company file before the real import. If the file passes in the test company and still fails in yours, disconnect and set up the account again, as Intuit's guide advises. ## When a converted QBO file is the wrong thing to make A converted QBO file is the wrong thing to make when your software takes a simpler file, when the data isn't bank transactions, or when the converter can't write good bank details for your bank. QuickBooks Online accepts a CSV bank upload, so a QBO is a convenience there, not a requirement. QuickBooks Desktop is where QBO really matters. Pick a different file when: - **You use QuickBooks Online and the QBO keeps failing.** A three-column CSV uploads to the same screen with no bank ID to get wrong. - **You use Xero.** A CSV laid out for Xero's statement import is the plainer route for a PDF statement. - **The data is bills or invoices.** A bank file records money moving, not what you owe. Supplier bills belong in a bill import; for Xero, [importing bills from a CSV template](/blog/import-bills-into-xero) shows how. - **The statement is a scan of poor quality.** A converter reading a blurry page can produce a file that passes every check and still has wrong amounts. Check the totals before trusting it. SimpleBankConvert is being built to make CSV and QBO files from PDF statements and to tell you when a statement can't be read cleanly rather than hand over a file with mistakes. It is not open yet; [get started](/get-started) to hear when it is.