> 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/november-2026/reports-queries/sale-registers/daily-sale-report-with-c.card-details.md).

# Daily Sale Report with C.Card Details

Logic ERP has corrected the totals of the **Daily Sale Report with C.Card Details**. Sale returns now reduce the date, branch and grand totals, quantity totals add up correctly for every payment type, and the **Grand Totals** option now decides whether the grand total is shown. The report also runs much faster for long date ranges and busy branches.

***

### **Step 1: Open the Report**

* Navigate to **Reports/Queries** and select **Sale Registers**.
* Open the **Daily Sale Report with C.Card Details**.

***

### **Step 2: Check the report options**

* Under **Configuration > Report Options**, tick the payment types to list: **CASH**, **CREDIT**, **CHEQUE**, **CREDIT CARD** and **GIFT VOUCH AMOUNT**.
* Under **Configuration > Totals**, tick the totals to show: **Sale Totals**, **Date Totals**, **Credit Card Account Wise Total**, **Branch Totals** and **Grand Totals**.
* **Grand Totals** must be ticked to see the **GRAND TOTAL** row at the end of the report. Before, the grand total was always shown, whether this option was ticked or not. If a saved configuration does not show the grand total any more, open it, tick **Grand Totals** and save.

***

### **What's corrected**

* **Sale returns:** a sale return is shown as a minus amount and a minus quantity on its row, and now reduces the **DATE TOTAL**, **BRANCH TOTAL** and **GRAND TOTAL**. Before, the return's amount was added to these totals instead of being taken off, and its quantity was shown as a plus on the row.
* Because of this, on days with sale returns, the date, branch and grand totals now come out **lower** than before. This is intended - the new figures are the correct ones.
* **Quantity totals:**
  * The quantity in the **CHEQUE TOTAL**, **CREDIT CARD TOTAL** and **GIFT TOTAL** now counts only that payment type. Before, it carried over the quantity of the payment types listed above it.
  * The **CASH TOTAL** now includes the quantity of the last cash bills of the day, and the **CREDIT TOTAL** now shows the credit quantity.
  * A bill paid in more than one way (for example part cash, part card) shows its quantity on one of its rows only - the cash row if there is one, otherwise credit, then cheque, then gift voucher, then card - and leaves it blank on its other payment rows. The payment-type totals, date totals and grand total now agree with each other.
* **Credit Card Account Wise Total:** a day's card payments are now grouped by card account (accounts in alphabetical order, bills in their usual order within each account), so each account gets one **CREDIT CARD ACCOUNT TOTAL** per day. Before, the rows stayed in bill order and the same account could get several part totals in a day.
* Gift voucher amounts are no longer added into the next **CREDIT CARD ACCOUNT TOTAL**.
* **Branch Totals off:** with **Branch Totals** unticked, each day now has one **DATE TOTAL** covering all branches. Before, the day was split into a separate group, with its own date total, every time the branch changed.
* **Branch Totals on:** the **BRANCH TOTAL** is now always shown at the end of a branch. Before, it could be missed when nothing was listed for that branch's last day.
* The report is much faster, especially for a month or more of bills or branches with many card payments.


---

# 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/november-2026/reports-queries/sale-registers/daily-sale-report-with-c.card-details.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.
