-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Make Depreciation Entry posting more flexible #28421
Merged
nextchamp-saqib
merged 11 commits into
frappe:develop
from
GangaManoj:depr-expense-account
Dec 6, 2021
Merged
feat: Make Depreciation Entry posting more flexible #28421
nextchamp-saqib
merged 11 commits into
frappe:develop
from
GangaManoj:depr-expense-account
Dec 6, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GangaManoj
requested review from
deepeshgarg007 and
nextchamp-saqib
as code owners
November 16, 2021 23:49
Codecov Report
@@ Coverage Diff @@
## develop #28421 +/- ##
===========================================
- Coverage 55.34% 55.19% -0.15%
===========================================
Files 1119 1121 +2
Lines 66664 66760 +96
===========================================
- Hits 36897 36851 -46
- Misses 29767 29909 +142
|
…t is an Expense Account
…t is an Income Account
nextchamp-saqib
approved these changes
Dec 6, 2021
@Mergifyio backport version-13-hotfix |
✅ Backports have been created
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In order to post Depreciation Entries, you need to set 2 accounts:
However, this poses a problem for some customers in the European region. They prefer to use the same root node for both Income and Expense Accounts, which means that they're unable to set Depreciation Expense Accounts(which need to have Root Type = Expense). Consequently, they're unable to post Depreciation Entries(manually or otherwise).
Fix
To Do:
Testing Info
Case 1:
Create a new Asset Category
Set an Expense Account as the Depreciation Expense Account
Create a depreciable Asset belonging to that Asset Category, with Depreciation Starting Date set as a past date
After submission of the Asset doc, expand the Depreciation Schedule row whose Schedule Date has already passed and click on the Make Depreciation Entry button
Check the Journal Entry thus created and confirm that the Depreciation Expense Account was debited
Case 2:
no-docs