> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/enforcement-provisions/denial-or-revocation-of-license-for-failure-to-pay-civil-penalties.md).

# Denial or Revocation of License for Failure to Pay Civil Penalties

101198.1

(a) The licensee shall be responsible for paying civil penalties. 

   (1) Unless otherwise provided, the transfer, surrender, forfeiture or revocation of a license shall not affect the licensee's responsibility for paying any civil penalties accrued while the license was in effect. 

(b) The Department shall have the authority to deny or revoke any license for failure to pay civil penalty assessments. 

   (1) The Department shall have the authority to approve payment arrangements acceptable to the Department. 

   (2) The Department shall have the authority to approve the form of payment. 

   (3) The licensee's failure to pay civil penalty assessments pursuant to a payment plan approved by the Department may result in the denial or revocation of any license, and/or any other appropriate action. 

(c) Any denial or revocation of the license for failure to pay civil penalties may be appealed as provided by Health and Safety Code Section 1596.887.

> NOTE: Authority cited: Section 1596.81, Health and Safety Code. Reference: Sections 1596.81, 1596.871, 1596.887, 1596.98, and 1596.99, Health and Safety 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://t22.caqualityearlylearning.org/enforcement-provisions/denial-or-revocation-of-license-for-failure-to-pay-civil-penalties.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.