How do I create a valuation point?

You can create a valuation point (VP) for a NAV type in a particular fund that nominates both:

• An effectiveAt datetime marking the closure of the current accounting period for that NAV type and simultaneously the opening of the next period.

• A queryAsAt datetime determining a cut off for settings and data to incorporate into the closed period for that NAV type. Note other as at fields are available to exert fine-grained control over data cut offs.

You should use a VP when you strike a NAV or generate other financial reports.

Note the following:

• A VP has an initial status of Estimate, and striking a NAV is part of a workflow with checks and balances. Only when the status is Final does LUSID officially close the period and persist data associated with the VP, so reports are always reproducible.

• You cannot create a new VP (with a status of Estimate) unless the previous period is officially closed (the preceeding VP has a status of Final). LUSID automatically sets the start of the new VP to the end of the old. More information.

• You can strike an ad-hoc NAV without closing a period using a bookmark instead of a VP. Note LUSID does not persist associated data.

Methods

curl -X POST 'https://<your-domain>.lusid.com/api/api/funds/MyFunds/Growth/valuationpoints?navTypeCode=OFFICIAL'
  -H 'Content-Type: application/json-patch+json'
  -H 'Authorization: Bearer <your-API-access-token>'
  -d '{
  "diaryEntryCode": "31Jan2025",
  "name": "End January 2025",
  "effectiveAt": "2025-01-31T17:00:00.0000000+00:00",
  "queryAsAt": "2025-01-31T19:59:59.0000000+00:00"
}'

Data fields and properties

This section supplements the API documentation and on-screen help text in the LUSID web app.

Fields

A VP is identified by a diaryEntryCode that must be unique within the parent NAV type.

For more information on the effectiveAt, queryAsAt, holdingsAsAtOverride and valuationsAsAtOverride fields, see the NAV documentation.

Properties

You can optionally extend the data model of a VP by adding custom properties from the DiaryEntry domain.

Subsequent updates

You cannot update a VP. However, for:

• An Estimate VP, you can call the UpsertDiaryEntryTypeValuationPoint API again to create a variant with the same diaryEntryCode and effectiveAt but perhaps different as at timestamps or a change to a field such as applyClearDown. You can then choose which variant to finalise. More information.

• A Final VP, you can call the RevertValuationPointToEstimate API to revert to a status of Estimate.

For any VP, you have the option to call DeleteValuationPoint API and start over.

Working with multiple VPs

The previous VP must be finalised (status set to Final, signifying a closed period) before you can create a new VP (with a status of Estimate).

The effectiveAt, queryAsAt, holdingsAsAtOverride and valuationsAsAtOverride timestamps of the new Estimate VP must all be later than those of the previous Final VP. Note only data since this last closed period is included in Estimate VP reports.