|
Microfinance institutions usually work with various external parties, such as funders or investors. Using the data that is available in MifosX we would like to offer those stakeholders a seperate portal showing accurate and high-level information about the institution that would otherwise be reported manually by the institution. This information helps them in their decision making processes, but also enables them to assess the broader impact they are having with their funding.
Following high level information will be fetched from back end to show in front end UI application.
Loans | Description |
---|---|
Outstanding Loans (principal) | Outstanding principal of all outstanding loans of the institution |
Outstanding Loans (number) | Total number of all outstanding loans of the institution |
PAR 1 (%) | The outstanding principal of all outstanding loans of the institution that have at least one payment >1 day in arrears divided by the Outstanding Loans and shown as a % |
PAR 30 (%) | The outstanding principal of all outstanding loans of the institution that have at least one payment >30 day in arrears divided by the Outstanding Loans and shown as a % |
Savings | Definition |
Voluntary Savings (amount) | Sum of the balances of all voluntary savings accounts in the institution |
Compulsory Savings (amount) | Sum of the balances of all compulsory savings accounts in the institution |
Clients | Definition |
Total number of clients | The total number of clients that have at least one outstanding loan and/or an open position (savings, deposits) |
2. Back end user login for front end requests
3. Run report API changes for retrieve high level client details
4. Front End development to view user data
5. testing/documentation
High level schedule for implementation based on GSOC calendar
Link to background, wiki pages, other similar work, research related to the project.
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | Short identifier for the story | Describe the user and what they are trying to achieve | Must Have |
|
Include any mockups, diagrams or visual designs relating to these requirements.
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 |