> 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-complete-online-documentation/chap-9-report-center/report/report-t-and-a/tips-declaration.md).

# Tips Declaration

Maitre'D tip declaration report shows employee's sales, the actual employee tip declaration, tip transfers and the rate the tip declaration represents. To work with this report you need to enable the enhance tip declaration under your T\&A options. It gives you a list of all the employee tip declaration done daily and then it summarizes the information. It also provides you with a receipt of tip declaration that can be signed by each employee. From the report filter window, select date or date range and employee(s) to be included in the report.

#### The following is a sample of the tip declaration report:

<img src="https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/Sample-TipsDeclaration.png" alt="" height="432" width="734">

**Date:**

Date of the actual tip declaration done by the employee

**Tippable Sales Column-A:**

Total of sales where cash tips have been paid.

**Declared Tips Column-B:**

Tip declared by the employee

**Other Tips Column-C:**

Tips received for other tasks then server (Doorman, Busboy, etc…)

**Received Tips Column-D:**

Tip received from another employee

**Remitted Tips Column-E:**

Tip transferred to another employee

**Total Tips Column-F:**

Declared Tips plus Other Tips plus Received Tips minus Remitted Tips. (B+C+D-E)

**Rate declared:**

Effective rate of Total Tips (F) according to Tippable Sales (A)


---

# 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-complete-online-documentation/chap-9-report-center/report/report-t-and-a/tips-declaration.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.
