> 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-learning-hub-tutorials-and-best-practices/reports-queries/sale-registers/daily-sale-report-with-c.card-details/daily-sale-report-with-c.card-details-configuration.md).

# Daily Sale Report with C.Card Details - Configuration

The configuration of the [**Daily Sale Report with C.Card Details**](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/sale-registers/daily-sale-report-with-c.card-details.md) decides which payment types are listed and which totals are printed. You can keep several configurations and pick one when you run the report.

***

### **Step 1: Open the configuration**

* Navigate to **Reports/Queries\Sale Registers** and click on "Daily Sale Report with C.Card Details".
* Open the configuration, pick an existing configuration to change it, or type a new name to create one. The name is saved in capital letters.

***

### **Step 2: Report Options**

Tick the payment types to list. A payment type that is not ticked is not listed and is not counted in the date, branch or grand totals.

| Setting               | What it does                                                                                                               |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **CASH**              | Lists cash payments. Cash bills with numbers running one after another in the same series are shown on one row as a range. |
| **CREDIT**            | Lists credit bills, one row per bill.                                                                                      |
| **CHEQUE**            | Lists cheque payments with their cheque details.                                                                           |
| **CREDIT CARD**       | Lists card payments, one row per card.                                                                                     |
| **GIFT VOUCH AMOUNT** | Lists the amounts paid by gift voucher.                                                                                    |

None of these is ticked in a new configuration — tick at least one, or the report lists no bills.

***

### **Step 3: Totals**

| Setting                            | What it does                                                                                                                                                                             |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sale Totals**                    | Prints **CASH TOTAL**, **CREDIT TOTAL**, **CHEQUE TOTAL**, **CREDIT CARD TOTAL** and **GIFT TOTAL** after each payment type.                                                             |
| **Date Totals**                    | Prints a **DATE TOTAL** at the end of each day.                                                                                                                                          |
| **Credit Card Account Wise Total** | Groups a day's card rows by card account, in alphabetical order, and prints a **CREDIT CARD ACCOUNT TOTAL** after each account.                                                          |
| **Branch Totals**                  | Lists the report branch by branch and prints a **BRANCH TOTAL** at the end of each branch. Unticked, the rows run date by date across all the branches, with one **DATE TOTAL** per day. |
| **Grand Totals**                   | Prints a **GRAND TOTAL** at the end of the report.                                                                                                                                       |

None of these is ticked in a new configuration.

***

### **Step 4: Save**

* Click **Save**. The configuration is used the next time the report is run with it.

***

### **A good starting set**

> **Example — daily card reconciliation**
>
> Tick **CASH**, **CREDIT**, **CHEQUE**, **CREDIT CARD** and **GIFT VOUCH AMOUNT**, then **Sale Totals**, **Date Totals**, **Credit Card Account Wise Total** and **Grand Totals**, and save it as **DAILY COLLECTION**. Each day then shows the collection for every payment type, a total for each card account to match against the bank's settlement, and the day's total.


---

# 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-learning-hub-tutorials-and-best-practices/reports-queries/sale-registers/daily-sale-report-with-c.card-details/daily-sale-report-with-c.card-details-configuration.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.
