> For the complete documentation index, see [llms.txt](https://docs.communityinclusion.org/training-and-technical-assistance-materials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.communityinclusion.org/training-and-technical-assistance-materials/state-plan-expenditure-tracking-and-reporting-reporting/budgeting-cycle.md).

# Budgeting Cycle

The budgeting cycle for a Section 4 AT Act grantee should identify a specific target date for obligation and liquidation of the entire fiscal year grant award long before the final deadline for each. This is especially true when grant funds are used for external contracts for which there is no guarantee of funding being liquidated by the final deadline date. The obligation deadline for all grants is September 30 of the carryover year — 24 months from the award date. The liquidation deadline is December 31 of the carryover year — 27 months from the award date. A recommended budget cycle sets April 1 in the carryover year as the target date for liquidation of all funds in the prior fiscal year award. This target date provides ample time to address contractors not submitting invoices on time or other unexpected situations resulting in liquidations not occurring as expected.

Applied to a single fiscal year award, an appropriate budgeting cycle is as follows:

* Award start date of October 1
* Obligate and liquidate that award in the next 18 months
* Target liquidation date of April 1
* April through September is available to de-obligate and re-obligate if necessary
* October through December is available to liquidate if necessary

Using this kind of budgeting cycle will help ensure that all grant funds are liquidated in a timely manner.

*Last updated January 2023*

<figure><img src="/files/aJamcP9YMgoOQiXPRjNe" alt="catada logo"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.communityinclusion.org/training-and-technical-assistance-materials/state-plan-expenditure-tracking-and-reporting-reporting/budgeting-cycle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
