> 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/usa/applications/payfacto-gift-datacandy/reporting.md).

# Reporting

## Reporting

### Reports

The Gift PayFacto application includes reporting functionality. For more information on gift card reporting, refer to the following topics:

* [About Reporting](#about-reporting)
* [View a Report](#view-a-report)

***

### About Reporting

The terminal can print reports, allowing you to view detailed or summary information on the day’s gift card transactions. You can print reports to view information on gift card transactions by employee of for the overall merchant account. Report data comes from the DataCandy server.

{% hint style="warning" %}
IMPORTANT: Gift card reports are based on the current day’s transactions. If you do not print a report for a specific day, you will not be able to print the previous day’s report the next day.
{% endhint %}

#### The available reports include:

* **Daily detail report by employee**: Prints a detailed report of all the day’s gift card transactions, separated by employee.
* **Daily summary report by employee**: Prints a summary report of the day’s different types of gift card transactions, separated by employee.
* **Daily summary report by merchant**: Prints a summary report of the day’s various types of gift card transactions for the merchant account.

***

### View a Report

Regardless of the report you want to view, the procedure is the same. Viewing the detailed report for the current batch of transactions allows you to see each individual transaction’s details and allows you to reprint or void the transaction if desired.

#### **To view a detailed list of transactions for the current batch:**

1. Touch the **Action** button on the main screen. <img src="https://documentation.payfacto.com/PF_GiftCard_DataCandy/UG/CA-EN/assets/images/image3.png" alt="Action" data-size="line">
2. Touch **Settings**.  <img src="https://documentation.payfacto.com/PF_GiftCard_DataCandy/UG/CA-EN/assets/images/image19.png" alt="Transactions" data-size="line">
3. Enter the Admin password and touch **OK**.
4. The selected report appears on the terminal screen.In the **Details and summary reports** section, touch the report you want to view:
   * **Daily detail report by employee**
   * **Daily summary report by employee**
   * **Daily summary report by merchant**

![Details and summary reports](https://documentation.payfacto.com/PF_GiftCard_DataCandy/UG/CA-EN/assets/images/image50.png)\
The selected report appears on the terminal screen.

5. Touch the **Back** icon to return to the main screen.  <img src="https://documentation.payfacto.com/PF_GiftCard_DataCandy/UG/CA-EN/assets/images/image21.png" alt="Back icon" data-size="line">


---

# 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/usa/applications/payfacto-gift-datacandy/reporting.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.
