NOTICE: Out of Scope for v1.1 release

Feature OverviewMoratorium is a legally authorized period of delay in the performance of a legal obligation or the payment of a debt. A moratorium could be granted in case

• The client gets sick or her family member dies.
• The client's home or business has been afflicted by a calamity such as a storm, flood, landslide, or fire.

The moratorium can be granted to a client or all the clients of an entire center or group and can be effective for a given date range. During the moratorium, the client is not obligated to pay any of her loans, and savings dues. The period that a client is in moratorium is tracked to reflect that no amount is due to the client at the given moratorium period.

UI screens have been completed for the Moratorium feature. Download the most recently dated folder: https://mifos.dev.java.net/source/browse/mifos/documents/ui-workspace/

Feature Summary

User Flow: Configuring moratorium

• From Admin section, under "Organizational Preferences", user clicks "Configure moratorium".
• User is taken to the "Configure moratorium-Select" page where he can choose to configure a moratorium for either, the HO, a regional office , a branch or a client/group/center.
• If the user chooses to configure a moratorium for a HO/regional/branch he is taken to a page where he can choose from a list of regional offices or branches.
• Label to select configuration for HO/regional/branch will be dynamic. * E.g.: If the MFI does not have a configuration for regional offices, then the option would be HO/branch
• Note: These branches will be displayed according to the user scope of the logged in user. * E.g.: If the logged in user is in an Area Office then the list of branches under the Area Office will be displayed. If the logged in user belongs to a branch then only that branch will be shown.
• If the user chooses to configure a moratorium for a client/group/center he is taken to a page where he can search for the same on the basis of the name.
• Once the user has chosen either the branch or the client /group/center he proceeds to the page where he can enter the moratorium information. * User enters the start date and end date of the moratorium. He can also enter notes to state the reason for the moratorium. The size of the notes would be limited to 200 characters
• User clicks on Preview and is taken to the preview page. On this page, the user has the option to edit the moratorium information.
• User enters "submit" and is taken back to the admin page.
• System performs the following validations/actions: _ The End Date has to be greater than or equal the Start date. _ The Start Date can be set to a date earlier than the System Date as long as the Start Date is not 30 days earlier than the System Date. * A new moratorium period for the same client or center should not overlap with an existing moratorium period.
  • This calculation should be based off the effective moratorium period. The effective moratorium period should be the Start Date and End Date or Start Date or Lift Date, whichever is shorter. E.g., if the Moratorium is originally set for Nov 1 to 30 and the moratorium is lifted Nov 15, the effective moratorium period is Nov 1 to 15. Thus, the user should be able to add another moratorium for the same client or center starting Nov 16.
  • This validation will only be done between client vs. client moratorium and center vs. center moratorium. I.e., there will no validation in the overlap between center vs. client moratorium.

User Flow: View moratoriums

• From Admin section, under "Organizational Preferences", user clicks "View Moratoriums".
• User is taken to page where he can view the list of branches, clients, groups and centers, which are currently in moratorium.
• The following details will be displayed in a table structure _ Branch/Center/Group/Client Name _ Branch/Center/Group/Client Name _ Start Date _ End Date _ Created By _ Date Created _ Lift Date _ Lifted By

Additional Information

• When a branch is in moratorium, all active centers, groups and clients within that branch will be in moratorium.
• When a center is in moratorium, all active groups or clients within that center will be in moratorium.
• When a group is in moratorium, all active clients within that group will be in moratorium.
• When a client is in moratorium, all of the client's active accounts will be in moratorium.
• When a loan account is in moratorium, the following should be reflected in the loan account's schedule: _ 0 principal and interest due during repayments within the moratorium period. _ An extension of the loan maturity as the effect of the Moratorium.
• There will be no savings due for the client for the given moratorium period.

Open Issues

• Can a moratorium be edited.

Suggestions

• We could have a pre-defined list of reasons, while applying a moratorium. These could be configuration items that could be inserted into the database. E.g: Earthquakes, Tsumani, Sickness, Death of family member.