---
title: "How do I create a valuation point?"
slug: "how-do-i-create-a-valuation-point"
updated: 2026-03-02T13:31:19Z
published: 2026-03-02T13:31:19Z
canonical: "support.lusid.com/how-do-i-create-a-valuation-point"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I create a valuation point?

You can create a *valuation point* (VP) for a [NAV type](/v1/docs/how-do-i-create-a-fund#understanding-nav-types) 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](/v1/docs/striking-a-nav#creating-a-valuation-point-with-closure-date-and-cutoffs).

You should use a VP when you [strike a NAV](/v1/docs/striking-a-nav) or [generate other financial reports](/v1/docs/generating-fund-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](/v1/docs/how-do-i-create-a-valuation-point#working-with-multiple-vps).
- You can strike an ad-hoc NAV without closing a period using a [bookmark](/v1/docs/how-do-i-create-a-bookmark) instead of a VP. Note LUSID does not persist associated data.

## Methods

LUSID web appLUSID APILuminesce

Call the [UpsertDiaryEntryTypeValuationPoint](https://www.lusid.com/docs/api/lusid/endpoints/funds/UpsertDiaryEntryTypeValuationPoint) API, for example:

```json
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"
}'
```

Navigate to **Fund Accounting > Calendar Management**, select a fund and click **Create valuation point**:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-ANKUC6IL.png)

Write a Luminesce SQL query using the [Lusid.Fund.ValuationPoint.Writer](/v1/docs/lusidfundvaluationpointwriter) provider and execute it using a tool such as the LUSID web app, for example:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(969).png)

## Data fields and properties

This section supplements the [API documentation](https://www.lusid.com/docs/api/lusid/endpoints/funds/UpsertDiaryEntryTypeValuationPoint) 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](/v1/docs/striking-a-nav#creating-a-valuation-point-with-closure-date-and-cutoffs).

### Properties

You can optionally extend the data model of a VP by adding [custom properties](/v1/docs/properties) from the `DiaryEntry` domain.

## Subsequent updates

You cannot update a VP. However, for:

- An `Estimate` VP, you can call the [UpsertDiaryEntryTypeValuationPoint](https://www.lusid.com/docs/api/lusid/endpoints/funds/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](/v1/docs/striking-a-nav#creating-multiple-variants-of-the-same-estimate).
- A `Final` VP, you can call the [RevertValuationPointToEstimate](https://www.lusid.com/docs/api/lusid/endpoints/funds/RevertValuationPointToEstimate) API to revert to a status of `Estimate`.

For any VP, you have the option to call [DeleteValuationPoint](https://www.lusid.com/docs/api/lusid/endpoints/funds/DeleteValuationPoint) API and start over.

## Working with multiple VPs

The previous VP must be [finalised](/v1/docs/striking-a-nav#finalising-an-estimate-to-officially-close-a-period-and-persist-data) (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.

| **Scenarios** | **T1** | **T2** | **T3+ →** | **Explanation** |
| --- | --- | --- | --- | --- |
| **Possible** |  | No VP |
| `Estimate` |  | One estimate VP |
| `Final` |  | One finalised VP |
| `Final` | `Estimate` |  | Mix of estimate/finalised (providing estimate follows finalised) |
| `Final` | `Final` |  | Multiple finalised VPs |
| **Not possible** |  | `Estimate` |  | Estimate cannot follow no VP |
| `Estimate` | `Estimate` |  | Estimate cannot follow estimate |
| `Estimate` | `Final` |  | Finalised cannot follow estimate |