> 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/customer-+-item-sale-analysis/branch-wise-sale-commission-report.md).

# Branch Wise Sale/Commission Report

Logic ERP has improved the **Branch Wise Sale/Commission Report**. Branch Group totals now show the cash, credit card, service tax, payable and total commission figures, commission is worked out correctly across slab ranges, MG totals are correct period-wise, and **COMMISSION(%)** now shows when the commission slab comes from the **Discount Range**. The report also runs faster.

***

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

* Navigate to **Reports/Queries** and select **Customer + Item Sale Analysis**.
* Open the **Branch Wise Sale/Commission Report**.

***

### **Step 2: Branch Group totals**

* When **Branch** is not ticked under **Report Consolidation** (the Branch Group layout), the total rows (**Branch Group Wise**, **Period**, **Grand Total** and the item totals) now show **CASH SALE**, **CREDIT CARD SALE**, **CASH+CREDIT CARD SALE**, **CREDIT CARD CHARGES**, **SERVICE TAX**, **CURRENT DATE CASH IN HAND**, **PAYABLE AMT**, **TOTAL COMMISSION (WITH DISCOUNT)** and **TOTAL COMMISSION (W/O DISCOUNT)**. Earlier these were blank on the total rows.
* Each Branch Group row now shows these figures for all the branches in the group. Earlier the cash sale, credit card sale, credit card charges, cash in hand and payable figures (and the service tax) were those of the last branch only. These figures will **rise** on Branch Group rows that have more than one branch, and **PAYABLE AMT** can **rise or fall**. This is intended.
* **PAYABLE AMT** now always agrees with the figures it is worked out from on the same row.

***

### **Step 3: Commission from the Discount Range**

* When **Pick Commission Slab From Master** is not ticked, the commission is worked out from the **Discount Range** entered in the report settings.
* **COMMISSION(%)** and **TOTAL COMMISSION(W/O DISCOUNT)** are now shown on this basis. Earlier they were blank.
* **DISCOUNT COMMISSION(%)** and **TOTAL COMMISSION(WITH DISCOUNT)** stay blank on this basis, because the Discount Range carries only one commission percentage.

***

### **What's corrected**

* With **Pick Commission Slab From Master** ticked, **TOTAL COMMISSION(WITH DISCOUNT)** and **TOTAL COMMISSION(W/O DISCOUNT)** are now worked out sale by sale, each at the commission percentage of its own slab range. Earlier, a report line whose sales fell in more than one slab range was worked out at a single percentage. These totals can **rise or fall** where a line spans several slab ranges. This is intended.
* When **Branch** is not ticked under **Report Consolidation** and **Pick Commission Slab From Master** is not ticked, **TOTAL COMMISSION** and **TDS CHARGES** are now shown correctly.
* **TDS CHARGES** on Branch Group rows now includes the service tax in its base, as it does on branch rows. **TDS CHARGES** will **rise** there for branches that carry service tax. This is intended.
* **MG PER MONTH** totals on the Branch Group layout are now counted once per branch for each period when **Period** is ticked under **Report Consolidation**, the same as on the Branch layout. These totals will **rise** where they were undercounted. This is intended.
* Selecting **TOTAL COMMISSION(WITH DISCOUNT)** or **TOTAL COMMISSION(W/O DISCOUNT)** without also selecting the matching amount column no longer shows the commission as zero.
* With **Pick Commission Slab From Master** ticked, the top range of a commission slab, which has no upper limit, is now picked up for every slab and not only the last one. Sales in that range now get their commission where earlier they got none, so commission will **rise**. This is intended.
* With the **Discount Range**, a discount that falls in the gap between two ranges (for example exactly at the upper limit of a range, or a fraction above it) no longer picks up the percentage of the last range. No commission is worked out for it. Commission on such sales will **fall**. This is intended.
* With **Pick Commission Slab From Master** ticked, two commission slab masters with the same name no longer mix their ranges.
* The **DISCOUNT(%)** columns are now filled on the **Extra Item Groups** subtotal rows.
* The report no longer stops with an error when none of the **Discount As** options is ticked, when **Slab As** is **Company + Group** with an **Item Group Level** above the first level, when **Slab As** is **Group** or **Company + Group** and **Item Group Level** is left blank, when **TDS Charges(%)** is left blank, or when **Slab Format As** is **Discount Amount** with large amounts.
* The report now runs faster, especially when it has many rows.


---

# 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/customer-+-item-sale-analysis/branch-wise-sale-commission-report.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.
