> 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/january-2026/reports/branch-filter-in-issue-receipt-register-report.md).

# Branch Filter in Issue/Receipt Register Report

Logic ERP has introduced a new update to improve branch-wise reporting in the Issue/Receipt Register.\
With this update, a Branch filter has been added to the report, allowing users to easily view branch-wise Issue and Receipt entries.

Additionally, when generating the report for all branches, a Branch Name column is now available, making it easier to identify which entries belong to which branch and improving overall report clarity.

***

### **Viewing Branch-wise Issue and Receipt Entries in Report**

* Open the report.
* On the **right side**, you will see the **Filter Tree**.
* In the Filter Tree, a new option named **“Branch Name”** is now available.
* Select the required **Branch Name** from this filter.
* Apply the filter and **generate the report** to view branch-wise data.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FqeqpIWHY1IYRFIG85NlQ%2FFilter%20Tree.png?alt=media&amp;token=bd239695-5074-42cf-95c2-c2bb9c658bab" alt=""><figcaption></figcaption></figure>


---

# 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/january-2026/reports/branch-filter-in-issue-receipt-register-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.