| Target release | 16.03.RELEASE |
|---|---|
| Epic | MifosX-2182 |
| Document status | |
| Document owner | Ippez Robert |
| Designer | Lead designer |
| Developers | Lead developer |
| QA | Subramanya |
|
Account to Journal Entries Posting and Vice versa
There are times when a client will need to make payments to MFI/SACCO or MFI/SACCO needs to make payments to a client/group account. Mifos X at the moment doesn't support GL to Client account entry and vice versa.
This feature will extend the possibility to have two way account entries between GL Accounts and Client/Group Accounts. It will cover both Loans and Savings Accounts and will extend to both Individual Client Account and Group Accounts.
Strategic vision of The Mifos Initiative to support two-way account entries
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Create Savings Account to GL Entry | As an accountant, i would like to be able to make a transfer from a Savings Account to a General Ledger Account | Must Have | |
| Create Loan Account to GL Entry | As an accountant, i would like to be able to make a transfer from a Loan Account to a General Ledger Account | Must Have | ||
| Create GL Entry to Savings Account Entry | As an accountant, i would like to be able to make transfer from a General Ledger Account (e.g Cash at Hand) to Client's Savings Account | Must Have | ||
| Create GL Entry to Loan Account Entry | As an accountant, i would like to be able to make transfer from a General Ledger Account (e.g Cash at Hand) to Client's Loans Account | Must Have |
| Attribute | Description | Notes |
|---|---|---|
List of security areas to be considered and permissions to be added/considered for a user/role to have access to this functionality
List of existing screens that need any kind of changes
Functional changes to Batch jobs that may be needed - along with suggested frequency at which it should be run for various scenarios
With sample accounting entries with dates
Include any mockups, diagrams or visual designs relating to these requirements.
List of error scenarios and the action - if message is to be displayed, then text of the message.
List of changes/enhancements/new reports to support this functionality
From a functional perspective, list of new APIs needed.
From a functional perspective, list of existing APIs that need changes.
Points to be handled during upgrades
Any reference data that needs to be prepopulated or defaulted for clients/users
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |