Target release 15.06 Epic Document status Document owner Dayna Harp Designer   Developers   QA Lead tester

Overview

• There are very few differences between a credit union operation and a bank operation.  The primary difference is the ownership structure. An individual or a group of individuals owns a bank.  The members – or account holders - own a credit union.

• Products are nearly identical – the names only are different.  Credit union products can be set up in Mifos X as it is today and description of the functionality to be achieved.

   

• The difference in setting up a credit union/SACCO account is the membership fee.

Background and strategic fit

Credit unions/SACCOs and similarly structured financial institutions charge a membership fee.  This fee must be collected that the time of application - therefore it is a client-level fee.  This fee must have the ability to refund back to the client based on the organization's policies.  

The fit in workflow is:

• Create New Client.
• Take Photo, upload
• Upload Signature
• Enter ID
• Upload Membership Application
• Collect Membership Fee. 
  • Entry = Cash received,
  • Transaction Type = Membership Fee
  • Posts to General Ledger Income Account – Fee Income
  • Posts to teller cash drawer as cash received 
  • Notification forwarded to supervisor or membership committee for review and decision.
  • If declined, membership fee refunded (organization dependent – some may keep fee)
  • Client account is closed with notes entered for reason for denial.
  • If approved, savings account is opened 

Requirements/User Stories

Business Rules

Any preconditions before a client can use the new functionality

Any rules to be applied for a client or user when using this functionality

Attributes

List of attributes to be captured for the new functionality

Security and Permissions

List of security areas to be considered and permissions to be added/considered for a user/role to have access to this functionality 

Mifos Functionality Enhancements

New Screens

List of new screens required

Changes to Existing Screens

List of existing screens that need any kind of changes

Changes/Enhancements to Batch Jobs

Functional changes to Batch jobs that may be needed - along with suggested frequency at which it should be run for various scenarios

Changes/Enhancements to Accounting Entries

With sample accounting entries with dates

User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Exception Handling

List of error scenarios and the action - if message is to be displayed, then text of the message.

Reporting

List of changes/enhancements/new reports to support this functionality

APIs

From a functional perspective, list of new APIs needed.

From a functional perspective, list of existing APIs that need changes.

Notes

Points to be handled during upgrades

Any reference data that needs to be prepopulated or defaulted for clients/users

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Out of Scope

• List the features discussed which are out of scope or might be revisited in a later release.