...
New accounts can be either "header" or "detail" accounts to make things simpler for a user. "Header" accounts would be used purely for grouping together
related accounts etc, an organization would not log journal entries against the same (Journal entry screens would not list "Header" accounts)
I would be interested in hearing what COA nirantara and GK accountants use (or any other MFI in community). On document pages 23, 24 is content about the 'classification of transactions' through chart of accounts and a sample chart of accounts for MFIs. How does nirantara and gk COA differ and why would be good to know.
...
| Column Name | Data Type | Description |
|---|---|---|
| id | int | |
| gl_code | varchar(45) | |
| category | varchar(45) | Whether the account falls under “asset”, “income”, “expense”, “liability” or “equity” |
| parent_Id | int | References “id” of table “m_acc_coa”. For enabling a hierarchical COA |
| name | varchar(45) | |
| type | varchar(45) | Either “header” or “detail” account. Header accounts will not have transactions logged against them |
| description | varchar(500) | |
| disabled | Boolean | A Flag indicating if the account has been disabled (not deleted). No more manual entries can be posted against a disabled Account |
7.2 Modifications to Loan Product (“m_product_loan”)
...