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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/modeling/models/fiscal-month-offset",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# fiscal_month_offset

> Sets a fiscal calendar in Omni and enables adding fiscal time metrics to time dimension groups and filters in the UI.

Sets a fiscal calendar in Omni and enables adding fiscal time metrics to time dimension groups and filters in the UI.

<Tip>
  `fiscal_quarter` and `fiscal_year` timeframes will not work without a `fiscal_month_offset`.
</Tip>

This parameter can be set dynamically using a [user attribute](/administration/users/attributes), which is useful when different users or business units use different fiscal calendars.

## Syntax

```yaml theme={null}
fiscal_month_offset: positive_or_negative_number
```

<ParamField path="fiscal_month_offset" type="number">
  A positive or negative number used to set the fiscal calendar. A positive month offset will set the fiscal calendar in front of the [Gregorian calendar date](https://en.wikipedia.org/wiki/Gregorian_calendar).

  Can be set dynamically using [user attributes](/administration/users/attributes). See the [**Examples**](#dynamic-value-using-user-attributes) section for an example.
</ParamField>

## Examples

### Static values

```yaml title="Feb 1 start - FY Month 1 of 2025 = Feb 2024" theme={null}
fiscal_month_offset: 11
```

```yaml title="March 1 start" theme={null}
fiscal_month_offset: 10
```

```yaml title="Feb 1 start but FY Month 1 of 2024 = Feb 2024" theme={null}
fiscal_month_offset: -1
```

### Dynamic value using user attributes

This example assumes your Omni instance has an existing user attribute called `fiscal_offset` and that users have been assigned appropriate numeric values, such as `11` for users in Region A, `10` for users in Region B, etc.

```yaml title="Set fiscal month offset based on user's region" theme={null}
fiscal_month_offset: {{ omni_attributes.fiscal_offset }}
```