QuickBooks Error OL-221 -- Malformed Bank Feed Response

Error OL-221 interrupts a bank feed download when QuickBooks receives data it cannot parse, and our engineers can restore clean syncing with targeted steps.

QuickBooks Error OL-221 appears during a bank feed download and signals that the financial institution's server returned a response QuickBooks could not interpret. The download halts, and until the underlying data conflict is cleared, subsequent attempts typically produce the same error.

What the Error Message Says

The full message displayed by QuickBooks is:

QuickBooks was not able to complete your request. Please contact your financial institution. (OL-221)

In some installations the message continues with additional text noting that the problem may be caused by the way the financial institution's server is communicating with QuickBooks. The number in parentheses is the distinguishing code.

What the Code Means

The OL-221 code belongs to the OL/OLSU family of bank feed errors. Our engineers classify OL-221 specifically as a response-parsing failure: QuickBooks successfully contacted the financial institution's server, the server acknowledged the request, but the data packet returned contained a field, character, or structure that QuickBooks could not process. Unlike OL-332 or OL-301, which typically point to invalid credentials or server-side outages, OL-221 almost always traces back to malformed or unexpected content within the download payload itself.

What Triggers It

The most common triggers, ordered by how frequently our engineers encounter them, are:

1. A single corrupted or unusually formatted transaction in the pending download. One transaction with an unsupported character, an over-length memo field, or a missing required field can cause the entire batch to fail parsing.
2. A mismatch between the account type configured in QuickBooks and the account type reported by the financial institution. If the bank's server labels the account as a money market account but QuickBooks expects a standard checking profile, the response structure may not align.
3. An outdated or deprecated FIDIR (financial institution directory) file inside QuickBooks. The FIDIR contains the routing and brand identifiers QuickBooks uses to interpret server responses; a stale entry can cause structural mismatches.
4. A temporary server-side formatting change by the financial institution. Some banks push updates to their OFX server that inadvertently produce non-compliant responses, affecting all QuickBooks users on a given brand until the bank rolls back or patches the change.

How to Fix It

Our engineers recommend working through these scenarios in the order shown below.

Scenario 1: A corrupted transaction in the pending batch

1. Sign in to your bank's website directly through a browser and review the transactions that have posted since your last successful download.
2. Look for anything unusual: a memo or payee field containing special characters, an extremely long description, a blank amount, or a duplicate pending transaction.
3. If you find a suspect transaction, add a short note or category to it on the bank's site (many banks allow editing the memo or description). This forces the server to regenerate that transaction's record.
4. Return to QuickBooks and attempt the download again. If the batch parses successfully, the offending transaction has been normalized.

Scenario 2: Account type mismatch

1. In QuickBooks, press Ctrl+A to open the Chart of Accounts.
2. Right-click the affected bank feed account and select Edit Account.
3. Note the Account Type and Detail Type settings.
4. Compare these to the account type shown on your bank statement or online banking portal. If they differ, change the QuickBooks settings to match the bank's classification.
5. Save the change and attempt the download again.

Scenario 3: Outdated financial institution directory

1. Close QuickBooks completely.
2. Download the latest FIDIR update from the brand directory for your QuickBooks version and year.
3. Replace the existing FIDIR.txt file in the QuickBooks installation directory (typically under C:\ProgramData\Intuit\QuickBooks or the equivalent install path).
4. Restart QuickBooks and attempt the bank feed download.

Scenario 4: Temporary server-side formatting change

1. Wait 24 to 48 hours, as many server-side formatting issues are detected and corrected by the financial institution within that window.
2. If the error persists beyond 48 hours, deactivate bank feeds for the account (Chart of Accounts > Edit Account > Bank Feeds Settings > Deactivate), then reactivate and re-link the account using the current brand listing.
3. During reactivation, select your financial institution from the list rather than typing the name manually, ensuring QuickBooks uses the most current connection parameters.

How to Prevent It Recurring

Keep QuickBooks updated to the latest release for your version, as Intuit periodically refreshes the financial institution directory through maintenance updates. Review pending transactions on your bank's website before downloading when you notice unusually long memos or special characters in payee names. If your financial institution offers both Web Connect (manual QBO import) and Direct Connect, try the alternate method when OL-221 appears: downloading a QBO file from the bank's website and importing it via File > Utilities > Import > Web Connect Files bypasses the live server response path and often succeeds where a direct download fails.