CLOSINGBALANCEYEAR DAX Function (Time Intelligence) Context Transition
Evaluates the specified expression for the date corresponding to the end of the current year after applying specified filters.
Syntax
| Parameter | Attributes | Description |
|---|---|---|
|
Expression By Expression |
The expression to be evaluated. |
|
| Dates |
The name of a column containing dates, a single column table containing dates, or a calendar reference. |
|
| Filter | Optional |
A boolean (True/False) expression or a table expression that defines a filter. |
| YearEndDate | Optional |
End of year date. |
Return values
A scalar value that represents the expression evaluated at the last date of the year in the current context.
Notes
In order to use any time intelligence calculation, you need a well-formed date table. The Date table must satisfy the following requirements:
- All dates need to be present for the years required. The Date table must always start on January 1 and end on December 31, including all the days in this range. If the report only references fiscal years, then the date table must include all the dates from the first to the last day of a fiscal year. For example, if the fiscal year 2008 starts on July 1, 2007, then the Date table must include all the days from July 1, 2007 to June 30, 2008.
- There needs to be a column with a DateTime or Date data type containing unique values. This column is usually called Date. Even though the Date column is often used to define relationships with other tables, this is not required. Still, the Date column must contain unique values and should be referenced by the Mark as Date Table feature. In case the column also contains a time part, no time should be used – for example, the time should always be 12:00 am.
- The Date table must be marked as a date table in the model, in case the relationship between the Date table and any other table is not based on the Date.
Remarks
The dates argument can be any of the following:
- A reference to a date/time column. Only in this case a context transition applies because the column reference is replaced by
- CALCULATETABLE ( DISTINCT ( <Dates> ) )
- A table expression that returns a single column of date/time values.
- A Boolean expression that defines a single-column table of date/time values.
The syntax:
CLOSINGBALANCEYEAR ( <Expression>, <Dates> [, <Filter>] [, <YearEndDate>] )
corresponds to:
CALCULATE (
<Expression>,
ENDOFYEAR ( <Dates> [, <YearEndDate>] )
[, <Filter>]
)
The Dates argument can also be a calendar reference (calendar-based time intelligence). In that case, the year is the year that the calendar defines, for example a fiscal year.
CLOSINGBALANCEYEAR uses the last date of the year in the Dates column or in the calendar. It does not search for the last date that has data. For example, if a stock table has no row for the last day of the year, the result is BLANK. To get the value at the last date with data, use a different pattern, for example with LASTNONBLANK.
YearEndDate is a text literal with a date, for example “06-30”. The year part of the date is ignored, so “2001-06-30” and “06-30” give the same result. If you do not use Filter, you can write YearEndDate as the third argument. You cannot use YearEndDate with a calendar reference: in that case, CLOSINGBALANCEYEAR returns an error.
» 2 related functions
Examples
DEFINE
MEASURE Sales[Sales YTD] =
CALCULATE ( [Sales Amount], DATESYTD ( 'Date'[Date] ) )
MEASURE Sales[Sales OBY] =
OPENINGBALANCEYEAR ( [Sales YTD], 'Date'[Date] )
MEASURE Sales[Sales CBY] =
CLOSINGBALANCEYEAR ( [Sales YTD], 'Date'[Date] )
EVALUATE
CALCULATETABLE (
SUMMARIZECOLUMNS (
'Date'[Calendar Year Quarter],
'Date'[Calendar Year Quarter Number],
"Sales", [Sales Amount],
"Sales YTD", [Sales YTD],
"Sales OBY", [Sales OBY],
"Sales CBY", [Sales CBY]
),
'Date'[Calendar Year Month Number] <= 200812
)
ORDER BY 'Date'[Calendar Year Quarter Number]
| Calendar Year Quarter | Calendar Year Quarter Number | Sales | Sales YTD | Sales OBY | Sales CBY |
|---|---|---|---|---|---|
| Q1-2007 | 20071 | 2,646,673.39 | 2,646,673.39 | (Blank) | 11,309,946.12 |
| Q2-2007 | 20072 | 3,046,602.02 | 5,693,275.41 | (Blank) | 11,309,946.12 |
| Q3-2007 | 20073 | 2,885,246.55 | 8,578,521.96 | (Blank) | 11,309,946.12 |
| Q4-2007 | 20074 | 2,731,424.16 | 11,309,946.12 | (Blank) | 11,309,946.12 |
| Q1-2008 | 20081 | 1,816,385.21 | 1,816,385.21 | 11,309,946.12 | 9,927,582.99 |
| Q2-2008 | 20082 | 2,738,040.73 | 4,554,425.94 | 11,309,946.12 | 9,927,582.99 |
| Q3-2008 | 20083 | 2,575,545.59 | 7,129,971.53 | 11,309,946.12 | 9,927,582.99 |
| Q4-2008 | 20084 | 2,797,611.46 | 9,927,582.99 | 11,309,946.12 | 9,927,582.99 |
Related articles
Learn more about CLOSINGBALANCEYEAR in the following articles:
-
Semi-Additive Measures in DAX
Values such as inventory and balance account, usually calculated from a snapshot table, require the use of semi-additive measures. In Multidimensional you have specific aggregation types, like LastChild and LastNonEmpty. In PowerPivot and Tabular you use DAX, which is flexible enough to implement any calculation, as described in this article. » Read more
Related functions
Other related functions are:
Last update: Oct 28, 2026 » Contribute » Show contributors
Contributors: Alberto Ferrari, Marco Russo
Microsoft documentation: https://learn.microsoft.com/en-us/dax/closingbalanceyear-function-dax