Fidelity serves roughly 90 days of downloadable activity, while your statements go back years. Upload them and get a clean QFX that imports straight into Quicken, dated, signed, and ready to reconcile.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
Fidelity is really several different connections wearing one name, and which one you are on decides whether the problem is fixable at your end. Fidelity HSA accounts are the clearest case: Quicken support staff have said Fidelity sends HSA data in a different format from its brokerage and IRA accounts, without the transaction description Quicken requires, so those transactions cannot be processed at all. Deactivating and reactivating will not fix that one. Fidelity NetBenefits, the 401(k) side, is a separate institution entry with its own history of downloading nothing or downloading securities Quicken cannot identify. For everything Fidelity will not send, converting the Fidelity PDF statement to a QFX file and importing that gets the transactions into the register without touching the connection.
Fidelity fails in several distinct ways depending on the account type, and the fix for one is useless on another. Identify which of these you are looking at before you change anything.
The connection reports success, the balance may update, and not one transaction appears. Quicken tracked this under ticket 1999090 and the explanation given is that Fidelity does not send a transaction description for HSA accounts, which Quicken treats as a required field. There is no setting on your side that changes it.
Fidelity NetBenefits is a separate institution entry from Fidelity Investments. Users have reported it completing without error and adding no transactions, and reported Fidelity proprietary funds arriving as an unknown security with no ticker or CUSIP, coded to the wrong transaction type.
Fidelity appears in the institution list more than once, including separate entries for the brokerage side, NetBenefits, and a Mac specific entry. Pick the wrong one and the connection succeeds, authenticates, and then quietly downloads nothing forever.
Even a healthy Fidelity connection only reaches back about 90 days. If the feed broke in the spring and you noticed at quarter close, the missing months are already outside what any reconnection will backfill.
Fidelity core positions such as SPAXX and FCASH, and some proprietary funds, come through without a symbol Quicken recognizes, so it stops and asks you to match a security before it will accept the batch.
Quicken community reports describe Fidelity reducing the transaction detail served through its connection, with the Mac entry offering a choice between detailed and simple tracking. A register that used to show individual activity may now show summaries.
Fidelity keeps monthly and quarterly statements available long after its 90 day download window has closed. Turn any of them into a QFX file and Quicken imports it exactly the way it imports a bank download.
The export is a Web Connect QFX written to spec, with the balance and transaction blocks Quicken expects, so the import runs instead of erroring out. Quicken does not accept a plain OFX file, so QFX is the format to pick here.
Since Fidelity HSA transactions cannot come down the connection, an imported file is the practical alternative to typing a year of contributions, distributions and card spend by hand.
Statements go back years. Converting them is the only realistic way to load history that the download screen will no longer serve.
Debits import negative and credits positive, so the balance after the import ties to the printed Fidelity statement instead of drifting.
Fidelity Cash Management Account statements and the cash activity on a brokerage account convert cleanly, since both read as ordinary dated debits and credits.
Need the same activity in a spreadsheet or in MS Money instead? Export the identical extraction as CSV, Excel or OFX from the same upload.
No reconnection, no retyping, no waiting on a ticket.
Sign in at fidelity.com and save the PDF statements covering the period Quicken skipped, one file per statement period.
Tip: Statements live under Accounts and Trade, then Statements, separate from the activity download screen.
Upload the statements, check the extracted transaction table against the printed one, and export a QFX file built for Quicken.
Tip: Pick OFX instead if you are on MS Money or another finance program that reads plain OFX.
Use File, then File Import, then Web Connect File, choose the existing Fidelity account, and review the matches before accepting.
Tip: Quicken flags likely duplicates, so a little overlap at the edges is safe.
Anyone whose books depend on Quicken staying current with a Fidelity account.
A health savings account that has never downloaded a single transaction into Quicken, with a year of qualified medical spending that still has to be substantiated at tax time.
Employer retirement accounts where contributions post every payroll and the register has been frozen for months, or filled with unknown securities.
People using the Fidelity CMA as a checking replacement, where a broken feed means bill payments and card spend stop reaching the register.
Working in a client Quicken file where the Fidelity feed broke months ago and the gap now sits outside the 90 day window entirely.
Work from the top, and check the account type first, because the Fidelity HSA problem does not respond to any of the standard connection fixes. Back the file up before anything that deactivates an account.
| Fix | When it applies | What to do |
|---|---|---|
| Identify the account type first | Always, before anything else | HSA, NetBenefits 401(k), brokerage and Cash Management are four different connections. An HSA that downloads nothing is a known Fidelity data problem, not a fault in your file. |
| Confirm you picked the right Fidelity entry | Connection succeeds but no transactions ever arrive | Edit account details, then Online Services, and read the institution name. NetBenefits accounts must use the NetBenefits entry, not the brokerage one. |
| Check for a Fidelity side outage | Several Fidelity accounts stopped on the same day | If other institutions in the same file update normally, the problem is at Fidelity. Give it a business day before changing your setup. |
| Resolve unidentified securities | The import stops asking you to match a security | Match the incoming line to the existing security in your file rather than creating a new one, or Quicken will end up holding two positions in the same fund. |
| Deactivate hidden and closed Fidelity accounts | Errors persist after every active account is working | Tools, then Manage Hidden Accounts, and turn off online services for any closed Fidelity account still enabled for downloads. |
| Deactivate, restart Quicken, reactivate | Only after the steps above have failed, and never for an HSA | Back up first. Deactivate online setup in Edit account details, fully close and reopen Quicken, then reconnect and pick the correct Fidelity entry. |
| Convert the statement and import it | The gap is older than 90 days, or the account will never download | Turn the Fidelity PDF statements into a QFX file and import them through File, File Import, Web Connect File. This is the only route for HSA activity. |
Almost every broken bank feed in Quicken is a connection problem, which is why the standard advice is to deactivate the account, restart, and reconnect. That advice is actively wasted effort on a Fidelity HSA. According to Quicken support staff responding in the Quicken community under ticket 1999090, Fidelity sends HSA data in a different format from its brokerage and IRA accounts, and specifically does not include a transaction description. Quicken treats the description as a required field, so the transactions cannot be processed even though the connection itself works fine. Reconnecting hands Quicken the same unusable data a second time.
The guidance given alongside that explanation was to update the HSA balance manually until Fidelity changes how it sends the data, and no date for such a change has been offered. That is a reasonable answer if your HSA sees four transactions a year. It is not a reasonable answer if you are running medical spending through a Fidelity HSA debit card and need every qualified expense in the register at tax time. Converting the statements is the practical middle ground: you get real dated transactions in the account instead of a single adjusting balance entry, and the reconciliation actually means something.
This is the quiet cause behind a lot of Fidelity accounts that appear to work and never deliver. Fidelity appears in Quicken under separate entries covering the retail brokerage side, NetBenefits for employer sponsored retirement plans, and a Mac specific entry. They authenticate against different systems and serve different data. A NetBenefits 401(k) set up against the brokerage entry can sign in successfully, report a completed update, and add nothing, because the account it is being asked about does not live on that system.
Check it under Edit account details, then Online Services, and read the financial institution name recorded against the account rather than the nickname you gave it. If it is wrong, that is worth fixing before you try anything more drastic, since a deactivate and reactivate cycle done against the wrong entry just recreates the same dead end. The same class of mistake affects Capital One, which publishes multiple institution entries for its bank, 360 and card products, covered in the Capital One not downloading to Quicken guide.
Fidelity serves roughly 90 days of downloadable activity, which is in line with most large US institutions. That limit is the reason a repaired connection so often leaves a hole in the middle of the year. You notice in October that the feed died in June, you fix the connection in an afternoon, and the download still starts from about July because June is already outside the window. Nothing about repairing the connection reaches backwards.
Statements are the exception. Fidelity keeps monthly and quarterly PDFs available long past the activity window, and those documents contain the same transactions in printed form. Converting them to QFX turns archived documents back into importable data. The same 90 day pattern shows up at Wells Fargo, where the download window is short even though Direct Connect still works, described in the Wells Fargo not downloading to Quicken guide.
Worth being straight about this, because Fidelity accounts hold two very different kinds of activity. Cash movement converts cleanly: contributions, distributions, dividends paid as cash, debit card spend, transfers, fees and bill payments are all ordinary dated debits and credits, and they land in Quicken as normal transactions with the right sign. That covers the whole of a Cash Management Account, the whole of the cash side of an HSA, and the cash activity on a brokerage account.
Trade level detail is a different structure. A buy or sell carries a security, a quantity, a price per share and a commission, and an investment transaction in Quicken is built from those fields rather than from a single amount. If what you need is share lots reconstructed inside a brokerage account, read investment statement to OFX for how that data is shaped before you rely on a converted file for it. For the cash side, which is where most broken Fidelity registers actually hurt, conversion is a direct fix.
Pick QFX if the destination is Quicken. This trips people up constantly because OFX and QFX look interchangeable and are not: QFX is Intuit's licensed variant of OFX carrying extra identifiers, and Quicken's own import documentation lists QFX, QIF, CSV and QXF as what it accepts, with plain OFX absent from the list. Renaming an OFX to .qfx does not work either, because the identifiers Quicken validates are inside the file. The QFX file format reference walks through what those identifiers are and why the two formats are not swappable.
Pick OFX if you are importing into MS Money, GnuCash, Banktivity or another program that reads the open format. Pick CSV only if you are heading into a spreadsheet, since a CSV import into Quicken carries no transaction identifier and therefore no duplicate matching, so reimporting the same period silently doubles it.
It depends on the account type. Fidelity HSA accounts do not download transactions at all, because Fidelity sends HSA data without the transaction description Quicken requires. NetBenefits 401(k) accounts are a separate institution entry with their own history of downloading nothing or downloading unidentifiable securities. Brokerage and Cash Management accounts usually fail for ordinary connection reasons, or hit the 90 day limit.
Quicken support staff have explained that Fidelity sends HSA account data in a different format from its brokerage and IRA accounts, and does not include a transaction description, which Quicken treats as a required field. The transactions therefore cannot be processed. This was tracked under ticket 1999090, and Fidelity has not published a date for changing it.
No. Deactivating and reactivating is the standard fix for a broken connection, but the HSA problem is not a connection problem. The connection works and the data Fidelity sends is missing a field Quicken requires, so reconnecting delivers the same unusable data again. Manual entry or importing a converted statement file are the working options.
NetBenefits is a separate institution entry from Fidelity Investments, and the most common setup mistake is connecting a 401(k) against the brokerage entry, which signs in successfully and returns nothing. Beyond that, users have reported NetBenefits completing an update with no transactions added, and Fidelity proprietary funds arriving as an unknown security with no ticker or CUSIP.
About 90 days through the connection. Anything older has to come from a downloaded file or a statement. Fidelity keeps monthly and quarterly PDF statements available for far longer than the activity window, so converting those statements to QFX is the practical way to load history that the download screen will no longer serve.
Yes for brokerage, IRA and Cash Management accounts, which connect and download normally most of the time. It works poorly for NetBenefits 401(k) accounts and not at all for HSA transaction downloads. Fidelity also offers a file download from its website, which is the route to use when the live connection is not serving what you need.
QFX. Quicken's import documentation lists QFX, QIF, CSV and QXF as the formats it accepts, and plain OFX is not among them. Import through File, then File Import, then Web Connect File. Avoid CSV for statements, because a CSV import carries no transaction identifier, so Quicken cannot match duplicates and a reimport doubles the period.
Fidelity core cash positions such as SPAXX and FCASH, and some proprietary funds, arrive without a symbol or CUSIP that Quicken can match to a security in your file. Quicken pauses and asks you to identify it. Match it to the security already in your file rather than creating a new one, otherwise you end up holding the same fund twice.
Quicken community reports describe Fidelity reducing the level of transaction detail served through its connection, with the Mac institution entry offering a choice between detailed and simple tracking. If a register that used to show individual activity now shows summaries, check which tracking method the account is set to, and use converted statements when you need the detail the feed no longer carries.
Yes. Download the Fidelity HSA statements as PDFs, convert them to a QFX file, and import that through File, File Import, Web Connect File. You get real dated transactions in the account rather than a single balance adjustment, which means the account reconciles properly and qualified medical spending is itemized for tax time.
The full troubleshooting order for any broken Quicken feed.
Amex, the 90 day reauthorization, and why not to deactivate.
The reauthorization loop and three institution entries.
How brokerage and trade level data is structured.
Why Quicken takes QFX and not a plain OFX file.
Turn a PDF statement into the QFX file Quicken imports.
Get started converting bank statements to OFX.
USD
per month
per month
$288 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
per month
$888 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
