> 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-version-release-notes/october-2026/reports-queries/financial-analysis/cash-summary-report.md). # Cash Summary Report Logic ERP has corrected the **Cash Summary Report** for branch-wise reporting, for cash accounts with no entries in the period, and for days when sales returns are more than cash sales. *** ### **Step 1: Open the Report** * Navigate to **Reports/Queries** and select **Financial Analysis**. * Open the **Cash Summary Report**. *** ### **What's corrected** * When the **BRANCH NAME** column is shown, each branch of a cash account now has its own opening balance, closing balance and account total. * A cash account with an opening balance but no entries in the selected period now shows one row: the date is blank and the closing balance equals the opening balance. Its closing balance is now part of the grand **CLOSING BALANCE**, which can **rise**. This is intended. An account with no entries and a zero balance stays hidden. * The report now opens without an error when the **BRANCH NAME** column is shown and **Report Generation** is set to **Cash Amount Wise Consolidated**. This works for every **Period** choice (**Date Wise**, **Month Wise**, **Consolidated**). * **CASH SALES** now shows a negative figure when cash sales returns for the period are more than cash sales. If **Cash Sale** is ticked under **Total Inwards As**, **TOTAL INWARDS** will be **lower** than before on those days. This is intended. --- # 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-version-release-notes/october-2026/reports-queries/financial-analysis/cash-summary-report.md?ask=&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.