> 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/deprecation-schedule.md).

# Deprecation Schedule

Logic ERP has corrected the monthly depreciation in the **Deprecation Schedule** when **FAR Register As** is set to **Monthly**. Depreciation now stops when an asset's **useful days** are over, depreciation entries and sales are no longer shown as negative depreciation, a sale stops or reduces the depreciation of the asset from the sale date, and the month columns are now totalled.

***

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

* Navigate to **Reports/Queries** and select **Balance Sheet**.
* Open the **Deprecation Schedule**.
* In **Configuration > Report Options**, set **FAR Register As** to **Monthly**. The changes below apply only to this monthly view.

***

### **Step 2: Depreciation stops after the useful days**

* Each purchase of an asset is depreciated from its voucher date, by the same amount each day: the purchase value divided by the asset's **USEFULL DAYS**.
* Once the useful days are over, the depreciation stops. The months after that are left blank.
* **TOTAL DEP DURING THE YEAR** is now the total of the month columns on that line.

> **Example — a laptop with 60 useful days**
>
> A laptop is bought on 05/10/2026 for ₹30,000, with 60 useful days, so it is depreciated by ₹500 a day. The report shows October ₹13,500 (27 days), November ₹15,000 (30 days) and December ₹1,500 (3 days). January to March are blank, and **TOTAL DEP DURING THE YEAR** is ₹30,000. Earlier the report kept depreciating every month up to the end of the year and showed ₹89,000.

***

### **Step 3: Depreciation entries**

* A credit to an asset made by a journal voucher that debits a depreciation account is treated as a depreciation entry. It is no longer shown as negative depreciation, and it does not reduce the depreciation for the months.
* Depreciation entries passed by the **Trading and Profit and Loss A/c** closing entries are treated the same way.
* The depreciation accounts are the ones selected in **Depreciation Accounts** (Step 5) and the **Depreciation A/c** set in the **Trading and Profit and Loss A/c** under **Configuration > Report Options > Account Entry Setting**.

***

### **Step 4: Sale of an asset**

* Any other credit to an asset is treated as a sale. Its amount is shown in **SALE/ADJ DURING THE YEAR**, and it is not shown as negative depreciation.
* From the sale date, the depreciation of that asset is reduced in proportion to the value sold. The oldest value is taken first: the asset's value at the start of the first year shown, then its purchases in date order.
* When the whole asset is sold, its depreciation stops from the sale date.

> **Example — part of a purchase sold**
>
> Machines worth ₹46,000 are bought on 15/09/2025 with 1,095 useful days, so they are depreciated by about ₹42 a day. On 20/03/2026 machines worth ₹41,116 of that purchase are sold to a customer. From 20/03/2026 the purchase is depreciated by about ₹4.46 a day, for the part still held, and ₹41,116 is shown in **SALE/ADJ DURING THE YEAR** on the sale line.

***

### **Step 5: Depreciation Accounts**

* Go to **Configuration > Report Options > Depreciation Accounts** and tick it.
* The account selection opens, listing expense accounts. Select every account your company uses to book depreciation, then click **OK**.
* Select only depreciation accounts. An account such as profit or loss on sale of assets must not be selected, or sales will be treated as depreciation entries.
* If you click **OK** without selecting any account, all the listed accounts are taken.
* The **Depreciation A/c** set for the **Trading and Profit and Loss A/c** is always included, even when no account is selected here.

***

### **Step 6: Month totals**

* The month columns are now totalled on the **BRANCH Wise Totals**, extra account group totals and **GRAND Totals** lines.

***

### **Good to know**

* The value an asset carries from earlier years is not depreciated by itself. To see the depreciation of an asset bought in an earlier year, run the report from the financial year in which it was bought.
* When **Branches As** is set to **Branch Name**, the depreciation entries passed by the **Trading and Profit and Loss A/c** closing entries are not counted, because they are not made for a branch.
* Totals can be lower than before, because depreciation now stops after the useful days and depreciation entries and sales are no longer counted as depreciation. 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/deprecation-schedule.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.
