> 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/agent-wise-reports/branch-+-agent-+-date-wise-target-vs-achievement-analysis.md).

# Branch + Agent + Date Wise Target Vs Achievement Analysis

Logic ERP has improved the **Branch + Agent + Date Wise Target Vs Achievement Analysis**. Any item group level can now be chosen in **Item Group H - Level** and saved, including levels after the ninth. The report can now also be used as a **salesman-wise sale report**, with each salesman listed under their agent group, and agent group, branch and grand totals when those totals are ticked. The report's configuration screen has also been updated.

***

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

* Navigate to **Reports/Queries** and select **Agent Wise Reports**.
* Open the **Branch + Agent + Date Wise Target Vs Achievement Analysis**.

***

### **Step 2: Item Group H - Level**

* Go to **Configuration > Report Options > Item Group H - Level**.
* Choose the item group level the targets are matched on. Every item group level defined in the company can be chosen.
* Configurations saved earlier keep the level they had.

***

### **Step 3: Achievement / Incentive Slabs**

* Go to **Configuration > Report Options > Achievement / Incentive Slabs**.
* Enter the **Achievement %** and the **Incentive %** earned at each level of achievement.
* An achievement percentage cannot be left blank or entered twice. If it is, the configuration is not saved and a message is shown. For a percentage entered twice, the message names it.

***

### **Step 4: Agent Wise Rows Under Agent Group**

* Go to **Configuration > Report Options > Agent Wise Rows Under Agent Group** and tick it.
* Tick **Agent Name** and **Agent Group** under **Report Consolidation**, set **Agent Group Level** to **None**, and keep **Achievement As** set to **Sale**.
* Each salesman gets their own row under their agent group, sorted by group and then by salesman. Tick **Agent Group** under **Report Totals** to print **Agent Group Wise Totals** after each group.
* Salesmen not placed under any agent group are listed together under the name of the agent they are linked to in the agent master — usually **NIL** — in its place among the groups, with their own total.
* Configurations saved earlier have this option unticked and work as before.

To learn how to set up a salesman-wise sale report with agent groups, [**Click Here**](/logic-erp-learning-hub-tutorials-and-best-practices/reports-queries/agent-wise-reports/branch-+-agent-+-date-wise-target-vs-achievement-analysis.md).

***

### **Step 5: Totals**

* The totals of the inner levels are now printed before the total around them — for example each agent group's total before the branch total.
* An inner total now also closes when a level around it changes — for example an agent's total when the branch changes — so it no longer runs on into the next branch.
* A **Branch Wise Totals** row now shows the branch name, and an **Agent Group Wise Totals** row shows the agent group's name (not when **Achievement As** is **Sale Collection** with **Month Wise**).

***

### **What's corrected**

* A configuration with an item group level after the ninth chosen in **Item Group H - Level** can now be saved. Earlier such a configuration could not be saved at all.
* With **Agent Group** ticked, **Agent Group Level** set to **Level-1** to **Level-4** and **Achievement As** set to **Sale**, each row is one agent group. The **AGENT NAME** column on these rows showed one of the group's agents; it is now blank, and **Agent Name** totals are no longer printed for them. **TOTAL BILLS** now counts the bills of the whole group instead of one agent's. A target set for an agent group is now counted once; earlier, with **Agent Name** not ticked, it was multiplied by the number of agents in the group.
* With an **Agent Group Level** chosen but **Agent Group** not ticked (and **Agent Name** ticked), agents appearing next to each other were added together into one row. Each agent now has their own row.
* **TOTAL BILLS**, **ABV** and **BASKET** (shown when **Achievement As** is **Sale**) now count only the bills behind the rows shown: they follow the **Branch**, **Agent**, **Company** and **Extra Item Groups** selections, **Show Data For Current Branch Only**, the **Item Wise** agent, the **Item Group H - Level** and the agent groups. **TOTAL BILLS** is now also shown on the **Target Date** and **Agent Group** totals. **TOTAL BILLS can now be lower than before** — this is intended: bills outside the selections, or credited to another agent, are no longer counted. On agent group rows it is usually higher, as it now covers the whole group.
* With **Sale Report On** set to **Sale + Sale Return (Net)** and **Include Free/Repl/Sample In Total Quantity** ticked, the free, replacement and sample quantity of sales is now added to **TOTAL QUANITY**. Earlier that quantity was deducted for returns but not added for sales, so the quantity can now be higher than before.
* With **Target Date As** set to **Month Wise**, the months are now listed in date order — April first in a financial year — instead of by month number.
* With **Target Date** ticked and **Date Wise** (and **Achievement As** set to **Sale**), the incentive is now worked out for each agent separately in each branch. Earlier an agent working in several branches had it worked out on the combined sales of all branches.
* **Min Ach (%) for Incentive** and **UD Net Amount-2** have been removed from the configuration screen; they had no effect on the report.


---

# 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/agent-wise-reports/branch-+-agent-+-date-wise-target-vs-achievement-analysis.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.
