You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While viewing the General Ledger there is a flag called “ Include Default FB Entries”, enabling this flag add some depreciation entries that was created after upgrading to version 15 storing the FB on the GL Entry, The point is that the actual depreciation calculation appears while enabling it.
But this flag does not exist on the Profit and Loss Statement, and the calculation of the depreciation in P&L excludes the FB Entries, so the total expense is not faithfully represented in the financial statements. And this creates a discrepancy between both general ledger and P&L.
So my suggestion is to add the same flag on the P&L to make sure the FB Entries are included, and to avoid this discrepancy.
Module
accounts
Version
Frappe Version 15.17.1
ERPNext Version 15.16.2
Installation method
FrappeCloud
Relevant log output / Stack trace / Full Error Message.
No response
The text was updated successfully, but these errors were encountered:
Information about bug
While viewing the General Ledger there is a flag called “ Include Default FB Entries”, enabling this flag add some depreciation entries that was created after upgrading to version 15 storing the FB on the GL Entry,
The point is that the actual depreciation calculation appears while enabling it.
But this flag does not exist on the Profit and Loss Statement, and the calculation of the depreciation in P&L excludes the FB Entries, so the total expense is not faithfully represented in the financial statements. And this creates a discrepancy between both general ledger and P&L.
So my suggestion is to add the same flag on the P&L to make sure the FB Entries are included, and to avoid this discrepancy.
Module
accounts
Version
Frappe Version 15.17.1
ERPNext Version 15.16.2
Installation method
FrappeCloud
Relevant log output / Stack trace / Full Error Message.
No response
The text was updated successfully, but these errors were encountered: