The Fidelity Jig Might Finally Be Up. :(

[-Kevin N]

As of 1/21/2026, I'm getting an 'Error occurred logging in' message in the Fidelity Investment's OFX file using Pocketsense.

-Kevin N.

[Cal Learner]

I just tried also, and got a fail.

It had worked this morning.

Let's hope it is a temporary thing, but people should save a copy of their ofx files before trying getdata.py. Pocketsense deletes the OFX files from the xfr folder when you do a get data. Using setup.py to test does not delete OFX files.

I will pay attention to F2O tomorrow.  https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/

[-Kevin N]

Hi Cal,

Yep, it was working for me too this morning but not this evening.

-Kevin N.

[Cal Learner]

Kevin: If somebody works with F20, and did not successfully download transactions from Jan 20, you will want your F2O_cfg.py to contain 

IGNORE_BEFORE_YYYYMMDD="20260120" If it had been a while, the date would be set accordingly. The point of this is to not duplicate transactions. F2O produces its own FITID that will not match the ones that Fidelity generated.

Since we got the Jan 20 transactions already, we will want our F2O_cfg.py to contain 

IGNORE_BEFORE_YYYYMMDD="20260121"

If you have saved successful downloaded OFX files since you ran F2O_DBgather.py , you will be able to use F2O_DBgather.bat or F2O_DBgather.py to update  F2O_DB.csv 

Those who have not generated  F2O_DB.csv  from existing transactions and did not save prior OFX files, and want to use F20,  will have to prepare the database more manually.  It is going to be tough probably.

[Ken H]

@Cal I'm trying to get F2O up and running and downloaded beta11A.  I've got the most recent Fidelity OFX files.  However, when I extract the downloaded zip there's no F2O_DBgather.py file.  Where might it be hiding? 

I'm sure I'll have more basic questions in the future, but I'd like to get the DB set up, at least :)

Ken

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Run  make_new_F2O_DBgather.bat.bat  (just this one time), which will create a new  F2O_DBgather bat for you

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Sorry, you are missing the py, not the bat.

[Cal Learner]

These are the files in beta10A.zip.

02/01/2024  07:52 AM                48 F2O_cfg.py.DEBUG4
03/03/2024  12:33 PM                30 f2.bat
03/10/2024  09:06 PM             1,432 F2O_risky_info.txt
03/12/2024  05:06 PM             1,240 make_new_F2O_DBgather.bat.bat
03/16/2024  04:42 PM             6,211 F2O_MorningAfterFidelity.docx
03/16/2024  04:43 PM             9,109 F2Obeta.docx
03/17/2024  09:50 AM               442 f2o.bat
03/24/2024  12:05 PM                46 F2O_cfg.py.sample1
03/26/2024  08:35 AM            12,357 F2O_DBgather.py
03/30/2024  03:03 PM             1,287 F2O_DB.csv.seed
02/01/2025  09:22 AM            58,437 F2O.py

=====================

I think  F2O_MorningAfterFidelity.docx would be the place to start among those files. https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/ may be the better place to start.

Any suggested changes for a new zip file? Let me know. As you proceed, it would be nice if you took notes about what is confusing or non-working. Then let us know. I will be looking, and I expect Ameridan will be looking.

I envision some new threads here... one starting from people who don't have any prior existing  FIDELITY202*.ofx files that are over 600 bytes long.  My tries that fail gives me FIDELITY20260121*.ofx files that are 558 bytes long 

I will say to not modify F2O_DB.csv with Excel or other spreadsheet program. Those can add quote (either ' or ") characters that can mess things up. I expect to address things to allow producing a F2O_DB.csv file with a spreadsheet program, and then remove the quotes with some new python file. But for now, if producing the file or modifying the file, please let the F2O*. py do the modifications or use a text editor such as Notepad or Notepad++.  You can use a spreadsheet program to look at a copy of  your F2O_DB.csv file, but please be careful to not modify the F2O_DB.csv file itself with a spreadsheet program.

[Cal Learner]

Note that the  F2O_DB.csv.seed is intended to be the start of a new  F2O_DB.csv file. It has some entries already that may be of actual use to some, but it also serves as an example of various lines. It also has a first row which can serve to make the CSV more readable, and F2O knows to ignore that.

[Dan Adkins]

Well, F2O worked for me back when I wrote my article, but it seems to be incomplete now?  I was successful at running fidelityset while good ofx files were in my xfr folder on 1/21, DB_gather created a nice F2O_db.csv, and F2O.py creates 2 ofx files for me into my \import folder, but they are somewhat empty (example attached; ofx file renamed txt).  Is this a clue? - <!--ofx1_init--><!--ofx1_init-->

--
You received this message because you are subscribed to a topic in the Google Groups "Microsoft Money" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microsoft-money/_hb28u6bnEY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/bf106b4a-c100-4f6b-9bf3-3877d9b7d1cfn%40googlegroups.com.

[Cal Learner]

I am glad you posted...

Could it be that there were no transactions for the day? I suspect you have IGNORE_BEFORE_YYYYMMDD="20260121" in  F2O_cfg.py 

I do have stuff between those comments.

I have some stuff going on Friday, but I should be able to get some time this weekend.

[Ken H]

OK.  So if I run F2O_DBGather.bat with nothing in my xfr folder it executes without error.  However, when I put my most recent Fidelity OFX files (of which there are 12) in xfr I get the following:

E:\OneDrive\Documents\F2O_beta10A>cd "E:\OneDrive\Documents\F2O_beta10A"

E:\OneDrive\Documents\F2O_beta10A>py -2.7 F2O_DBgather.py "E:\OneDrive\OFX PocketSense\xfr"
Traceback (most recent call last):
  File "F2O_DBgather.py", line 225, in <module>
    DBGather_logit("OPTINFO, but  no pat_OPT match found\n"+str(ofx_pieces[pair_i]))
  File "F2O_DBgather.py", line 43, in DBGather_logit
    BGather_log_ctr+=1
UnboundLocalError: local variable 'BGather_log_ctr' referenced before assignment

I'm not experienced enough to even know where to begin to look for what's causing the error

[Ken H]

I'd be happy to make notes and suggestions.  As one who is marginally competent I can represent those who are new to F2O and not necessarily knowledgeable about Python.

My first suggestion would be to mention that F2O_beta11A doesn't include all the necessary files.  I mistakenly assumed it would and spent some time figuring out why it wouldn't work.  Anyone new to F2O should be directed to the most recent complete entry on Google Drive (10A currently).  Also, I've had problems in the past with Python programs automatically being associated with Python 3.  Because of this I modified F2O_DBgather.bat to be:

cd "E:\OneDrive\Documents\F2O_beta10A"

py -2.7 F2O_DBgather.py "E:\OneDrive\OFX PocketSense\xfr" %1
pause

I put the pause in so I could see what happened when it ran.  The paths are correct for my system.

[Ken H]

Well I identified my problem with F2O and I think I'm screwed.  I had a hunch that having options (equity and index) in my accounts might be the issue.  I ran  F2O_DBgather.bat with only my 4 accounts that don't have options and it ran without error and created a CSV file that included the one stock position in 2 of the accounts.  The only other positions are sweep MMFs that are scrubbed out.  After running this test I noticed there was a DBGather_log.txt file and guess what it showed? My previous try with all 11 accounts nerfed on the first option position as shown here:

OPTINFO, but  no pat_OPT match found

<OPTINFO><SECINFO><SECID><UNIQUEID>6926059XR<UNIQUEIDTYPE>CUSIP</SECID><SECNAME>CALL (SPY) SPDR S&amp;P500 ETF DEC 18 26 $540 (100 SHS)<TICKER>SPY261218C540<UNITPRICE>162.7300000<DTASOF>20260121033004.000[-5:EST]<CURRENCY><CURRATE>1.000<CURSYM>USD  </CURRENCY></SECINFO><OPTTYPE>CALL<STRIKEPRICE>00000000540.00<DTEXPIRE>20261218120000<SHPERCTRCT>100 <SECID><UNIQUEID>6926059XR<UNIQUEIDTYPE>CUSIP</SECID>

My question is how difficult would it be to implement handling options in F2O?  If it's not possible then I may have to consider moving all my accounts to E*Trade as they still work directly with PocketSense.  Don't know how long that'll last, but I don't think I have any other option because I'm a fairly active trader and I do a lot of options.

As always, any thoughts are appreciated.

Ken

[Cal Learner]

Ken: I expect I could grow F2O to include options better, and in fact I thought it did that. I even bought and sold 3 option to generate OFX files.  So I did very few options.  Not sure about the timeframe to work on it. The most sensitive part may be the account number, although other stuff can be sensitive too. 

I worked from examples of what Fidelity produced in OFX files vs what the CSV files contained.  

If you have a collection of working Fidelity OFX files hold on to those. 

I was not aware that E-Trade still worked properly. That would be good reason to move stuff.

[Tom Meyer]

Is it your expectation that these Money Investment Activities to work with F2O?  I can only test Dividends at this point, but they work well.

Buy
Sell
Dividend
Other Income
Reinvest Dividend
Add Shares
Remove Shares
S-Term Cap Gains Dist
Mid-Term Cap Gains Dist
L-Term Cap Gains Dist
Reinvest L-Term CG Dist
Transfer In
Transfer Out

Thx,

Tom (Texas)

[Dan Adkins]

Never mind Cal - all is good.  in my cfg file, OVERRIDE_HISTORY_FILES was set to the set folder.  I commented it out, so now F2O looks in Downloads.

You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/cbefc159-0ff7-4c7e-b1b3-ac31a0391f8dn%40googlegroups.com.

[Ken H]

Cal, thanks for your response.  I just added a fifth OFX file to xfr.  Unlike the first 4 which only had MMFs and 1 stock, this account has 1 option position.  As expected, it was unable to process the 1 option position.  I would be happy to provide you with the last OFX file from 1/21/26 for this account and the CSV from Fidelity with 90 days of data (which is minimal), if they would be of use.  I understand it's a BIG ask to add options capability to F2O and realize it's not a priority.  It's just a daunting task to move everything to E*Trade.  I've been very happy with Fidelity over the last 20 years and who knows when E*Trade will pull the plug on their OFX server.

FWIW here's the DBGather_log.txt from the most recent attempt:

OPTINFO, but  no pat_OPT match found

<OPTINFO><SECINFO><SECID><UNIQUEID>7418449HF<UNIQUEIDTYPE>CUSIP</SECID><SECNAME>CALL (BX) BLACKSTONE INC JAN 15 27 $170 (100 SHS)<TICKER>BX270115C170<UNITPRICE>14.0000000<DTASOF>20260121033004.000[-5:EST]<CURRENCY><CURRATE>1.000<CURSYM>USD  </CURRENCY></SECINFO><OPTTYPE>CALL<STRIKEPRICE>00000000170.00<DTEXPIRE>20270115120000<SHPERCTRCT>100 <SECID><UNIQUEID>7418449HF<UNIQUEIDTYPE>CUSIP</SECID>

[Cal Learner]

Ameridan: If  IGNORE_BEFORE_YYYYMMDD is set such that there were no transactions from the date forward, a section will be empty save comments. 

But I still am tracking a bug. The positions info does not seem to be being processed. I find that important, and will figure it out.

Ken: I had options added I thought. I will address  improving/fixing options after I get positions working. I tend to succeed in bursts when I get inspired. Takes me a bit to get re-engaged.

What I would ideally want to have is the line in  Accounts_History*.csv that represent a transaction, and if available what the OFX that fidelity generated for that same transaction.  But I do expect to have options work.

Tom: Not sure about transfer out, but it does the others.

[Cal Learner]

Ken: The purpose of  F2O_DBgather.py is to create or update   F2O_DB.csv from existing good Fidelity OFX files from when those are working. You can also work on the   F2O_DB.csv itself. Keep backups!  One thing is that spreadsheet programs such as Excel can do is to add quote characters when editing a CSV. F2O is not as tolerant of quote characters as I wish it was. But you can edit   F2O_DB.csv to add more lines with a text editor, such as Notepad or Notepad++.

 F2O_DB.csv.seed may be of interest. It is intended to be both a starting point and an example. The first line is a header line that describes each column. F2O does not require that. The third line is an example of a line for an option. You may be able to create your own lines if  F2O_DBgather.py did not do a good-enough job.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

When I was testing F2O for you back in 2024, I used the SET folder for history, positions, and ofx files.  Now, I'm properly using the DOWNLOADS folder and IMPORT folder for those files.  So, yes, because of the IGNORE_BEFORE, I was processing the most recent files from 2024/2025 = no results ;)

My positions were all imported as Zero quantity, but thankfully Money allowed me to select "Ignore, I will process manually".

[Cal Learner]

I am posting f2o_beta10B.zip very shortly.

It helps my positions generation, although there are still a few that are showing a positions quantity mismatch.  So continue to  select "Ignore, I will process manually". 

The biggest change is to tolerate commas in the CSVs quoted  strings. Those were causing problems for me.

I expect to start a new thread noting the new version. 

[Tom Meyer]

Cal,

Here’s a couple of transactions that are not being imported from the CVS.  Historically in my MSMoney file they were just recorded in “Cash Transactions” as:

Taxes>Foreign Taxes

Fees

They were not tied to an investment asset.  There are approximately 500 assest in that account.

 >>>>>>>>>>>>>>>>>>>>>>>%<<<<<<<<<<<<<<<<<<<<<<<<<

Jan-23-2026

FOREIGN TAX PAID TOTALENERGIES SE EUR2.5 (TTE) (Cash)

-$1.03

Jan-21-2026

FEE CHARGED ADR FEE P/D 02/18/25 as of Feb-18-2025 NOKIA OYJ ADR EACH REPR 1 ORD NPV (NOK) (Cash)

-$0.02

Jan-21-2026

ADJ FOREIGN TAX PAID TAX RCLM PD:02/18/25 as of Feb-18-2025 NOKIA OYJ ADR EACH REPR 1 ORD NPV (NOK) (Cash)

+$0.06

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>%<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Tom (Texas)

Sunset Home & Business

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Cal, should we be using AutoGen=1 now?  If so, you might add it to your new beta.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

I edited this morning by adding the red portion.  Did I do correctly, or not?

2. F2O_DBgather.py

This script builds a cumulative database of your Fidelity portfolio holdings (primarily for CUSIP matching) using your current Pocketsense OFX files in your XFR folder (or your history file, if those OFX files are no longer available, by using  AutoGen=1  in the config file).

[Cal Learner]

Ameridan: I have not played with that for a while, but it may be time. I will think about how to do that. In the mean time I have posted f2o_beta11B.zip

Tom: Thanks. I should be able to address that duplicating the way Fidelity handled it.  I was thinking that was already working, but I have transactions to test it on.

[Cal Learner]

Ameridan: I had intended the autogen to only be used once -- to catch up. Then the generated F2O_DB.csv would be manually inspected and tweaked in case that the autogen did not pick the right kind of thing. Reminder that tweaking should not be done with a spreadsheet program. Maybe I will be able to tolerate that in the future... seems like a natural, but for now, no.

AutoGen does not actually generate OFX files IIRC. It has been months since I worked with that.

But providing a sample F2O_cfg.py.autogen_sample makes sense.

The dialog that occurs when a new investment is found could use some better documentation, and maybe the dialog should be improved. I expect the Update choice to be more routine so that the F2O_DB.csv gets updated with the new entry.

[Cal Learner]

Ameridan:  I am thinking to include Autogen_fresh_F2O_DB_OnceOnly.bat ... name could use some improvement.

Working on that...

[Ameridan (microsoftmoneyoffline.wordpress.com)]

OK, I reversed my edit, and we'll update to reflect your "improvements".   Let me know if my article needs to be improved.

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Tried out f2o ver 11b.  Ran fine, but no different regarding positions.

[Cal Learner]

Revision will be needed to incorporate Autogen_fresh_F2O_DB_OnceOnly.bat if I get good review of that. I hope to put out beta11C.zip soon.

Besides the batch file, it will have a revision of F2O_DB.csv.seed to remove an extra blank line.

On Saturday, January 24, 2026 at 1:09:59 PM UTC-6 Ameridan (microsoftmoneyoffline.wordpress.com) wrote:

[Ameridan (microsoftmoneyoffline.wordpress.com)]

I updated my article today.  Redid the F2O.bat section, now that I see that Cal has a nice one in his zip.

https://microsoftmoneyoffline.wordpress.com/2024/02/03/cals-fidelity-specific-csv-to-ofx-converter/ 

[Gaurav Kumar]

Hi Cal,

I am about to start using the F2O utility. THankfully, I had updated my copy of pocketsense to copy older odx files into a backup folder, and I have had copies since 9/15.

I was looking at the csv files to be downloaded and I found that the "positions csv" file for me contains the positions for external accounts that I have linked for consolidated view.

I have not started the integration yet, but wanted to let you know (if you are not already aware). that it may need to be handled.

The account number for my external account is listed as "9274ae09-6a4a-4e4e-b13c-97fd0b8caddb". So, it maybe an easy fix to ignore any lines with similar patterns in account numbers.

Regards,
Gaurav

--

You received this message because you are subscribed to the Google Groups "Microsoft Money" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microsoft-mon...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/61b4cee3-5520-4790-9cf7-b9b2850ef97an%40googlegroups.com.

[Cal Learner]

Gaurav: never anticipated that.  So in your   Portfolio_Positions_Jan-22-2026.csv, for example, "Account number" column A (column 1) contains a really long string for that account?

F2O.py  line 1054 says

   if not re.match("^\w{5,9}$",split_ptext[P_AccountNumber]): #    Fidelity account numbers are 5 to 9 characters

    #debug_print("ignoring this ptext line "+str(split_ptext)) #qq
    continue #not a date, so do not process.

So that should prevent the line in Portfolio_Positions*.csv from being processed. Two ways-- too long and contains non-alphanumeric

Is the same "account number" in your  Accounts_History*.csv file?

[Gaurav Kumar]

This is how the 1st 2 columns are shown in the position csv. I have masked the account name.

Each line item represents 1 fund/script that I have in my external account. Thankfully, I had only listed 1 external account.

Account Number	Account Name
9274ae09-6a4a-4e4e-b13c-97fd0b8caddb	<External Account Name>
9274ae09-6a4a-4e4e-b13c-97fd0b8caddb	<External Account Name>
9274ae09-6a4a-4e4e-b13c-97fd0b8caddb	<External Account Name>
9274ae09-6a4a-4e4e-b13c-97fd0b8caddb	<External Account Name>
9274ae09-6a4a-4e4e-b13c-97fd0b8caddb	<External Account Name>

The external accounts are not listed in the Accounts_History*.csv. It shows all my accounts that are with Fidelity.

Regards,
Gaurav

To view this discussion visit https://groups.google.com/d/msgid/microsoft-money/0cb53c83-7ac5-45c9-920e-3994c83d4e87n%40googlegroups.com.

[Cal Learner]

So you should be good.... those will be ignored.

[Ken H]

Cal, I emailed you directly to "msm.cal...@gmail.com" <msm.cal...@gmail.com>.  I've put together the option OFX and CSV info, but they're directly from my account so I'd prefer not to post them here.  Can you DM me with a good email address for you and I'll send the info.

Ken

[Ken H]

Just emailed you the options info :)

[Ken H]

Cal, I think I know what the issue might be with my options.  All of my option positions are short (either covered calls, naked puts or naked calls).  Because of this, there is a minus sign everywhere they show up (-5 contracts, etc.).  Was F2O designed to handle short option (or possibly even short stock) positions?  When I removed all of the option info from the OFX file for my most active account I was able to create an F2O_DB.csv file without any glitches.  At least that's a start.  I can add the option symbols to F20_DB.csv, but am I going to run into more issues when I show positions that have a minus sign?

[Ameridan (microsoftmoneyoffline.wordpress.com)]

Cal, upon closer inspection today using f2o.py from beta11c.zip, positions are reported properly for me now in the created ofx files!

Hopefully, it all works for you too, now.

[Cal Learner]

Oddly I had to tell Money to not update a position. I searched, and it sure looks like the correct position info was being generated into the OFX. I will see if that continues.

This particular thing was listed as OTHER in the fidelity-provided OFX. I have it listed as STOCK in Money. But I will see what happens. Just a singular mystery event maybe..