> 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/trading-account-balance-sheet-groups.md).

# Trading Account - Balance Sheet Groups

Logic ERP has added a **Branch Columns Show** option to the **Trading Account - Balance Sheet Groups**. With branch-wise columns on, you can now hide either the branch amount columns or the branch sub total columns. You no longer need to delete them by hand after exporting.

***

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

* Navigate to **Reports/Queries** and select **Balance Sheet**.
* Open the **Trading Account - Balance Sheet Groups**.

***

### **Step 2: Branch Columns Show**

* Go to **Configuration > Report Options-1 > Branch Columns Show**.
* The option works only when **Amount Columns As** is set to **Branch** or **Branch Groups**. When **Amount Columns As** is **None**, it cannot be changed and is saved as **Show All**.
* Choices:
  * **Show All**: each branch shows **EXPENSE AMOUNT**, **SUB TOTAL EXPENSE**, **INCOME AMOUNT** and **SUB TOTAL INCOME** (as before).
  * **Hide Amount Columns**: each branch shows only **SUB TOTAL EXPENSE** and **SUB TOTAL INCOME**.
  * **Hide Sub Total Columns**: each branch shows only **EXPENSE AMOUNT** and **INCOME AMOUNT**.
* With **Hide Amount Columns**, the branch figures for stock, gross profit, net profit and totals are hidden as well, because they appear in the amount columns.
* Hidden columns are also left out of print and Excel export.
* The company-wide columns do not change.
* Saved configurations stay on **Show All**, so existing reports look the same until you change this option.


---

# 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/trading-account-balance-sheet-groups.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.