F2O note, and upcoming F2O minor tweaks

[Cal Learner]

Beta19 came out  2026/6/18. The major change to F2O_beta19.zip was to rather than enter a dividend for the core position, the interest is entered as bank interest.  This is overridable. There are some  overrides that can let you identify your core to be something other than the FDIC-insured, SPAXX, or FDRXX. If you have a core balance, identifying the core is automatic. The only time overrides could matter is if your core is down to zero, but you get an end-of-month distribution. This was tried out in alpha versions and has now been mainstreamed. I really try to make the defaults the way to go rather than having people use overrides.

There were some other minor tweaks.

If there are any questions or comments, please post.

On my current personal version, I have made two changes since the F2O_beta19.zip. I am not issuing a new zip file for those at this time. The changes will be very unlikely to affect others.  I thought I would post about those two change. My personal version usually becomes the next mainstream.

One change is for a very rare condition that I ran into. With the right set of circumstances, you could get a  "DIVIDEND CHARGED" in CSV history . This is very unusual Due Bill .. It is a negative dividend due to sell ex-div of lent security. You will later receive dividend to undo the negative. Most people will never see that condition, but if it happens F2O will issue a negative dividend. Money is OK with that.

I noted that surprise because I had set DEBUG=1 which generated  F2O_logged_a_note.csv. I have decided  to set the new default to DEBUG=1. This generated file can be ignored, and it will only be generated if there is some kind of transaction in the History that F2O ignored for producing OFX files.  The DEBUG level is still overridable in F2O_DB.csv

I expect to incorporate these the next time there is a new version uploaded for some reason.

I note that the Fidelity Accounts_History*.csv filename changed format. Fortunately this did not affect those used the defaults, even for the oldest versions of F2O.

[Cal Learner]

F2O_beta20.zip uploaded to https://drive.google.com/drive/folders/1-4fBbRxaPhNYZK0gNHuZ3n-Bdoncy2aR

If you use F2O and new transactions are not coming in, a change in the Fidelity Accounts_History*.csv files for some users has been discovered. Such changes may be phased in to the rest of us at some point.

Date format in the CSV has been mm/dd/yyyy format, but for some has changed to mm-dd-yyyy format. This caused the transactions to be ignored during processing. A change to be tolerant of either is being tested.  Beta20 accepts either date format.

If/when that change happens to your CSV, since the CSV lines changed, and the FITID is a hash based on the CSV line, there will be a different FITID for existing transactions. Therefore in your F2O_cfg.py, add/change IGNORE_BEFORE_YYYYMMDD="20260618", but use whatever date comes after your latest existing successful downloads. Alternatively, accept the duplicates and void one of each duplication, or just click No, and that gives a voided transaction.

See the bottom of recent_note.txt for recent changes.

[Cal Learner]

The Fidelity Accounts_History*.csv format change arrived for me today.  Initial symptom was that F2O wanted me to add a new security, and there was none. If you run into this, do not add a new symbol, and check back. To abort, Cntl-C and/or Cntl-Break should get you out.

I am tracing this down, and will update with more info later today.

[Cal Learner]

The change impacts everybody. See the new thread.

On Thursday, July 2, 2026 at 10:02:13 AM UTC-5 Cal Learner wrote:

Problem will not affect most people, is the good news, but it could affect some. At least I don't have the urgency that I did.

The problem is that the CSV used to have double quotes around the Action column. The Action includes the Description  (name of security)

ONE of my securities has a comma in that name/Description and also within the Action. That was not a problem when there were double-quotes around the Action entries. However those double-quotes are gone, but they still there for Description.

I will give that some thought although I would expect Fidelity will restore the quotes at some time. After all, CSV stands for Comma-Separated-Values. I may make the workaround more specific to this presumably temporary situation. If this affects anybody else, please post. I may do something that can be added to the F2O_cfg.py, and avoid people having  to even read about this unless they get a specific problem. A more general automatic thing I am thinking about is that if the symbol has a space (will not occur in a real symbol) to adjust the record accordingly.