> 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/the-cdr-inbox.md). # The CDR Inbox Your daily view into CDR clearing activity. ### Navigation Go to **CDRs → Inbox**. ### Views * **To Review.** CDRs that failed one or more validation rules and need your attention. Shows a count of pending CDRs. CDRs that pass all rules are automatically accepted and don't appear here. * **Disputed.** CDRs where you and your partner disagree — one party accepted, the other rejected. Requires direct communication with your partner to resolve. Shows a count of disputed CDRs. * **All CDRs.** Every CDR across all partners and statuses. Use this for search, investigation, or bulk exports. **Start most days in To Review.** That's your active queue.

CDR Inbox.

### Reading the table * **You.** Your party ID and current status on this CDR (pending, accepted, rejected). * **Partner.** Your partner's party ID and status. * **Checks.** Color-coded badges for each validation rule: green = rules passed, red = rules failed, gray = missing CDR; hover over the badges to see which specific rules triggered. * **CDR ID.** Unique identifier for this CDR. * **Created.** When the CDR was generated. * **kWh**, **Duration**, **Cost.** Session values from the CDR. * **Calc. Cost.** ENAPI's independently calculated cost, for comparison with reported cost. * **Currency.** The CDR's currency.

Hovering over validation check badges.

### Filtering Filter by CDR ID, Session ID, Passed/Failed, start/end date, or owner. The filter bar persists across views — useful for isolating a billing period or a single partner across the whole inbox.

CDR filter options.

### Sorting Use **Display** to sort by created date, kWh, or cost. Toggle ascending or descending.

CDR sort options.

### CDR detail page Click any row to open the detail page: * **Transaction summary** — high-level overview. * **CDR details** — full OCPI fields. * **Rule checks** — each rule that ran, with pass/fail and the values used. * **Log** — status changes from both parties, timestamped. Use **View Session** to jump to the related charging session. ### Setting status Accept or reject a CDR to confirm whether it should be billed: * **Accept.** The CDR is accurate and should be included in billing. * **Reject.** The CDR is incorrect and should be excluded from billing. **From the table (bulk).** Check one or more rows — the header checkbox selects all on the current page — then **Set status → Accept** or **Reject** in the top right.

Bulk status update.

**From the detail page.** Open the CDR, then **Set status → Accept** or **Reject** in the top right.

Setting CDR status from the detail page.

**What happens next.** If your partner sets the same status, the CDR is marked completed. If your partner sets a different status, the CDR moves to **Disputed** and needs direct resolution with your partner. --- # 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/the-cdr-inbox.md?ask=&goal= ``` `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.