> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/reporting.md).

# Reporting

### **Close Period**

The Close Period command allows authorized users to manually trigger a period close on the Verifone Commander from Commander Central. This is useful when an end-of-day or end-of-period close needs to be initiated remotely without requiring on-site access.

Navigation: Verifone Commander Central > Site Management > (Select Site) > Reporting > Close Period.

<figure><img src="https://2845923820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff8N3RLcEwSqYn1EvDXrj%2Fuploads%2Fnt78o6ykP7ZufTQseOjS%2Fimage.png?alt=media&amp;token=8e6156f1-84c7-4e0b-9c79-187eb94cd9a5" alt=""><figcaption></figcaption></figure>

To close a period:

{% stepper %}
{% step %}
**Navigate**

Navigate to Reporting > Close Period.
{% endstep %}

{% step %}
**Select Period**

From the Period Type drop-down, select the period type you want to close.
{% endstep %}

{% step %}
**Override Failure**

If a payment host network failure is present and you have been advised to proceed anyway, select the Override Network Failure checkbox.
{% endstep %}

{% step %}
**Review History**

Review the history table to see the date and time of the last period close.
{% endstep %}

{% step %}
**Apply Changes**

Select Apply Changes.
{% endstep %}

{% step %}
**Confirm Close**

Review the confirmation prompt. Confirm the period type and override setting shown are correct, then select Close Period Now.
{% endstep %}

{% step %}
**Track Status**

The command is sent to the Commander. The history table updates with a new entry showing the submission timestamp and status.
{% endstep %}
{% endstepper %}

<table><thead><tr><th width="216" valign="top">Field / Button</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Close Period Now</td><td valign="top">After applying the changes, it sends a period close command to the Commander at the site. A confirmation prompt is displayed before the command is submitted.</td></tr><tr><td valign="top">Period Type*</td><td valign="top">Required. A drop-down list specifying which type of reporting period to close on the Commander. Select the period type before submitting the close command. Available options depend on the site's Commander configuration - see Period Type Options below. Defaults to Day.</td></tr><tr><td valign="top">Override Network Failure</td><td valign="top">Optional checkbox. When selected, the close period command is sent to the Commander even if a payment host network failure is detected at the site. When not selected (default), a network failure will cause the close to fail rather than proceed.</td></tr><tr><td valign="top">Apply Changes</td><td valign="top">Submits the Close Period command to the Commander with the selected Period Type and Override Network Failure settings. A confirmation prompt is displayed before the command is sent.</td></tr><tr><td valign="top">Discard</td><td valign="top">Resets the Period Type and Override Network Failure fields to their default values without submitting a command.</td></tr></tbody></table>


---

# 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://commanderhelp.verifone.com/customer-documentation/petro-and-c-store/commander-central/commander-central-user-guide/site-configuration/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.
