Jan 24, 2020 | Read in 2 minutes
We have found an anomaly when instructing a sell of an asset to then withdraw the proceeds, this generated 2 withdraw messages. The two messages were posted to the clients message hub however, this has now been updated to ensure that only 1 message is sent as expected. For more information on the sell and withdraw function click here.
When setting up a regular withdraw on a client account a pending withdraw payment is created for this withdraw. This is to ensure that there is enough available cash at this time to make the withdraw payment on the correct date. It had been discovered that when the pending payment is created, a withdraw message was also being created. Where these payments are made on a monthly basis the withdraw message would not be sent. For more information on regular payments please click here.
When creating a user on the system we require the first name, surname and email address to create this record. The email address has to be unique across both user and client records on a firm.
We have now created a dashboard page in the professional Ui where firms are able to see firm level data. The information on this page include the following:
We have introduced an exceptions banner where users will be able to see the exceptions that have been created. Initially, the suspicious activity exception you will be able to access the underlying data and clear these transactions, depending on the user scope. You will also have the ability to filter this by node, where applicable, to see the underlying transactions at different levels.
Under the exceptions bar we now show firm data of:
These figures will update where you are able to select different nodes from the dropdown.
Within our next sprint we will focus on the ability to create an illustration. The development we have planned across the next 2 sprints are:
If you have any questions or would like further detail on any of the above development please get in touch. Thanks
The Product Team
As one of our product managers, Ronak works to discover, design and deliver functionality, alongside our engineering team. He’s not actually a honey badger, although he’s just as fearless, and nearly as clever.
Apr 14, 2021 | Read in 4 minutes
Apr 8, 2021 | Read in 7 minutes
Dec 2, 2020 | Read in 4 minutes
Oct 7, 2020 | Read in 3 minutes