> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-installation-configuration-and-troubleshooting-solutions/troubleshooting/sales/sale-summary-disabled-in-sale-bill-window.md).

# Sale summary disabled in sale bill window

**YouTube:** [Sale summary disabled in sale bill window](https://www.youtube.com/watch?v=iMWINGBoXHw)

 In this tutorial, we’ll address a common issue encountered in **Logic ERP** where the **daily sales summary** is not displayed when pressing **Ctrl + F5** in the Sale Bill window — even though transactions exist for the day.

***

### Understanding the Problem

1. Navigate to the **Main Menu** and open the **Sale Bill** window.
2. Press **Ctrl + F5** to view the **Sales Summary**.
3. You may observe that the **summary is showing as nil or empty**.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fxzvb1ngAo6uaRdLmaVuq%2FShowing%20Sale%20Summery%20as%20zer.png?alt=media&amp;token=d12257ee-2021-4801-a9de-763f3595ea0a" alt=""><figcaption></figcaption></figure>

* However, when you right-click on the **Modify** button and check the transaction list:
  * You can see that **bills exist** for the current date.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F949MBKI45RYFbYd9Bfzx%2FSale%20Bill%20Modify.png?alt=media&amp;token=316aedd9-c662-4f7d-8728-3e2ab7bc5224" alt=""><figcaption></figcaption></figure>

* But these are not reflected in the **sales summary**.

***

### Step-by-Step Solution

* Navigate to the **Main Menu**.
* Expand the **Utilities** module.
* Click on **General Utilities**.
* From the list of utilities, select **“Update Zero Records from New Fin Year.**
* A confirmation prompt will appear — click **Yes** to proceed.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fikr4VASclzrM7cZsqAYx%2FUpdate%20Zero%20record.png?alt=media&amp;token=95bd035d-3a3d-4719-b92d-d7b5a7b44ecc" alt=""><figcaption></figcaption></figure>

* The utility will now execute and update any missing summary records.

***

### Final Check

* Return to the **Sale Bill** window.
* Press **Ctrl + F5** again to view the **Sales Summary**.
* You will now observe that the **summary is visible and accurate** based on the existing bills.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FznX607vVRzuiuD64Lkqw%2FUpdated%20Sale%20Summery.png?alt=media&amp;token=766c551f-5585-4506-83d0-2ec58e9815e5" alt=""><figcaption></figcaption></figure>

***

This process helps fix discrepancies between the transaction data and its display in daily summaries, ensuring accurate sales monitoring within the system.


---

# 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://kb.logicerp.com/logic-erp-installation-configuration-and-troubleshooting-solutions/troubleshooting/sales/sale-summary-disabled-in-sale-bill-window.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.