How do I create a valuation point?

You can create a valuation point for a particular fund NAV type that nominates both:

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

• A queryAsAt datetime determining a cut-off point for settings and data to incorporate into the closed period.

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

Note that a valuation point has an initial status of Estimate, and that 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 all the data associated with the valuation point, so reports are always reproducible.

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 valuation point is identified by a diaryEntryCode that must be unique within the parent NAV type.

A valuation point must have an effectiveAt datetime, for example 2026-01-31T59:59:59Z.

You have the option to specify a different queryAsAt datetime to specify a cut-off for settings and data to flow into LUSID and be incorporated into the closed period. Note the following:

• If you omit this field, LUSID applies the datetime of the request to create the valuation point (that is, ‘now’). You can set queryAsAt to the same datetime as effectiveAt if you wish.

• Settings refers to configuration changes to fund components such as CoAs, posting rules, recipes and so on.

• Data refers to economic inputs such as new or updated transactions, settlement instructions, market data, and changes to instrument definitions (see also below).

You have the option to additionally specify:

• A holdingsAsAtOverride datetime to override queryAsAt for the following data: transactions (whether manually entered or generated by LUSID in response to instrument events), settlement instructions, changes to instrument definitions, and FX rates used in the calculation of transaction and portfolio cost.

• A valuationAsAtOverride datetime to override queryAsAt for data used to calculate the PV of instruments in portfolios: simple market data (quotes and FX rates), complex market data, and SRS results.

More information.

Properties

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

Subsequent updates

You cannot update a valuation point. However, for:

• An Estimate valuation point, you can call the UpsertDiaryEntryTypeValuationPoint API again to create a variant with the same diaryEntryCode and effectiveAt but perhaps a change to an asAt datetime or to a setting such as applyClearDown. You can then choose which variant to finalise. More information.

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

For any valuation point, you have the option to call DeleteValuationPoint API and re-open the closed period.