User Driven Nomenclature Customization facility for object Numbers #341
EFFICIENTCORPORATES
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have multiple types of Numbers / alias creation in the accounting system.
It is a best practice to have a rule defined for each type of number , so that the validation checks can be maintained.
For e/g. An Account code should always be 10 digit long.
Account code starting with 1* reflects equities and Reserves
Account code starting with 2* reflects liabilities
Account code starting with 3* reflects assets
Account code starting with 4* reflects Incomes
Account code starting with 5* reflects expenses
Similarly, a JV number should be 10 digit long .
JV for Bill booking should start with 3*
JV for Sales Invoice booking should start with 4*
JV for Bank related booking should start with 5*
Other Misc JV should be 8*
Also, Rules of Nomenclature like, Vendor Code should have a prefix of "V" or "S"
Customer code should have a prefix of "C"
Assets code should have a prefix of "C"
Invoices should have prefix as "AB/2022/"
PO number to be 8 digit long starting from 2*
SO number to be 8 digit long starting from 2*
Similarly for all the other objects like Items, materials , Banking GLs
All these should be customizable by the admin of the entity under a setting tab . (However, as a best practice ,once set, these should not be allowed to change in future)
All reactions