Office Admin Explorer

Use starting year for FY numbering

Registry value
use starting year for fy numbering
Group PolicyUse starting year for FY numbering
German versionAnfangsjahr zur Nummerierung des Geschäftsjahrs verwenden
Intune settings catalogUse starting year for FY numbering (User)
ScopeUser · HKCU
ADMXproj16.admx · L_PjStartingYear
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Project 2016\Project Options\Calendar
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Project 2016\Projektoptionen\Kalender

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\ms project\options\calendar
use starting year for fy numberingEnabled = 1 · Disabled = 0

Not configured = the value does not exist – the application default applies and users may change the setting.

PowerShell

Check the current value (read-only)

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
foreach ($name in @('use starting year for fy numbering')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'use starting year for fy numbering' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null   # Enabled
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Disable
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'use starting year for fy numbering' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # Disabled
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
Remove-ItemProperty -Path $key -Name 'use starting year for fy numbering' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Use starting year for FY numbering (User)

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/proj16v2~Policy~L_Proj~L_ProjectOptions~L_PjCalendar/L_PjStartingYear
Data typeString
Value<enabled/> · <disabled/>

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Use starting year for FY numbering. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

Labels the fiscal year using the calendar year in which the fiscal year begins.

If you enable this setting, the label for the fiscal year is the calendar year in which the fiscal year begins.

If you disable or do not configure this setting, the user's default setting is used.

Same category: Microsoft Project 2016 › Project Options › Calendar

All policies in this category · All 140 policies of proj16.admx