BYDDF – “Stock Splits May Be Missing”. Anyone Still Seeing This?

Thanks Quicken Kristina. I reviewed the suggested fix, but that situation is different from what’s happening here. In that example, the solution was to accept a split and adjust the dates to make everything line up. That won’t solve this problem.

In this case, BYD Co. Ltd. has two different share classes that trade separately. Each share class had its own split, on different dates and with different ratios. During a one-time bad data feed, those two separate splits were treated as if they belonged to the same security, and both were downloaded into BYDDF. The 6-for-1 split does not belong to BYDDF, but it's still sitting in BYDDF’s historical data.

Every time One Step Update runs, Quicken checks that history. It finds the 6-for-1 split and flags it as “missing.” In plain English, it’s thinking: “I see a 6-for-1 split listed for BYDDF and the user hasn’t accepted it.” But BYDDF never had a 6-for-1 split. The alert is being triggered by incorrect historical data, not by a missing transaction.

The problem is in the stored data history itself. The incorrect 6-for-1 split needs to be removed from BYDDF’s historical record by the data team or a programmer. It isn’t something that can be resolved through Community troubleshooting steps, which is why I called support and a ticket was opened.

I understand there may not be anything further that can be done at the Community level. Since my ticket has been open for eight months, I would greatly appreciate any assistance in getting it in front of the appropriate team for review. Until the incorrect 6-for-1 split is removed from BYDDF’s historical data, the “Stock Splits May Be Missing” alert will continue forever.