> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/centre-de-documentation-payfacto/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/centre-de-documentation-payfacto/maitred-pos/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-a-r/ar-sales-by-category-and-revenue-center.md).
# AR Sales by Category and Revenue Center
Sales by Category and Revenue Center
Maitre'D's account receivable sales by category and Revenue Center report shows you sales closed to customers' accounts divided by Divisions Categories and Revenue Centers, according to your specifications. From the report filter window, select the dates, Revenue Centers, modes, customers, categories and divisions to be included in the report. The following is a sample of the account receivable sales by category and Revenue Center report:
For each Revenue Center, the report provides you with:
**Account:**
Account number.
**Name:**
Customer name.
**Categories:**
Sales closed to that account for the first three categories.
**Others:**
Sales closed to that account for the remaining categories.
**Taxes:**
Taxes charged to that account.
**Tips:**
Tips charged to that account.
**Total:**
Total charged to that account.
NOTE: By default, even customers who did not purchase anything will be included.
---
# 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/centre-de-documentation-payfacto/maitred-pos/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-a-r/ar-sales-by-category-and-revenue-center.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.