> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/age-restriction/reporting-age-restriction/report-details.md).

# Report Details

* Date/Time: Date and Time of each transaction.
* Transaction ID: The ID or identifier of the transaction on the system.
* Cashier ID: The ID of the cashier who performed the transaction.
* Entry Method: The Entry Method (Skipped, Scanned, Swiped, Manual. Mobile).
* Min Age: The minimum age allowed to purchase the item.
* Birth Date: The birth date of the customer or default birth date based on current date if ID Check is skipped.
* Over Age: Indicates the customer is at least the age listed when the entry method is "Mobile".
* Age: The calculated age based on the birth date of the customer or default age based on current date.
* Cashier Name: Name of the cashier who performed the transactions.
* Cashier ID: ID of the cashier who performed the transactions.
* Scanned: Total count of drivers’ licenses scanned.
* Swiped: Total count of drivers’ licenses swiped.
* Manual Entry: Total count of all manual entries.
* Skipped: Total count of ID Check SKIPPED.


---

# 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.verifone.com/feature-references/features-and-products-references/age-restriction/reporting-age-restriction/report-details.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.
