Forum Discussion
marc.fraser-jones
Iress Team
Iress TeamAMA: I'm Marc Fraser-Jones, Xplan Portfolio expert and product manager at Iress, Ask Me Anything!
Do you have a burning question about Separately Managed Accounts (SMAs) capabilities in Xplan?
Join me here on Tuesday 13th August from 2pm to 2:30pm.
With years of experience helping advisers, p...
How can I code a document to show what SMA's investments are in? I'm aware I can use row[‘sub_account’]. However this gives a code, not the name of the SMA. BT Panorama in particular gives the subaccount as accountnumber.01, accountnumber.02 etc. The number of the end is different for every client, so it's impossible to tell which SMA it is. The new Portfolio Position (Beta) screen is able to give names to all of the SMAs, so I'm hoping there's some code we can use.
We also have an issue with this re SMAs in Panorama. We have Xport reports that pull portfolio data including the SubAccount name and for other vendors/platforms this displays the correct SMA name however with Pano it's just numbers and gives no indication of the actual SMA that the asset is held in. In the new Beta screen i can see the SMA name in the Panorama portfolio but this beta field is not available to pull into our Xport reports. As is visible in the Beta screen Panorama is actually feeding the correct SMA name into Iressnet however there appears to be an inconsistency in mapping because it's not being mapped to the same 'Sub Account' field that other platforms/vendors are feeding the SMA name to. Could this inconsistency be corrected so that the SMA name from Panorama is mapped to the same consistent field as it is with Macquarie and other vendors? or failing that can the new beta field that houses the SMA name be made available to pull into Xport reports?
- marc.fraser-jones
The detail in SubAccount is dependant on what the vendor/platform provides us, with the work we've been doing for SMA we've added the new SMA fields to the front end. Our intention is to expose the SMA fields into report datasources so they can be pulled into Xport, which should resolve this situation. This work is currently in progress, as it becomes available we'll provide further information in release notes.
Related Discussions
Recent Discussions
