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
As per #56, more individualization on the accounting side is requested.
I think the best way, providing sufficient means for individualization, is perusing the Contract Number (Loan ID) as an (additional) accounting dimension to make sure every single accounting record is tagged and identifiable even amidst thousands and tens of thousands of records.
Even if it may not prove sufficient for every single use case, in most use cases or even almost all of them, the contract number is going to be a loan‘s main identifier over the whole course of a loan contract. Therefore this particular dimension should be configured out of the box, not left to admins to define and implement.
There may be an opt-out though for a couple of edge use cases. Imagine some company only administering a handful of employee loans and not wanting the whole CoA be littered with another, rarely used accounting dimension.
The text was updated successfully, but these errors were encountered:
I think this is the basic use case, so should be kind of a built-in accounting dimension just the way cost center is in frappe/erpnext. Might be taking on this tomorrow.
As per #56, more individualization on the accounting side is requested.
I think the best way, providing sufficient means for individualization, is perusing the Contract Number (Loan ID) as an (additional) accounting dimension to make sure every single accounting record is tagged and identifiable even amidst thousands and tens of thousands of records.
Even if it may not prove sufficient for every single use case, in most use cases or even almost all of them, the contract number is going to be a loan‘s main identifier over the whole course of a loan contract. Therefore this particular dimension should be configured out of the box, not left to admins to define and implement.
There may be an opt-out though for a couple of edge use cases. Imagine some company only administering a handful of employee loans and not wanting the whole CoA be littered with another, rarely used accounting dimension.
The text was updated successfully, but these errors were encountered: