> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/item-correct-detail.md).
# Item Correct Detail
Maitre'D item correct detail report provides you with a list of all the items that were removed from server's tables by manager before they were ordered for the selected date or period of time per manager. From the report filter window, select the date, revenue center and employees to be included in the report. The following is a sample of the item correct detail report:
Name and number (from POS Control) of the manager who removed the item.
**Time:**
The time the item was removed.
**Server:**
The server # (from POS Control) for whom the item was removed.
**Table:**
Table number on which the item was removed.
**Clients**
Amount of customers at the table
**Item Description:**
Sales item description
**Item Id:**
Revenue center number (from POS Control) of the removed item.
**Quantity:**
Quantity of items removed.
**Revenue Center:**
Revenue center name, revenue center the item was originally ordered from.
**Amount:**
$ Value of the item removed.
---
# 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://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/item-correct-detail.md?ask=&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.
