> 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/moneyorder/reporting-moneyorder/money-order-device-report.md).

# Money Order Device Report

The Money Order Device Report summarizes money order sales and payment information. It can be printed individually as a POS Flash Report, or is included within the Close Shift Close Daily reports.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/1owSJLK1jIpKXTx7j6EL/images/image54.jpeg)

Report Details:

* TITLE: MONEY ORDER DEVICE REPORT
* STORE NUMBER: The listed store number.
* PERIOD INFORMATION: Logs the shift duration.
  * PERIOD: Shift open status.
  * OPEN PERIOD: Date and time the shift started.
    * MM/DD/YY: Date in month, date year format.
    * HH:MM:SS: Time in hour, minutes, and seconds.
  * CLOSE PERIOD: Shift close status.
* DESCRIPTION:
  * MONEY ORDER SALES: Money orders sold.
  * TOTAL MONEY ORDER SALES: The total money order sales reported.
  * VENDOR PAYMENTS: Vendor payouts made and printed.
  * TOTAL VENDOR PAYMENTS: The total vendor payouts.
  * TOTAL REFUNDS: The total refunds issued.
  * COUNT: The number of money orders sold and vendor payouts made.
  * AMOUNT: The amount of money orders and vendor payouts.


---

# 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/moneyorder/reporting-moneyorder/money-order-device-report.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.
