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

# CDR Clearing

Every charging session ends with a Charge Detail Record — the billing record a CPO generates once the driver unplugs. In theory, the CDR is the clean, settled receipt. In practice, it isn't. Cost calculations drift. Fields go missing. Sessions complete but produce no CDR. Tariffs get applied inconsistently.

Without a layer to catch these, bad CDRs silently land in your invoicing. CDR Clearing is that layer.

Every CDR passing through ENAPI runs against a set of validation rules you define. Clean ones pass through. Problem ones land in [The CDR Inbox](/cdr-clearing/the-cdr-inbox.md) — flagged, visible, reviewable by both sides — before they reach finance.

### In this section

Move through the workflow in this order:

* [What is CDR Clearing](/cdr-clearing/what-is-cdr-clearing.md) — understand where CDR clearing fits.
* [Setting Up CDR Clearing](/cdr-clearing/setting-up-cdr-clearing.md) — configure rule sets and quarantine.
* [Validation Rules Reference](/cdr-clearing/validation-rules-reference.md) — review each rule and its purpose.
* [The CDR Inbox](/cdr-clearing/the-cdr-inbox.md) — work the day-to-day review queue.
* [How to Handle Flagged CDRs](/cdr-clearing/how-to-handle-flagged-cdrs.md) — decide when to accept, reject, or dispute.
* [Exporting CDR Data](/cdr-clearing/exporting-cdr-data.md) — export cleared data for downstream workflows.


---

# 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.enapi.com/cdr-clearing.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.