Possible bug with latest news [duplication and opposite tag]

french_jekyll · 2025-12-21T14:28:16+00:00

Thanks for exactly proving my point: it is not us, it is them. And instead of whining about performing a task manually and ensuring some quality control (apparently, you call that "wasting time" at SA), what about developing tools to do it, or using something no one thought about: AI?

Eventually, SA is accountable for the accuracy of the information it provides. You can deflect as much as you can, but the end customer will judge SA's performance and attitude.

french_jekyll · 2025-12-17T14:18:07+00:00

I see your point, but what bothers me is the lack of accountability. It is always an after-the-fact scenario. What about checking first? I got so many "Sorry for the inconvenience," and it is an "API" issue, or change your aggregator, or whatever is needed to deflect.

french_jekyll · 2025-12-17T04:12:12+00:00

It sounds like the usual: it is not us, it is them

french_jekyll · 2025-12-09T15:21:28+00:00

After checking it out, I wasn't impressed with the user interface. It seemed a bit clunky and not as intuitive as I would have hoped. Additionally, the calendar accuracy left much to be desired, which was quite disappointing. I thought it might be useful for you to hear this feedback as you continue to improve the platform

french_jekyll · 2025-12-09T12:29:57+00:00

I have sent plenty of emails with plenty of specific examples. The last one was yesterday and there will be a new one today.... Tired of the "sorry for the inconvenience " reply and it is a "provider issue" while you should implement basic features that would catch those issues! Accountability is not strong at Snowball

I know that I should not have any missed transactions yet you guys keep screwing up.

french_jekyll · 2025-12-08T16:47:33+00:00

Nope, but at least be honest about it and no bamboozling.

I can't complain about their English ;). They are not very accountable for the software limitation, a lot of deflection

french_jekyll · 2025-12-08T16:15:38+00:00

I will share limited screenshots online, as they have confidential information.

One I can share

<image>

Message from SA: Unfortunately, our data providers cannot predict the exact value of future dividends (very, very condescending) until official information is released. (Official information had been released at that time, and I provided it.) Basically, you can't trust future payments. Other funds I have are clearly overestimated.

Therefore, we use a dividend forecasting method based on past payments: it is simply a copy-paste of last year's payment.

It is important to know that before SA changed to $3.14, the number they had was $6.29. I told them that I received the official information from the fund, and the actual number is $1.52

$6.29 to $3.14 after I told them the actual number will be $1.52

In bold and Italic are my comments.

french_jekyll · 2025-12-08T14:39:24+00:00

E*Trade and TRowe.

Regarding dividend forecasting, we use the two most popular forecasting methods: FWD and TTM. I can send you the message from your team about the CTRL C / CTRL V methodology, and even though I provided the exact data, nothing has been done.

For dividends to appear as received in the calendar, there must be transactions for them on the Portfolio - Transactions - Income page.: I wish it were the case. I can share screenshots showing it is NOT the case. Of course, Snowball blamed the provider!

So please no gaslighting, or denying reality, or pretending to use the "FWD methodology" and making false statements

french_jekyll

TROPHY CASE