At Finflux, we have taken a methodical approach to Moratorium.  We have invested in developing a comprehensive application module to apply Moratorium to existing loans.  The following checklist will help developers, product owners and the Line of Business leaders to track and ensure that the Moratorium rules are applied in a methodical way.

Contact us for more information on Finflux Moratorium support

S.No.

CheckList

Status / Comments

1

Ensure to have a Jira ID with the information

 

2

List of products for which Moratorium applies

 

3

Is this applicable to Web / Mobile applications?

 

4

What type of moratorium rule needs to be applied?

 

5

Does Moratorium have a configuration set up at the product level? Yes / No

 

If yes, get the option details to enable/disable?

 

6

Check the Moratorium setup required for Global configuration? Yes / No

 

If Yes, then check which option to be identified and enabled?

 

7

Check the Moratorium setup at other options in Admin? Yes / No.

 

If Yes, check the option details and its configuration setup.

 

8

Check the Impact Areas of this Moratorium by Dev & QA Observations?

 

9

Check from the DB perspective. Are any new tables (or) a new column in existing tables added for this Feature? Yes / No?

 

If yes, Get the Table names (or) Column name in the respective existing table names.

 

10

Is Moratorium enhanced through API ?. Yes / No.

 

If yes, get the API details for testing.

 

11

Check the compatibility of Moratorium on various LOB/Products/Geographies

 

If yes, check which client plan to enabled and plan to test the compatibility.

 

12

Does the Moratorium depend on Scheduler Job? Yes / No?

 

If Yes, Get the details of the Scheduler Job?

 

13

Check the detailed information is available in the Confluence? Yes / No.

 

If No, then check for the details and come up with queries.

 

14

Does this Moratorium apply to Bulk File Uploads?