Fidelity investment dividend transactions (most of them) still don't get assigned custom categories

Below are two recent consecutive transactions, each one being a dividend payout through Fidelity. From two different securities but with descriptions uniformally formatted as "DIVIDEND RECEIVED SECURITY XYZ (Symbol)(Cash)"

For reasons unknown one was assigned type "Income Dividend", and the other "Payment/Deposit" (with the check number blank).

The one which is "Payment/Deposit" also got mapped to a custom defined category "_FIN IN (Dividends) _", which I am able to see being represented on the Income report and chart.

The one which is "Income Dividend" ignored custom category rules, has not been mapped to a category and thus is not visible on the Income report. As far as I am concernd it only exists in the Transaction Activity log page.

Until recently I used to use custom categories to aggregate different sources of income on the Income report (which is based on categories), but after something was changed in how the investments transactions are processed by Simplifi most of the dividend transactions are no longer included in that report.

My main concern is that the dividend transactions with the Action type "Dividend Received" are not included in the Reports, namely the Income report, which is based on categories. It used to work fine, all credit transactions with the description containing "dividend" were being assigned to a custom category and were being displayed as stacked column format on the Income report along the job income and other income streams.

Hello Jon,

Ok that's a fair enough explanation. So is there a way at this point to run reports on dividend income? Because yes, all of the dividend received transactions get Action type "Dividend Income" assigned and are permanently exluded from Income reports, and there is no way to override this behavior in settings.

I guess I understand what is happening, but don't understand why. Are there plans to change this behavior of the app? By setting up a custom rule to automatically change Action type "Dividend Income" to "Payment/Deposit" for example?

Thank you, will definitely keep an eye on the progress of this feature. Looks like it was requested two years ago already! Strangely the reporting worked for me just a few months ago, maybe because Fidelity was returning the dividend transactions as different type? But since "the issue got corrected" the transactions disappeared from the Income report.

Without this how am I supposed to see, visually, at a glance, what my combined dividend income from different accounts is?

Hi Jon,

My take away from this is that Simplifi Investments doesn't want to smoothly integrate with the rest of Simplifi. The transactions received through brokerage account are treated separately from transactions from other accounts. To that, Investments doesn't have its own reporting and charting feature, so while it's possible get a total for a selected time range like you suggested, comparing totals or establishing a trend line would require me now do what, use a spreadsheet?

Which is regretful because the fix appears to be rather simple to implement technically. How? Once a dividend transaction gets its type changed, manually, from Income Dividend to Payment/Deposit it gets included in the Income report, alongside other types of income. Inconceivably, Investments activity log doesn't allow to bulk change multiple selected transactions. So each has to be selected one at a time, then Action has to be changed from the drop down list, then the entire list has to refresh.

I feel like Simplifi could be handling this busy manual work automatically, or automatically assign actions Payment/Deposit to dividend transactions as I, as the end user of the app, want it, according to custom rules, or at least allow editing multiple selected transactions with a single click instead of having to spend half hour clicking updating transactions one a time.

Is there a recent feature request already for the above so I could keep an eye on progress of resolution? The one referenced earlier is nearly two years old and apparently hasn't been updated? Although something must have changed, because what was working, for me at least, suddenly stopped working, and I'm strongly convinced that the current behavior is not correct, and is either a missing feature or a bug.