> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-a-r/ar-invoice-detail-search.md).

# AR Invoice Detail Search

Account Receivable

Invoice Detail Search

Maitre'D's account receivable invoice detail search report shows you the actual detailed invoice settled to the accounts receivable media type according to your specifications. It helps to retrieve and reprint specified invoices. From the report filter window, select the date and time range, amounts, invoices, tables, employees, items, promotions, Revenue Centers, modes and customers to be included in the report. The following is a sample of the account receivable invoice detail search report:

&#x20;

<img src="https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/ARInvoiceDetailSearch_files/image001.jpg" alt="" height="671" width="778">

It reports the invoice in the same layout format it was printed out at the workstation. In addition, it also reports the time the item was ordered.

&#x20;

&#x20;

<br>


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/report-center/report/report-a-r/ar-invoice-detail-search.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.
