> 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/automatic-end-of-day/using-aeod/close-day-cashier-messages.md).

# Close Day Cashier Messages

From Verifone Commander Release 56.00 onwards, the close day cashier messages have been updated to better indicate EPS/payment host issues.

These failure messages are only displayed on distributions where the payment host front end processor (FEP) supports failure responses. This includes Buypass/Fiserv and Shell but does not include Phillips 66.

## Manual Close with Host Failure Message

<div align="center"><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/pG0jW3i7OkNOEIxN38Au/Unknown%20image" alt=""></div>

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/IPa2w73vnM61vsBQ8yQU/Unknown%20image)

## AEOD Failed With Suspended Transaction

<div align="center"><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/J5zwYKqtModYSR0pi0WY/Unknown%20image" alt=""></div>

## AEOD with Host Failure Message

<div align="center"><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/aUwI6uq8cVWM5FlilspA/Unknown%20image" alt=""></div>

If “Ignore Network Error” is enabled in Configuration Client > Reporting > Report Configuration > Auto End OF Day (AEOD), the following message appears:

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/tDC1DrKfCDSjKFCrgTfq/Unknown%20image)


---

# 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/automatic-end-of-day/using-aeod/close-day-cashier-messages.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.
