> For the complete documentation index, see [llms.txt](https://title5.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://title5.caqualityearlylearning.org/utilization-of-the-regional-market-rate-ceiling/limitations-on-reimbursement.md).

# Limitations on Reimbursement

18076

(a) Single Rate Category. Contractors shall only reimburse providers using a single rate category as defined in Section 18075.&#x20;

(b) Notwithstanding subsection (a), contractors may provide reimbursement to a provider using both a daily and an hourly rate when:&#x20;

&#x20;             (1) No single rate established by the provider corresponds to the family's need for care; and&#x20;

&#x20;             (2) The provider has established a rate in both daily and hourly rate categories pursuant to Section 18074.3; and&#x20;

&#x20;             (3) Using both rates is consistent with the rates the provider charges unsubsidized families needing similar hours of care.&#x20;

(c) Notwithstanding subsection (a), when Sections 18075(a)(2), 18075(a)(3), or 18075(b)(2) are applicable, contractors may reimburse providers for those categories in addition to the applicable single category.

&#x20;(d) Contractors shall not be bound by the regional market rate ceilings when there are, in the region, no more than two child care providers of the type needed by the subsidized family. For the purposes of this subsection, types of providers are licensed child care centers, licensed family child care homes, and exempt providers.

> NOTE: Authority cited: Sections 8265 and 8269, Education Code. Reference: Sections 8222, 8266.5 and 8357, Education Code.


---

# 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://title5.caqualityearlylearning.org/utilization-of-the-regional-market-rate-ceiling/limitations-on-reimbursement.md?ask=<question>&goal=<user_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.
