Alert: Fidelity PocketSense Users: Do not do GetData today.
96 views
Skip to first unread message
Cal Learner
Dec 12, 2025, 9:42:21 AM12/12/25
to Microsoft Money
Keep a copy of your current Fidelity*.ofx files that are in the XFR folder before proceeding.
Those previously successful OFX files can make creating the database that F2O uses much easier. The database can be prepared from scratch, but that easy starting point is better.
GetData deletes existing *.OFX files from the XFR folder before trying to fetch new ones. So if Fideliy server stops working for you, as it did for me today, you could lose the latest successful Fidelity OFX files. Using Setup.py to run test is safe. It will try to get new OFX files for an account without deleting the existing OFX files.
Those previously successful OFX files can make creating the database that F2O uses much easier. The database can be prepared from scratch, but that easy starting point is better.
GetData deletes existing *.OFX files from the XFR folder before trying to fetch new ones. So if Fideliy server stops working for you, as it did for me today, you could lose the latest successful Fidelity OFX files. Using Setup.py to run test is safe. It will try to get new OFX files for an account without deleting the existing OFX files.
I would like to hope this is a temporary glitch, but we knew it was a matter of time.
https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/
https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/
Cal Learner
Dec 12, 2025, 12:59:17 PM12/12/25
to Microsoft Money
For those not sure they want to use F2O, at least save the OFX files you have to potentially use later.
F2O comments:
I am looking at F2O and considering some simplified or target documentation. I see 3 kinds of F2O users....
1. Those who have at least one set of old OFX files to gather info from. (that is where the existing notes are mostly aimed)
2. Those who will want to create a database CSV that will let Money recognize past investments.
3. Those who are content to let Money generate a pseudo-CUSIP, and for each investment, identify that this investment already exists under a different name.
Which group would you be, and do you see group 2 or group 3 as who I should concentrate on next?
If continuing to use PocketSense for other FIs, having a batch file put the resulting OFX files into the PocketSense Imports folder would be good after the initial setup, experimenting, and testing is done.
It has been months since I last worked on F2O, in anticipation of the Fidelity OFX/QFX server being disabled. So I have to re-learn too.
Note that F2O is written for Python 2.7 like PocketSense. I expect to get that to work with Python 3. Different version of F2O or be able to use either interchangeably.
I expect to put a new download file up today or tomorrow. If you experiment before then, please add this two-line file to F2O folder:
=============begin F2O_cfg.py===================
IGNORE_BEFORE_YYYYMMDD="20251210"DEBUG=0
================end F2O_cfg.py===========================
My last successfully downloaded transactions were from Dec 9. This will avoid duplicates. F2O generates unique FITID entries, but they will not be the same as what would have been generated. If your latest are earlier, adjust that string.
Ellen S
Jan 17, 2026, 6:46:34 PM (7 hours ago) Jan 17
to Microsoft Money
Cal et al,
I was successfully using Pocketsense to retrieve Fidelity data until a few weeks ago, with my last effort today (I download weekly). I wondered if Pocketsense access to Fidelity is now kaput? Your post sounds like you're still accessing, so maybe the problem is at my end.
GetData says "invalid OFX statement detected" and points me to "line 397, in getOFX raise Exception(msg)" and to the Fidelity OFX for possible clues.
Opening the Fidelity XFR file via Notepad++ shows:
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://ofx.fidelity.com/ftgw/OFX/clients/download" on this server.<P>
Reference #18.99463917.1768691407.7c887ed
<P>https://errors.edgesuite.net/18.99463917.1768691407.7c887ed</P>
</BODY>
</HTML>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://ofx.fidelity.com/ftgw/OFX/clients/download" on this server.<P>
Reference #18.99463917.1768691407.7c887ed
<P>https://errors.edgesuite.net/18.99463917.1768691407.7c887ed</P>
</BODY>
</HTML>
This is pretty much gobbledygook to me, and unfortunately, I missed your message about saving a good OFX to prevent overwriting so I can't compare files.
FWIW, I now use Pocketsense to update prices and iCreateOFX to convert my other account data (Phillip Katete, its creator based in England, is wonderfully helpful and I highly recommend his app.). The only downsides vs Pocketsense is that you have to download and convert the data files one by one, and it doesn't retrieve prices. If I find some spare time, I will try F2O again to compare, it's been awhile.
Ellen
-Kevin N
Jan 17, 2026, 7:00:11 PM (7 hours ago) Jan 17
to Microsoft Money
Hi Ellen,
Did you add userAgent to your sites.dat file for Fidelity?
If not, go https://whatmyuseragent.com/ and add the userAgent to your Fidelity <site> settings.
-Kevin N.
Reply all
Reply to author
Forward
0 new messages