> For the complete documentation index, see [llms.txt](https://help.rafflelink.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rafflelink.com.au/managing-your-raffle/proceeds-and-finances/documentation/how-navigate-your-sales-report.md).

# How Navigate Your Sales Report

<figure><img src="/files/CRXXMWsv19bmFckK5KFi" alt="" width="375"><figcaption></figcaption></figure>

{% file src="/files/BIKL0I9554JJ5UJ5fiL4" %}
Sales Report Sample
{% endfile %}

### Sales Summary Section (Top)

* Organized by date showing daily transactions
* For each day, displays:
  * Tickets Sold
  * Number of Sales/Transactions
  * Cancelled Sales
  * Cash / Offline Sales Amount (Includes Any Paper Tickets Sold If Applicable)
  * Credit Card Sales Amount
  * Fee Assistance Amount
  * Total Sales Revenue

### Detailed Transaction Section (Bottom)

Each row represents a single transaction with:

#### Customer Information

* Transaction ID
* First Name
* Last Name
* Email Address
* Physical Address
  * Address Line 1
  * Address Line 2
  * Suburb
  * Postcode
  * State
  * Country
* Contact Numbers
  * Home Phone
  * Mobile Phone

#### Purchase Details

* Number of Tickets
* Ticket Numbers
* Cancelled Status
* Price + Fee Assistance

#### Additional Information

* Contact Consent
  * "Yes" or "No" indicating if they've opted in for future communications
* Extra Information
  * Responses to any custom questions you included in the ticket purchase form

*Note: In the example image, you can see transactions ranging from single tickets (#1-#4) to larger purchases (#10-#159), with varying amounts of fee assistance and contact consent preferences.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rafflelink.com.au/managing-your-raffle/proceeds-and-finances/documentation/how-navigate-your-sales-report.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.