> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/end-of-day-report/end-of-day-report-contents/totals.md).
# Totals
The **Totals** section of the End of Day Report presents the financial summary of the trading day. It consolidates key figures relating to sales, costs, and profit, providing a clear snapshot of performance.
* **Orders Turnover** — Total value of all orders before deductions.
* **Service Charges** — Sum of service-related charges applied.
* **VAT** — Value Added Tax collected on sales.
* **Expenses** — Recorded operational expenses for the day.
* **Orders Net** — Net sales after service charges and VAT.
* **Theoretical Product Costs** — Expected cost of products based on sales.
* **Labour Cost** — Total staff wages and related labour expenses.
* **Actual Product Costs** — Recorded cost of products sold.
* **Total Cost** — Combined costs, including product and labour.
* **Profit** — Remaining balance after deducting total costs from net sales.
---
# 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.bossithq.com/end-of-day-report/end-of-day-report-contents/totals.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.
