> 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/feature-references/features-and-products-references/auto-upgrade/configuring-auto-upgrade/advanced-preparation/day-close-requirement.md).

# Day Close Requirement

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Released</td><td valign="top">Base057.01.00 · Base057.00.02 · Base056.03.02 · Base055.02.10</td></tr><tr><td valign="top">Applies to</td><td valign="top">All Commander sites running Auto Upgrade</td></tr><tr><td valign="top">Action required</td><td valign="top">Perform a Day Close or Shift Close from the POS before every Auto Upgrade</td></tr></tbody></table>

**What Changed and Why**

This update resolves two issues with Auto Upgrade that could cause unexpected failures or allow an upgrade to run when it should not. Both issues are now fixed across all upgrade types.

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><p>Fix 1 — False Upgrade Failure After Quiet Days</p><p>Previously, if a Day Close had been performed correctly but no transactions occurred for one or more days afterward, the Auto Upgrade could fail with a false error claiming the day was not closed. The site had done everything right — the system was wrong. This false failure is now corrected.</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><p>Fix 2 — Day Close Now Required for Partial Upgrades</p><p>Upgrades can run as a Full Upgrade (all modules installed) or a Partial Upgrade (only selected modules installed, no OS reinstall). Full Upgrades already required a Day Close or Shift Close before proceeding. Partial Upgrades did not — this gap is now closed.</p><p>Both upgrade types now consistently require a period close before the upgrade can proceed. If this is not done, the upgrade will be blocked with a clear error message.</p></td></tr></tbody></table>

**What to Do Before Every Auto Upgrade**

Before initiating any Auto Upgrade, perform a Day Close or Shift Close from the POS. This closes any open network batches and puts the Commander in a clean state for the upgrade.

{% hint style="info" %}
If you are unsure whether your site uses Day Close or Shift Close, check with your manager or your Verifone support contact.
{% endhint %}

This step is required even if your site has not had any transactions recently.

**Error Messages**

If a Day Close or Shift Close has not been performed before an Auto Upgrade, the upgrade will be blocked and one of the following messages will appear:

<table data-header-hidden><thead><tr><th width="113" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>E9095</strong></td><td valign="top"><p><em>"Software auto-upgrade failed due to open reports in Period-2. Perform Period-2 close and initiate auto-upgrade."</em></p><p>Action: Perform your Day Close or Shift Close from the POS, then re-stage and retry the upgrade.</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="113" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>E9096</strong></td><td valign="top"><p><em>"Software auto-upgrade failed due to open reports in Period-1. Perform Period-1 close and initiate auto-upgrade."</em></p><p>Action: Perform your Day Close or Shift Close from the POS, then re-stage and retry the upgrade.</p></td></tr></tbody></table>

{% hint style="info" %}
Period-1 and Period-2 are internal system names. Depending on your site configuration, they correspond to either Shift Close or Day Close. The action is the same in both cases: close the open period from your POS.
{% endhint %}

**Steps to Resolve E9095 or E9096**

1. Perform a Day Close or Shift Close from the POS:

   Use the same procedure your site follows for a regular end-of-day or end-of-shift close.
2. Re-stage the software upgrade:

   Stage the upgrade again as you normally would.
3. Retry Auto Upgrade:

   The upgrade will proceed normally once all open periods are closed.

**Frequently Asked Questions**

**My site has not had any transactions in a few days. Do I still need to perform a Day Close?**

Yes. Perform a Day Close (or Shift Close) from the POS before initiating Auto Upgrade, regardless of whether any transactions occurred. This is required even on quiet days.

Does this apply to both Full Upgrades and Partial Upgrades?

Yes. The Day Close requirement now applies consistently to all upgrade types — both Full Upgrades and Partial Upgrades.

**Which Commander software versions include this fix?**

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Version</td><td valign="top">Includes This Fix</td></tr><tr><td valign="top">Base055.02.10</td><td valign="top">Yes</td></tr><tr><td valign="top">Base056.03.02</td><td valign="top">Yes</td></tr><tr><td valign="top">Base057.00.02</td><td valign="top">Yes</td></tr><tr><td valign="top">Base057.01.00</td><td valign="top">Yes</td></tr></tbody></table>

**The upgrade still fails after I performed a Day Close. What should I do?**

Contact Verifone support and provide the error code (E9095 or E9096). You can also visit the Commander Help Center and search for "Auto Upgrade Failed Due to Open Reports" for additional guidance.


---

# 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/feature-references/features-and-products-references/auto-upgrade/configuring-auto-upgrade/advanced-preparation/day-close-requirement.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.
