@MatAtFreetrade to me it is obvious that @cheok was having some fun and made his comment in jest, underlying that his serious point is the resolution is to the benefit to both parties and their customers.
He knows what’s what and anyway the relevant discussions and resolutions are underway between the two parties.
Hi, just checking in on the Lloyds issue. Would be good to see Standing Order payments made from a Lloyds account [into Freetrade’s Lloyds account] appearing in the Activity feed.
Perhaps given the dataset where the Activity feed is not being updated can be quantified some kind of additional manual action can be updated to create an Activity feed update until an automated process can occur?
Still not sure I understand the issue though. If the trigger to generate an Activity feed was the insertion of a row into a transaction table, and the recipient is known (so the money is allocated to the correct account) then an Activity log record would be created with every insertion. Can only assume some other trigger is being used.
Hey @MatAtFreetrade, we are unfortunately still waiting on Lloyds to prioritise fixing the standing orders issue. It sounds like we aren’t the only ones impacted by this so we are hoping they will pick this up soon.
The result of this issue means we are having to manually allocate standing order payments that come in from Lloyds. You’re right in that it’s a different trigger making transactions show up in the Activity feed. This is why those deposits aren’t showing in your feed.
The two things we are looking at to help this are:
Following up with Lloyds to try and get this fix prioritised on their end
Reviewing other recurring deposits options we can provide to customers - these won’t be as easy to enable as standing orders but we’re hoping they’ll be more dependable!
Thanks for the suggestion. It’s something we’ve looked at in the past and is doable but we haven’t got around to making this improvement yet. The team are busy working on a new feature for Activity feed exports at the moment (look out for that one!) but it is something we can consider once we get a better understanding from Lloyds on their timelines for the fix on their end as that really is the root cause. Appreciate you raising the suggestion as it’s always a good indicator for us when we’re prioritising features and fixes what our customers like yourselves care about.
This is a standing item we have with them which we’ve been following up on but unfortunately we still don’t have a firm timeline from them on the fix. On top of being a pain for our customers who bank with Lloyds, it’s also causing us operational issues so it’s definitely something we are continuing to push for.