> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/design/enrolment-and-disbursement-cycles.md). # Enrolment & Disbursement Cycles A benefit program typically goes through two distinct repetitive cycles - enrolment cycles and disbursement cycles. These two cycles occur in parallel with different periodicities. {% embed url="" %} Figure showing Enrolment & Disbursement cycles in parallel with differing frequencies {% endembed %} The figure shows an example of a Benefit program with Enrolment Cycles occurring every six months - in January and June. Disbursement cycles are created every month. The Disbursement cycle will work on the latest approved enrolment list that's available. So in the example above, the disbursement cycle of Februrary will operate on the enrolment list created in January. Similary, the disbursement cycles of March, April, May and June will also operate on the enrolment list created in January. However the disbursement cycles starting from July onwards will start operating on the enrolment list created and approved in June, till the refreshed enrolment list is created and approved next January.

Program definition with Disbursement Cycle

--- # 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.openg2p.org/products/pbms/design/enrolment-and-disbursement-cycles.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.