In another discussion about a disconnect between what Quicken thought the investment holdings were for an account and what the actual holdings were, I was prompted to do some investigation that led to discovery of other issues not related to that discussion.
Issue 1: One step updates contain inconsistent data.
If I have 100 shares of IBM and sell 5 and then do a one step update the downloaded data may have the sold transaction but not the updated number of shares. Quicken will process the transaction and update its number of shares to 95 and then compare that to the number of shares the institution says the account has, which is still 100 shares. Quicken then pops up a a dialog asking me what I want to do about it and I respond by saying to create a placeholder entry and so it creates one for +5 shares making the number of shares in Quicken 100 again. In a later one step update, the FI's data has updated the number of shares to 95 and, again, Quicken notes the difference and pops a dialog and I respond by saying to create a placeholder entry and so it creates one for -5 shares making the number of shares 95. This also occurs for bought transactions.
This has all the symptoms of Quicken's generation of one step update data grabbing data from the FI's database while the FI is in the process of making updates. This is a very bad thing to do. The FI's database should be locked while it is being updated so that no other process can get data from it. In this case, Quicken may be the victim of bad practices of the FI.
This is happening exclusively in an IRA which was created from a 401K rollover in April of 2021. The FI manages it, buying and selling securities as they see fit. Because they are stock brokers, they seem to get a kick out of doing trades and there is a lot of activity in that account. :-). From June of 2021 when they started buying securities to July of 2023 there were 25 instances of the above somewhat simple scenario. There may be more such scenarios which are more complex due to a flurry of activity involving one security with more complex data mismatches. But I doubt if these types of scenarios account for all placeholder entries.
So what is the best way to clean things up?
What is the best way to avoid this kind of thing? One possibility is to do one step update only on Sunday mornings in the hope that there will be no FI database updates being performed.
Issue 2: There are lots and lots of +0 share placeholder entries.
What are these entries for? They are not the result of Quicken asking what to do with a mismatch in numbers of shares. Quicken put them there. There are no fractional shares involved.
What should I do with them?
This is almost exclusive to the IRA mentioned above in issue 1.
Issue 3: Why are there placeholder entries associated with stock splits?
On July 18, 2022 there is a StkSplit transaction for Alphabet. At the time I had 6 shares. The Share Bal column for the StkSplit transaction shows 120 shares, which is what it should be after the split. On 7/20/2022 there is an Added transaction for 144 shares bringing the balance to 234. On 7/23/2022 there is a placeholder transaction of -144 shares bring the balance back down to 120.
The same thing happened for every StkSplit for that FI except one and that was special. The first shares of that security were bought on the same day as the StkSplit. In that case the Share Bal column for the StkSplit transaction had 0. Also there was another FI that had a pair of 1 for 1 StkSplit transactions (what is that?). They didn't have any of this either.
This seems like a disconnect between what the FI thinks a StkSplit is and what Quicken thinks. Quicken thinks a StkSplit results in added shares while the FI thinks that doesn't happen and an Added transaction is needed to update the share balance. This results in the need for a placeholder transaction to get the number of shares correct.
What should I do with these placeholder transactions?
Couple of notes:
- The StkSplit and Added transactions were not on the same day. The Added transaction was a day or 2 after the StkSplit transaction with the exception of the "special" ones noted above which had no Added transactions.
- The descriptions of the StkSplit transactions were weird if the split was 10 or more for 1. For example the description for the 20 for 1 Alphabet StkSplit was 1 for 0.05. Not technically incorrect but who uses that kind of terminology.
Issue 4: Who is responsible for the correctness of downloaded transactions?
Somehow I'd think it would be some kind of shared responsibility. Anybody know who is responsible for what?
Thanks
Jim