2021.1 - Client level security prices

Security prices are usually received from a data feed and apply to all clients. But there are occasions when a different security price would be useful on a particular client. For instance, you might want to use prices from a broker that perhaps were converted at a different exchange rate, or included accrued income or included an inflation element on an index-linked security.

To facilitate this, client level security prices can now be entered. The option is in Investment Accounts > Other > Override security prices. Apart from allowing you to enter the new price and currency, it displays the latest price held at security level and any previous client level security price.

Notes

1. When a security price is looked up, the system first tries to find a client level security price. If it can’t find one within the Pricing Range in Days (which is specified in Database Parameters), then it looks for a normal security price. For instance, if

• the Pricing Range in Days is 30,
• there is a client level security price at 31/03/21,
• a security level price on 03/04/21, and
• you look up the price at 05/04/21

then the client level price is used. This is because both prices are within the Pricing Range in Days and the client level price is found first, even though the security level price is slightly more recent.

2. Client level security prices are used for valuations, e.g. on an investment schedule. But they are not used for CGT What If calculations, Transaction Reporter reports or the Ownership of Securities Report. The latter two are usually run for multiple clients and it would be odd to use different prices for different clients on the same report.