QuickBooks Error OLSU-1013

Let’s Dive in to see…

How to Fix QuickBooks Error OLSU=1013

Schedule a call to fix QuickBooks Errors
QuickBooks Payroll Error PS060

QuickBooks Bank Feed Error · OL / OLSU Series

How to Fix QuickBooks Error OLSU-1013

QuickBooks displays: "An unexpected error occurred. The branding and profile servers could not be accessed. Click Cancel to discontinue setup and then retry setting up the account for online services again. Error message number: [OLSU-1013]"

At QuickFix Bookkeeping, the key phrase is "branding and profile servers could not be accessed" — this is a Financial Institution Directory (FIDIR) failure, not a credentials error. QB cannot reach the servers that define how to connect to your bank. The FIDIR update is the primary fix.

The QuickFix Bookkeeping Distinction — What OLSU-1013 Specifically Means

OLSU-1013 is not a wrong password error. It is not a company file error. It is a QB bank connection infrastructure failure — the directory that tells QB how to connect to your bank is stale or unreachable.

What FIDIR Is and Why It Matters

FIDIR (Financial Institution Directory) is a file QB maintains that maps each bank to its Direct Connect or Web Connect endpoints, authentication methods, and branding data. When this file is outdated — especially after a bank changes its online banking infrastructure, after a QB update, or after a bank merger — QB cannot establish the connection and displays OLSU-1013. Updating FIDIR tells QB how to reach your bank correctly.

The Test Company File Diagnostic

If FIDIR update and TLS fix don't resolve OLSU-1013, create a new test company file and try connecting your bank from there. If the bank connects successfully in the new company — the problem is your main company file's bank settings, not QB or the directory. If it fails in the new company too — the problem is QB installation or the bank itself.

Manual FIDIR update path — when automatic sync fails: Navigate to C:\ProgramData\Intuit\QuickBooks [Year]\Components\OLB\branding\filist\ and manually replace the fidir.txt file with the current version from QB's servers. This forces the directory to update even when the in-app sync is blocked. The manual path is also the first place to check if FIDIR is corrupt — a zero-byte or very small fidir.txt file indicates corruption.

What Causes QuickBooks Error OLSU-1013?

Outdated Financial Institution Directory (FIDIR)

Primary cause — QB's local FIDIR file is stale and does not contain the current connection information for your bank. This happens after a bank changes its online banking infrastructure, after a bank merger or rebranding, or after a QB update that requires a fresh FIDIR. Updating FIDIR (Banking → Bank Feeds → Bank Feeds Center → Sync all) resolves this immediately.

TLS 1.2 Not Enabled in Internet Explorer

QB uses IE's networking stack for all bank connections. The branding and profile servers require TLS 1.2 for the connection. If TLS 1.2 is disabled in IE's Advanced settings (or TLS 1.0 is the only active version), QB cannot complete the secure handshake with the bank's servers and gets OLSU-1013.

Bank Server Maintenance or Outage

The bank's Direct Connect or Web Connect servers are temporarily unavailable — under maintenance, experiencing an outage, or undergoing infrastructure updates. OLSU-1013 produced by a bank-side outage resolves on its own. Wait 24–48 hours and retry. Log into your bank's website directly to verify the bank's online services are operational before troubleshooting QB settings.

Wrong Bank Feed Mode

QB must be set to Express Mode or Side-by-Side Mode for bank feeds to work properly. If QB is configured in Classic Mode for Bank Feeds, connection attempts can produce OLSU-1013. Change to Express Mode: Edit → Preferences → Checking → Company Preferences → Bank Feed Mode → Express Mode.

Outdated QuickBooks Version

Banks periodically upgrade their online banking security requirements. Very old QB Desktop versions (pre-2017) may not support the current authentication protocols required by banks and will consistently produce OLSU-1013. QB 2016 and earlier are no longer supported for bank feeds.

Corrupted Company File Bank Settings

The bank account setup within the specific company file is corrupted or contains stale connection data. When the connection works in a test company but fails in your main company, the issue is within the main company's bank account configuration — not QB itself.

How to Fix QuickBooks Error OLSU-1013

Start with Method 1 — the FIDIR sync resolves most OLSU-1013 cases immediately.

METHOD 1 Update the Financial Institution Directory (FIDIR) Do this first — resolves most OLSU-1013 cases
1

Automatic update: In QuickBooks → Banking → Bank Feeds → Bank Feeds Center. From the dropdown, select Sync all for this bank. This pushes an FIDIR update from Intuit's servers. After sync completes, retry your bank connection.

2

Manual update (if automatic sync fails): Open Windows File Explorer. Navigate to C:\ProgramData\Intuit\QuickBooks [Year]\Components\OLB\branding\filist\ (ProgramData is hidden — type the path directly). Open the fidir.txt file in Notepad. In a browser, go to Intuit's fidir update page for your QB version, select all text (Ctrl+A), copy (Ctrl+C), paste into fidir.txt (Ctrl+A then Ctrl+V), save and close. Restart QuickBooks and retry the bank connection.

