> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/clerk-guide/accepting-and-rejecting.md).

# Accepting and Rejecting

Once you have reviewed the documents and verified the filing information, you make a decision: accept, reject, partially accept, or route to a judge.

## Accepting a Filing

1. **Configure stamps** before accepting. In the document viewer, add stamps to each document as needed (see [Reviewing a Filing -- Stamps](/clerk-guide/reviewing-a-filing.md#document-viewer)). Lock each stamp in place when you are satisfied with its position. You can add multiple stamps to the same document.
2. Click the **Accept** button (or press **Alt + A**).
3. The Accept dialog opens, showing:
   * A summary of the filing (case and filer).
   * A fee / ledger breakdown (hidden for criminal filings).
   * An **Assign Filing To** party selector -- choose the party all docket entries are booked against.
   * For new cases, a **Filing Date** field for the Verdict CMS case.
   * A summary of which documents will be stamped and with which stamp types.
4. Click **Accept** to confirm.

When you confirm:

* The filing fee is charged to the filer's stored payment card (if applicable).
* The filing status changes to **Accepted**.
* All pending documents are marked as accepted.
* Court stamps are burned into accepted documents using the positions you configured.
* The filing is recorded in the Verdict CMS -- a case is created (for new-case filings) or a docket entry is added (for existing-case filings).
* The filer receives an in-app notification and email confirmation.
* The queue item moves to the **Accepted** sub-tab under **Processed**.

{% hint style="info" %}
**📹 GIF:** Accepting a filing -- clicking the Accept button, the Accept dialog showing the filing summary and stamp preview, clicking Accept, and the filing moving to the Processed tab's Accepted sub-tab in the queue.
{% endhint %}

{% hint style="warning" %}
If the filer requested a fee waiver and you have not yet approved or denied it, acceptance is blocked. The dialog forces you to decide the waiver first -- otherwise the filer could be charged while the request sits undecided.
{% endhint %}

{% hint style="info" %}
If payment fails, the filing moves to **Payment Failed** status. The filer is notified and can retry payment. The filing does not need to be re-reviewed.
{% endhint %}

{% hint style="info" %}
If stamping fails for a document, the filing is still accepted. You will receive a system notification alerting you to the unstamped document so you can address it manually.
{% endhint %}

## Partial Accept

If some documents pass review but others do not:

1. In the review panel, set each document's status individually -- **Accepted** or **Rejected**.
2. Click **Accept** (the confirm button reads **Partial Accept** once the dialog detects a rejected document). The filing status is set to **Partial Accept**.
3. The filer is notified that their filing was partially accepted and told which documents were rejected.

Partially accepted filings are still recorded in the CMS. The rejected documents are excluded from the case record.

## Rejecting a Filing

1. Click the **Reject** button (or press **Alt + R**).
2. The Reject dialog opens. Fill in the required fields:
   * **Reason code** (required) -- Select the primary reason:
     * Incomplete Filing
     * Incorrect Form
     * Missing Signature
     * Incorrect Fee
     * Wrong Court
     * Duplicate Filing
     * Defective Service
     * Other
   * **Notes** (optional) -- Provide additional detail for the filer.
   * **Cure deadline** (optional) -- Set a date by which the filer must resubmit.
3. Optionally add **deficiency notices** to document specific problems (see [Reviewing a Filing](/clerk-guide/reviewing-a-filing.md#adding-deficiency-notices)).
4. Click **Reject Filing**.

When you confirm:

* The filing status changes to **Rejected**.
* All pending documents are marked as rejected.
* The filer receives an in-app notification and email with the reason, notes, and cure deadline.
* The queue item moves to the **Rejected** sub-tab under **Processed**.

The filer can resubmit based on your feedback. Resubmitted filings link back to the original rejected filing.

{% hint style="info" %}
**📹 GIF:** Rejecting a filing -- clicking the Reject button, selecting "Incomplete Filing" as the reason, typing notes, setting a cure deadline date, adding a deficiency notice, and clicking Reject Filing.
{% endhint %}

## Routing to a Judge

Some filings need judicial review before you can make a decision (e.g., fee waiver requests requiring court approval, sealed filings, or complex procedural matters).

1. In the review panel, select **Route to Judge**.
2. Choose the judge from the dropdown (only active judges at your court are listed).
3. Write a **routing note** explaining what the judge needs to decide.
4. Optionally set a **due date** for the judge's response.
5. Confirm.

The filing status changes to **With Judge**. When the judge returns the filing, it comes back to the clerk queue with the judge's notes and decision.

{% hint style="info" %}
**📹 GIF:** Routing a filing to a judge -- clicking "Route to Judge" in the review panel, selecting a judge from the dropdown, writing a routing note, setting a due date, and clicking Confirm.
{% endhint %}

{% hint style="warning" %}
Only route to a judge when the matter genuinely requires judicial authority. Routine deficiencies (wrong form, missing signature) should be rejected directly so the filer can fix and resubmit quickly.
{% endhint %}

## Fee Waiver Decisions

If a filer requested a fee waiver, a banner appears on the filing during review.

* Click **Approve** to waive the fee. The filer is notified by email.
* Click **Deny** to deny the waiver. The filer is notified and the original fee applies.

Fee waiver decisions are audit-logged with the clerk who made the decision.

## Fee Overrides

You can override the system-calculated fee for a filing:

1. In the fee section of the review panel, click **Override Fee**.
2. Enter the new amount and a reason for the override.
3. Save.

The override replaces the calculated fee for this filing only. Your name is recorded as the overriding clerk. To revert, click **Remove Override** and the original calculated fee is restored.

## After Your Decision

After accepting or rejecting a filing:

* Acceptance shows a progress overlay that walks through each step (stamping, recording in Verdict, charging payment) and then returns you to the queue. Rejection confirms and returns you to the queue.
* You are returned to the queue once the action completes.

## Docket Entries

You can manually create docket entries on a filing from the review panel. Enter an **event code** and **description**. Docket entries are recorded against the filing and appear in the case timeline.


---

# 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.cottfile.com/clerk-guide/accepting-and-rejecting.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.