> 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/balance-sheet/balance-sheet-branch-wise-vertical.md).

# Balance Sheet - Branch Wise(Vertical)

Logic ERP has corrected the **Balance Sheet - Branch Wise(Vertical)** for financial-year columns, branch-wise closing stock values, the gross profit ratio and the current-branch option, and it now shows the difference when the totals do not agree.

***

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

* Navigate to **Reports/Queries** and select **Balance Sheet**.
* Open the **Balance Sheet - Branch Wise(Vertical)**.

***

### **Step 2: Financial-year columns**

* With **Column As** set to **Financial Year** and **Always Pick Opening Stock Value from Stock Transactions** ticked, the current year's opening stock is now valued as at the last day of the previous year. Earlier it also included the stock movements of the first day of the year.
* With that option ticked, the opening stock account is now left out of the current year's column, so the opening stock is counted once. Earlier this depended on **Branch Group H Level** instead, so the opening stock could be counted twice or left out.

***

### **Step 3: Branch-wise closing stock values**

* With **Column As** set to **Financial Year**, and both **Always Pick Opening Stock Value from Stock Transactions** and **Pick CS Value through Branch + Date wise Closing Stock Values input** ticked, the current year's opening stock now takes the latest value entered on or before the last day of the previous year. Earlier it took the latest value up to the **To** date, so the opening and the closing stock were the same.

***

### **Step 4: Gross profit ratio**

* When the closing stock is worked out from the gross profit ratio, it now includes the opening stock. For a period that starts after the first day of the year, the ratio is now applied to the sales of that period only.

***

### **Step 5: Show Data For Current Branch Only**

* The option is now read correctly for the account balances, for the branch and branch group columns, and when you open the profit and loss details by double-clicking.

***

### **Step 6: DIFFERENCE row**

* When a column's assets and liabilities totals do not agree, a **DIFFERENCE (Assets - Liabilities)** row now appears after **Assets Total**, showing the gap for that column. A minus means the liabilities are higher. The row is not added into either total.

***

### **Good to know**

* Sheets with financial-year columns can show a different current-year opening stock and profit, because the first day's stock movements are no longer included. This is intended.

**Available on:** Desktop · Web


---

# 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/balance-sheet/balance-sheet-branch-wise-vertical.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.
