> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/create-a-budget/period-types-in-budgets.md).
# Period types in budgets
{% hint style="info" %}
Periods are a core concept in Phocas. Read the Phocas basics > [Periods page](/basics/getting-started/periods.md) to learn more about the **Period** menu in Phocas and the different types of periods.
{% endhint %}
When [creating a budget](/budgets-and-forecasts/owner-and-administrator/create-a-budget.md), the available **Period type** options depend on the [period types](broken://pages/prvMVIptJ9sBhfiVtRix) that were added to the underlying database by the Phocas Implementations team or your administrator.
Typically, you can select either a Monthly or Yearly period type but you might also have the option to select a Custom period type. For example, you might want to create a quarterly budget or one based on a 4-4-5 calendar.
When you select the **Custom** option from the **Period Type** list, a new setting displays, allowing you to select the specific custom period to use and specify the start and end dates.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.phocassoftware.com/budgets-and-forecasts/owner-and-administrator/create-a-budget/period-types-in-budgets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
