You can use Performance NAV processing when you need the system to calculate an additional NAV on a monthly basis at an alternative pricing point to the normal NAV. For example, you can calculate the Performance NAV on the last business day of the month at a close of business (COB) valuation point. You can use this Performance NAV internally rather than release it to the market and use it to replace your existing daily process.
| Info |
|---|
Performance NAV processing is available as part of the Eagle mutual fund accounting solution. It is not part of the Eagle performance measurement solution. |
WRITERS NOTE: is it specific to MF accounting and/or Insurance accounting? Review note. I think we are documenting as a MF feature but I see the Service is listed under Insurance Accounting services...
WRITERS NOTE: in the first sentence, we say you use it to calculate a NAV on a monthly basis. I think I read somewhere that you can use it on a non monthly basis too. Should we say that somewhere? Or leave as is?
When you calculate the Performance NAV, you use special entity pricing target sources to allow for the additional valuation point and market value calculations. You must load pricing data released from the vendors into these target sources. The STAR to PACE Batch process pushes holdings data to the Eagle PACE data warehouse using these prices to carry out those market value calculations, storing them under a new Pace source instance.
...
The following diagram displays the Performance NAV processing workflow.
WRITERS NOTE: we do not typically include workflow diagrams for core engine enhancements. is this too technical for end users? if used, should we say the report at the end is the Performance NAV History report?
