V15: No clear way to stop asset depreciation from a specific date

ERPNext Asset Management
1

Hi everyone:

Use case: Our accountant has requested that depreciation on a specific asset stop as of a given date, with no further entries posted. The asset should remain active (not scrapped or sold).

Expected behavior: A straightforward workflow to freeze depreciation from a chosen date, preserving already-posted entries.

Actual behavior: There is no direct option to achieve this. The only path I found requires the following workaround as the asset has depreciation entries in already closed periods:

  1. Remove the Accounts Frozen Till Date in Accounts Settings

  2. Cancel the Period Closing Voucher for all the closed periods

  3. Post all unwanted unposted depreciation entries. Those exists since the date our accountant requested no more depreciations. (Posting them is required by ERPNext before the Depreciation Schedule can be cancelled)

  4. Cancel the Asset Depreciation Schedule

  5. Amend the Asset, reducing Total Number of Depreciations to match only the entries that should have been posted

  6. Cancel the unwanted Journal Entries created in step 3

  7. Recreate the Period Closing Voucher

This flow is fragile, counterintuitive, and risky in a production environment.

Question: Is there a supported, cleaner way to do this in v15? If not, could a “Stop Depreciation as of Date” option be considered, for example, a field on the Asset that halts schedule generation beyond that date without requiring cancellation of closed periods?

Thank you!

2

@MrMauro

Simply there is no solution to go back in time on a set date and redefine asset deprecation without revoking particular asset, depreciation schedule and deprecation jvs.

Those partially depreciated asset offer an option to Adjust Asset Value where particular asset value can be redefined but it works only with current and future dates. Setting backdates in this doctype does not impact what you are looking for infact.

The ease of recording any transaction in ERP also bring some compliance and reporting risk which developers and contributor need to account for as following;

  • Depreciation = accounting commitment

  • Once GL entries are posted, altering the schedule risks:

    • mismatched books

    • audit inconsistencies

    • tax reporting issues

The custom scripting may find a solution but will require some extensive code handling.

1 Like