METHOD 2 Enable TLS 1.2 in Internet Explorer Bank server requires TLS 1.2
1

Open Internet Explorer 11 → Tools (gear icon) → Internet Options → Advanced tab. Scroll to the Security section. Uncheck "Use TLS 1.0". Check "Use TLS 1.2". Click Apply → OK. Close all programs and restart the computer — TLS changes require a full restart. Reopen QuickBooks and retry the bank connection. TLS 1.2 is required by most bank Direct Connect servers. Without it, the "branding and profile servers" handshake fails.

METHOD 3 Set Bank Feed Mode to Express + Update QB Wrong mode or outdated QB version
1

Set Express Mode: Edit → Preferences → Checking tab → Company Preferences → in the Bank Feeds section, select Express Mode → OK. QB must be in Single User mode to change preferences.

2

Update QB: Help → Update QuickBooks Desktop → Update Now → Reset Update → Get Updates. Restart QB after update installs. Then retry the bank connection. Banks regularly update their connection protocols and QB updates bring the compatibility patches needed.

METHOD 4 Test with a New Company File + Deactivate and Reactivate Bank Account Isolate company file vs QB installation
1

Test company file: File → New Company → Express Start. Add the bank account in the new company. Try setting up bank feeds. If it connects — your main company file's bank settings are corrupted. If it fails — QB installation or the bank itself is the problem.

2

Deactivate and reactivate (if test company works): In your main company file, go to Chart of Accounts → right-click the bank account → Edit Account → Online Services tab → Deactivate. Close and reopen the company file. Then set up the bank account for online banking again fresh. This clears corrupted bank feed data and creates a clean connection.

METHOD 5 Use Web Connect as a Fallback Bank Direct Connect is unavailable
1

Log into your bank's website directly. Download transactions as a .QBO file (QuickBooks Web Connect format) for the required date range. In QuickBooks → File → Utilities → Import → Web Connect Files → select the downloaded .QBO file → import. This bypasses the Direct Connect branding server entirely and lets you bring transactions into QB without needing the OLSU-1013 connection to be resolved. Use this as an interim solution while troubleshooting the direct connection.

Quick Reference

Your situation Likely cause Start with
OLSU-1013 appeared suddenly, was working before Stale FIDIR after bank or QB update Method 1 — update FIDIR
FIDIR updated — still getting OLSU-1013 TLS 1.2 disabled in IE Method 2 — enable TLS 1.2
Works in new company file, fails in main file Corrupted bank settings in company file Method 4 — deactivate and reactivate
Need transactions now while troubleshooting Direct Connect unavailable Method 5 — use Web Connect import

Frequently Asked Questions

What is FIDIR and where does it come from?
FIDIR stands for Financial Institution Directory — it is a file maintained by Intuit that maps every supported bank to its connection type (Direct Connect or Web Connect), server endpoints, authentication requirements, and branding information. QuickBooks stores it locally at C:\ProgramData\Intuit\QuickBooks [Year]\Components\OLB\branding\filist\fidir.txt. Intuit updates this file when banks change their infrastructure. When your local copy is out of date — because your bank changed something after your last FIDIR sync — QB cannot find the correct server to connect to, producing OLSU-1013. Syncing FIDIR (Banking → Bank Feeds → Sync all) downloads the current version from Intuit's servers and updates your local copy.
Is my bank data at risk when OLSU-1013 appears?
No. OLSU-1013 only prevents QB from downloading new transactions from your bank — it is a connection failure, not a data error. All transactions already in your company file remain intact and unaffected. Your bank account itself is also unaffected — the error is within QB's connection infrastructure, not your actual bank account. You can continue working in QB normally; you simply cannot download new bank transactions until the connection is restored.
Can OLSU-1013 be caused by the bank itself?
Yes — if your bank's Direct Connect servers are under maintenance, experiencing an outage, or undergoing an infrastructure upgrade, OLSU-1013 will appear regardless of your QB or TLS settings. Before spending time troubleshooting QB, log directly into your bank's website to confirm their online banking is operational. Also check your bank's status page or contact their online banking support to confirm whether Direct Connect services are available. If the bank is the cause, the error resolves automatically when their servers come back online — no QB changes needed.

Related QuickBooks Bank Feed Errors

Still Getting OLSU-1013 After FIDIR Update and TLS Fix?

Let QuickFix Bookkeeping Restore Your Bank Feed.

Certified Intuit ProAdvisors — Bank Feed Specialists

Persistent OLSU-1013 after FIDIR, TLS, and mode fixes usually means a bank-specific Direct Connect configuration issue, an account deactivation/reactivation needed, or a QB version compatibility problem that requires specialist diagnosis.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Bank feed restored fast.