What you are seeing
QuickBooks is unable to complete this action. [OL-249] Please try again later.
OL-249 is OL-301’s quieter sibling. Both fire while QuickBooks Desktop is talking to a bank or reading a Web Connect file, and both blame the connection — but they usually mean different things, and treating them as the same error sends you down the wrong path.
What Intuit says OL-249 is
OL-249 is a QuickBooks Desktop Bank Feeds error. Intuit’s troubleshooting article puts it in a group with OL-221, OL-231 and OL-232, and the causes it lists for that group are broad: a pending alert on your online banking, a bank that changed between Web Connect and Direct Connect, an inactive account in QuickBooks that still has online banking on, outdated bank details in Intuit’s institution directory, a problem with one of the accounts in the company file, a bank file QuickBooks cannot read, or an unsupported version of QuickBooks.
That list covers live downloads and file imports alike. When OL-249 appears while you are importing a .qbo by hand, the causes narrow sharply, and almost all of them come down to the pairing between the file and the account it is going into.
Where the bank will not give you a Web Connect file at all, you can build the .qbo yourself from the statement PDF, which lets you set the bank ID and the account number to match what QuickBooks already has.
How OL-249 differs from OL-301
OL-301 is generally about the file: its bank ID, its structure, its provenance. OL-249 is generally about the pairing — the file is readable and the ID is recognised, but QuickBooks cannot match it to the account you are importing into.
| OL-301 | OL-249 | |
|---|---|---|
| Intuit’s group | OL-301, 332, 334, 392, 393 | OL-221, 231, 232, 249 |
| Usual cause on a file import | Bank ID (INTU.BID) or a damaged file | Account number, account type or the account’s bank feed setup |
| First thing to check in the file | INTU.BID and the closing </OFX> | ACCTID and ACCTTYPE |
| First thing to check in QuickBooks | Inactive accounts with online banking on | The account number and type on the target account |
The distinction matters because the fixes are different. Chasing the INTU.BID for an OL-249 usually wastes an afternoon, since the BID is often perfectly correct.
Confirm the cause before changing anything
Open the .qbo in Notepad or TextEdit — never in Word or Excel, which will reformat it — and note three values. Then compare them with the account in QuickBooks.
<INTU.BID>01234
<ACCTID>000123456789
<ACCTTYPE>CHECKING- 1In QuickBooks Desktop, open Lists → Chart of Accounts, select the account, and choose Edit Account.
- 2Compare the Bank Acct. No. field with ACCTID in the file, digit for digit.
- 3Compare the account type (Bank or Credit Card) with the file: a BANKACCTFROM block is a bank account, a CCACCTFROM block is a credit card.
- 4Open Bank Feed Settings on the same screen and note whether the account is already connected, and to which institution.
Cause 1: the account number does not match
A Web Connect file names the account it belongs to, and QuickBooks compares that against the account number stored on the account you are importing into. If they differ, the import stops.
They differ more often than you would expect. Banks mask account numbers in statements and not in Web Connect files. Some prefix a branch or sort code in one place and not the other. And an account set up in QuickBooks years ago may hold a number that has since changed.
- 1Open the .qbo in a text editor and find the ACCTID tag. That is the number the file claims.
- 2In QuickBooks, open the account and read the account number recorded on it.
- 3Make them match. Changing the number on the QuickBooks account is usually easier and safer than editing the file.
Cause 2: the account type does not agree
A Web Connect file declares whether it is for a checking account, a savings account or a credit card. Importing a credit-card file into an account QuickBooks holds as a bank account — or the reverse — produces OL-249 rather than a message about types.
This catches people whose credit card was set up as a bank account in the chart of accounts years ago and has worked fine ever since, because nothing before now cared. Try changing the type in Edit Account first; if QuickBooks will not allow it for that account, the cleaner fix is a new account of the right type to import into, with the old one made inactive after its online services are switched off.
Cause 3: stale bank feed settings, often on another account
Intuit’s first fix for this error group is not on the account you are importing into at all. An inactive account that still has online services switched on can disrupt the others, and it is invisible unless you go looking.
- 1Back up the company file.
- 2Open Lists → Chart of Accounts and tick Include Inactive.
- 3Find any account showing the lightning-bolt icon, starting with the inactive ones.
- 4Open Edit Account → Bank Feed Settings → Deactivate All Online Services, and confirm.
- 5Close and reopen the company file, then try the import again.
Some users report that the error only cleared once every account’s bank feed had been deactivated, not just the affected one. That is a bigger step, so take it only after the single-account version has failed.
When it is genuinely the connection
Occasionally OL-249 means what it says. If the same kind of file imported last month and fails today with nothing changed, check the ordinary causes before the exotic ones.
- QuickBooks is not on the current release. Run Help → Update QuickBooks Desktop; Intuit ships fixes for bank feed handling regularly.
- TLS 1.2 is off. Intuit’s steps include checking Internet Options → Advanced → Use TLS 1.2 in Windows, then restarting.
- Your version is past its support date. Each Desktop release loses online services about three years after launch, on 31 May; Desktop 2023 lost them after 31 May 2026.
- The company file is in multi-user mode. Switch to single-user before importing.
- The file is being read from a network path or a synced folder. Copy it to the local disk first — a file that moves under QuickBooks while it reads produces connection errors.
- Your bank has a notice waiting. Sign in on its website and clear it.
The last resort that usually works: create and merge
If nothing above clears it, Intuit’s answer is to give the account a clean bank feed history by creating a fresh account and merging the old one into it. Done carefully, every transaction and reconciliation survives; only the online banking state is reset.
- 1Back up the company file, and accept or clear anything waiting in the Bank Feeds window for this account.
- 2Edit the affected account and add an asterisk (*) to the end of its name, then Deactivate All Online Services on it.
- 3Create a new account of the same type with the original name and the correct account number.
- 4Edit the old account and rename it to exactly match the new one. QuickBooks asks whether to merge; say yes.
- 5Import the .qbo into the merged account, choosing Use an existing QuickBooks account when asked.
This is not free
A merge cannot be undone, and deactivating bank feeds clears the account’s connection state and, on some versions, its matching history. Back up first. If the account has years of reconciled history, try the account number fix before this one.
If you are in QuickBooks Online
QuickBooks Online does not use OL- codes. The nearest equivalent there is "The uploaded file is of a different type than these accounts", which Intuit explains as uploading a file for one kind of account — savings, say — into another. The upload is under Bank transactions → Link account → Upload from file, limited to 350 KB and 1,000 transactions per file, and it now also accepts PDF or image statements in English.