Date: Fri, 29 Mar 2024 09:20:12 +0000 (UTC) Message-ID: <1311916276.3.1711704012716@8e326fbc3eae> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_16652997.1711704012715" ------=_Part_2_16652997.1711704012715 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The following topics are for system administrators and Mifos specialists= configuring Mifos who are deploying Mifos.
The topics assume that you have installed Mifos and configured its third= -party applications as described in Installing Mifos,= and that you are ready to configure the administrative settings in Mifos. = After you configure these settings, your Mifos deployment will be ready for= you or someone else to create loan and savings products, add new clients a= nd groups, open accounts for clients and groups, and configure reporting.= p>
The administrative configuration process involves two groups of settings= , which should be configured at two different times:
Note for version 1.0 users: Changes since Mifos version= 1.0 include moving install-time settings out= of the database and into plain-text files. If you are using Mifos vers= ion 1.0, see Configuring Mifos version 1.0.
This section describes the install-time settings in Mifos, or those that= can only be configured when Mifos is not running. It also describes instal= l-time settings whose values can only be changed to non-default values once= , before you run Mifos for the first time.
When Mifos runs for the first time, it writes values to its database. Al= though many of these values can be changed later, some cannot. Specifically= , the values from the Chart of Accounts can only be written to the database= once. Similarly, TRAPDOOR properties in the application configuration file= can only be assigned non-default values once, before you run Mifos for the= first time. After that point, a TRAPDOOR property value can only be change= d to its default setting.
The Chart of Accounts used by Mifos can be customized to exclude certain= General Ledger (GL) accounts or use a different hierarchy of accounts. Not= e that you have only one opportunity to make these customizations, before y= ou run Mifos for the first time.
To customize the Chart of Accounts:
Note: Once Mifos is deployed, you won't be able to dele= te GL accounts or change the account hierarchy. See the bulleted lists belo= w for more information.
After Mifos is deployed, you can only make the following changes to your= GL accounts:
You cannot make the following GL account changes after Mifos is deployed= :
Unlike the Chart of Accounts, financial action mappings can be customize= d any time Mifos is not running.
GL accounts are used in conjunction with particular actions. For example= , when principal is added to a new loan account (a credit), Mifos choses a = GL account based on a mapping. The default m= appings that Mifos uses are stored in applicationCont= ext.xml, a file that ships with Mifos. For Mifos to function corre= ctly, all actions must be mapped to an existing GL account.
To customize the financial action mappings:
Example
Use the following as a starting point for creating your own mifosBeanConfig.custom.xml:
=09=09<?xml version=3D"1.0" encoding=3D"UTF= -8"?> <beans xmlns=3D"http://www.springframework.org/schema/beans" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=3D"http://www.springframework.org/schema/beans " title=3D"http://www.s= pringframework.org/schema/beans/spring-beans-2.0.xsd">">http://www.sp= ringframework.org/schema/beans/spring-beans-2.0.xsd"> <bean id =3D "financialRules" class=3D"org.mifos.accounts.financial.util.helpers.FinancialRules" abstract=3D"false" factory-method=3D"getInstance"> <property name=3D"actionToDebitAccount"> <map> <entry key=3D"PRINCIPALPOSTING" value=3D"11201"/> <entry key=3D"INTERESTPOSTING" value=3D"11201"/> <entry key=3D"FEEPOSTING" value=3D"11201"/> <entry key=3D"PENALTYPOSTING" value=3D"11200"/> <entry key=3D"ROUNDING" value=3D"31401"/> <entry key=3D"MANDATORYDEPOSIT" value=3D"11201"/> <entry key=3D"VOLUNTARYDEPOSIT" value=3D"11201"/> <entry key=3D"MANDATORYWITHDRAWAL" value=3D"24000"/> <entry key=3D"VOLUNTARYWITHDRAWAL" value=3D"23000"/> <entry key=3D"SAVINGS_INTERESTPOSTING" value=3D"41000"/&g= t; <entry key=3D"DISBURSAL" value=3D"13101"/> <entry key=3D"MISCFEEPOSTING" value=3D"11201"/> <entry key=3D"MISCPENALTYPOSTING" value=3D"11201"/> <entry key=3D"CUSTOMERACCOUNTMISCFEESPOSTING" value=3D"11= 201"/> <entry key=3D"MANDATORYDEPOSIT_ADJUSTMENT" value=3D"24000= "/> <entry key=3D"VOLUNTARYDEPOSIT_ADJUSTMENT" value=3D"23000= "/> <entry key=3D"MANDATORYWITHDRAWAL_ADJUSTMENT" value=3D"11= 201"/> <entry key=3D"VOLUNTARYWITHDRAWAL_ADJUSTMENT" value=3D"11= 201"/> <entry key=3D"WRITEOFF" value=3D"13201"/> <entry key=3D"RESCHEDULE" value=3D"11201"/> </map> </property> <property name=3D"actionToCreditAccount"> <map> <entry key=3D"PRINCIPALPOSTING" value=3D"13100"/> <entry key=3D"INTERESTPOSTING" value=3D"31100"/> <entry key=3D"FEEPOSTING" value=3D"31300"/> <entry key=3D"PENALTYPOSTING" value=3D"31102"/> <entry key=3D"ROUNDING" value=3D"31401"/> <entry key=3D"MANDATORYDEPOSIT" value=3D"24000"/> <entry key=3D"VOLUNTARYDEPOSIT" value=3D"23000"/> <entry key=3D"MANDATORYWITHDRAWAL" value=3D"11201"/> <entry key=3D"VOLUNTARYWITHDRAWAL" value=3D"11201"/> <entry key=3D"SAVINGS_INTERESTPOSTING" value=3D"24100"/&g= t; <entry key=3D"DISBURSAL" value=3D"11201"/> <entry key=3D"MISCFEEPOSTING" value=3D"31301"/> <entry key=3D"MISCPENALTYPOSTING" value=3D"31102"/> <entry key=3D"CUSTOMERACCOUNTMISCFEESPOSTING" value=3D"31= 301"/> <entry key=3D"MANDATORYDEPOSIT_ADJUSTMENT" value=3D"11201= "/>=20 <entry key=3D"VOLUNTARYDEPOSIT_ADJUSTMENT" value=3D"11201= "/> <entry key=3D"MANDATORYWITHDRAWAL_ADJUSTMENT" value=3D"24= 000"/> <entry key=3D"VOLUNTARYWITHDRAWAL_ADJUSTMENT" value=3D"23= 000"/> <entry key=3D"WRITEOFF" value=3D"13101"/> <entry key=3D"RESCHEDULE" value=3D"13101"/> </map> </property> </bean> </beans>
You may notice that other unrelated sections from applicati= onContext.xml have been omitted. This is intentional. The cod= e that parses this XML configuration file allows for partial changes, and o= nly those settings specific to financial action mappings inmifosBea= nConfig.custom.xml can be customized.
Action names are actually constants in the FinancialActionConstants = ;enum class= . All actions must be mapped (except, currently, PENALTYPOSTING and REVERSA= L_ADJUSTMENT) because Mifos assumes they are. For example, Mifos expects th= e mapping to contain a ROUNDING account. If the mapping doesn't exist, the = application may crash or corrupt data because it cannot find an account wit= h which to resolve rounded amounts.
Values may be changed, but they must point to GL account codes as specif= ied in the Chart of Accounts.
Mifos ships with a default application configuration file (appli= cationConfiguration.default.properties) that controls many aspects= of how Mifos is set up, including which currency and locale it uses, its a= ccounting rules, and many other important settings. You should never edit t= his default configuration file directly. Instead, use the file applicationConfiguration.custom.properties to override the v= alues you want to change:
To use the custom application configuration file:
The following settings in your applicationConfiguration.cus= tom.properties file control locale in Mifos.
In Mifos, settings for country and language work together to create a lo= cale-specific user interface. Choose the language you want first, then use = the CountryCode value that must be paired with t= hat language.
Use the following table to determine which LanguageCodes and CountryCodes must be paired with= one another:
For locales using this language... | use this CountryCode | and this LanguageCode |
---|---|---|
Spanish | ES | ES |
French | FR | FR |
English | GB | EN |
Example: Setting Localization.LanguageCode= to FR and Localizati= on.CountryCode to FR cause Mifos t= o display a French user interface.
In Mifos, settings for country and language work together to create a lo= cale-specific user interface. To get the language you want, it's possible t= hat you will have to use a country code that doesn't reflect where Mifos wi= ll be installed.
Use the following table to determine which LanguageCodes and CountryCode= s must be paired with one another:
For locales using this language... | use this CountryCode | and this LanguageCode |
---|---|---|
Spanish | ES | ES |
French | FR | FR |
English | GB | EN |
Example: Setting Localization.LanguageCode= to FR and Localizati= on.CountryCode to FR cause Mifos t= o display a French user interface.
If you are using a language that requires right-to-left, this setting ca= n be used to set the direction of the text. By default, this should b= e set to auto. If your locale is set up correctly, the direction shou= ld be automatically set and this direction does not need to be changed.
The accounting settings in applicationConfiguration.custom.= properties tell Mifos which currency you want to use and prov= ide information it needs to calculate repayment schedules, including how ma= ny decimal places of precision should be used, and how repayments should be= rounded and adjusted.
The currency that Mifos uses.
This setting causes Mifos to use currency set internally, in its calcula= tions and database. Externally, you will see no effect. The user interface = does not display currency symbols ($, =C2=A3, etc.). This is a known issue. This sets the default= currency in Mifos. All accounting rules without a currency code on t= he property applies to the default currency.
Example: AccountingRules.Curre= ncyCode=3DINR causes Mifos to use the Indian rupee as the curre= ncy.
The number of days per year that should be used by Mifos in its interest= calculations.
This setting does not apply to meeting scheduling. The meeting calendar = always has 365 days. This setting also doesn't apply to fees and penalties = calculation and repayment schedule generation. Because of its dependencies,= once you configure this setting, you should not change it. For example, in= the case of a moratorium, the loan schedule is recalculated, and changing = the number of interest-bearing days in a year could change the calculation = results.
Example: AccountingRules.Numbe= rOfInterestDays=3D365 causes Mifos to use 365 days in its inter= est calculations.
The number of digits after the decimal that Mifos will carry for the cur= rency.
This setting interacts with the rounding mode settings: Rounding mode for currency, Rounding mode for r= epayments, and Rounding mode for final payment<= /a>.
While most MFIs use a value that represents the currency's finest level = of precision, some do not. For example, the Tunisian dinar's smallest denom= ination is the milem, which is 1/1000 of a dinar. Instead of setting <= strong>AccountingRules.DigitsAfterDecimal to 3= strong>, which would represent the dinar's finest level of precision, a Tun= isian MFI might set AccountingRules.DigitsAfterDecimal to 2 (1/100 of a dinar).
Example: If AccountingRules.Cu= rrencyCode=3DUSD and AccountingRules.D= igitsAfterDecimal=3D2, the number of digits Mifos will carry represe= nts the currency's finest level of precision (1/100 of a dollar, or a penny= ).
The number of digits after the decimal that Mifos will carry for interes= t.
If you want to set a different digits after decimal that Mifos will carr= y for interest in an additional currency, set another property with the cur= rency code in the property name. For example, if Mifos has been confi= gured with an additional currency LBP, to set a different digits after deci= mal for interest that Mifos will cary for LBP, use the property name Accoun= tingRules.DigitsAfterDecimalForInterest.LBP.
The maximum allowable interest rate.
Unless you're advised otherwise by a Mifos specialist, use the default v= alue for this setting (999).
Example: AccountingRules.MaxIn= terest=3D999 means that the interest rate Mifos uses for its ca= lculations can be as high as 999%.
The minimum allowable interest rate.
Unless you're advised otherwise by a Mifos specialist, use the default v= alue for this setting (0).
Example: AccountingRules.MinIn= terest=3D0 means that the interest rate Mifos uses for its calc= ulations can be as low as 0%.
The minimum allowable cash flow threshold
Example: AccountingRules.MinCa= shFlowThreshold=3D0 means that the minimum allowed cash flow th= reshold for a loan product is 0.
The maximum allowable cash flow threshold
Example: AccountingRules.MaxCashFlowThreshold=3D99 means that the = maximum allowed cash flow threshold for a loan product is 99.
Example: AccountingRules.MaxRepaymentCapacity=3D1000 me= ans that the maximum allowed repayment capacity for a loan product is 1000.=
Example: AccountingRules.MinIndebtednessRatio=3D0 means= that the mimimum indebtedness ratio for a loan product is 0.
How Mifos rounds currency amounts.
This setting interacts with Number of digits afte= r decimal.
Example: Assuming that Number of= digits after decimal is set to 1, a value o= f...
How Mifos rounds repayment amounts when it calculates repayment schedule= s except for the last scheduled repayment.
This setting interacts with Number of digits afte= r decimal.
Example: Assuming that Number of= digits after decimal is set to 2, a value o= f...
The decimal place repayments are rounded to when Mifos calculates the lo= an repayment schedule.
The precision you use must be equal to or less precise than what you spe= cify for Number of digits after decimal. This se= tting does not affect the last repayment use R= ounding precision for final payment instead.
Example: If the currency is...
How rounding interacts with Number of digits after decimal: The value you use for Rounding precision for repayments= strong> cannot be more precise than what you use for Numb= er of digits after decimal. For example, you cannot specify <= strong>2 for Number of digits after decimal and 0.001 (which requires three digits= after the decimal) for Rounding precision for repayments. You can specify 3 forNumber of dig= its after decimal and 0.01 for&nbs= p;Rounding precision for repayments. Note that in this lat= ter situation, the amounts stored in the database will use three decimal pl= aces but the amounts that you view in the Mifos user interface will use two= .
How Mifos rounds the final scheduled repayment.
See Rounding rules for loan payment schedules= for a discussion of why you may choose to use a different rounding mo= de for the final repayment versus other repayments.
Example: Assuming that Number of= digits after decimal is set to 2, a value o= f...
The decimal place the final repayment is rounded to when Mifos calculate= s the loan repayment schedule.
The decimal place you choose can't have a greater precision than what yo= u specify for Number of digits after decimal. In= addition, the degree of precision used for the final repayment cannot be g= reater than what you use for the other repayments see the examples. A= lso, the setting must be greater or equal precision than InitialRoundingOff= Multiple.
Example: If the currency is...
How rounding interacts with Number of digits after decimal: The value of Rounding precision for repayments&n=
bsp;cannot be more precise than that of Number of digits after=
decimal. For example, you cannot specify 2&=
nbsp;for Number of digits after decimal and
About the precision used for final repayments: The prec=
ision you use for Rounding precision for final payments must be equal to or less precise than the precision you use for&nbs=
p;Rounding precision for repayments. For example, if you s=
et Rounding precision for repayments to
If you want to set a different Final Round Off Multiple in an additional= currency, set another property with the currency code in the property name= . For example, if Mifos has been configured with an additional curren= cy LBP, to set a different Final Round Off Multiple, use the property name = AccountingRules.FinalRoundOffMultiple.LBP.
In Mifos, the fiscal year starts on January 1 and ends December 31. Use = the Calendar section ofapplictionConfiguration.custom.properties to configure other aspects of the MFI's calendar, including whi= ch days are working days and how repayment meetings should be handled if a = meeting falls on on a non-working day.
The days of the week that are workdays.
Mifos uses the first day you specify as the start of the fiscal week. It= uses the days you do not specify as non-workdays. You must specify at leas= t one workday. Each workday you specify should be separated by a comma with= no spaces on either side.
Example: FiscalCalendarRules.W= orkingDays=3DMONDAY,TUESDAY,WEDNESDAY,THURSDAY,FRIDAY,SATURDAY = causes Mifos to treat Monday as the start of the fiscal week, for reporting= purposes, and Sunday as a non-workday.
How Mifos handles rescheduling a repayment or meeting when it falls on a= non-workday. There is still an existing issue here with same_day opt= ion. Issue MIFOS-2226.
This property applies to non-workdays. Mifos can either schedule t= he repayment or meeting for the same day (regardless of it being a non-work= day), the next workday, or the next scheduled meeting or repayment.
Example: If FiscalCalendarRule= s.ScheduleMeetingIfNonWorkingDay=3Dsame_day, repayments or meetings that fall on a non-workday will still be schedul= ed for that day. If the value is set to next_working_day, a repayment or meeting that falls on a non-workday will be rescheduled= for the next workday.
Use the Client section of applicationConfiguration.custom.p= roperties to refine how Mifos represents the MFI's hierarchy = and control which entities can apply for loans. This section also has= settings on client information.
Does the MFI have one or more centers in its hierarchy? By default, Mifo= s assumes that an office is at the top of the hierarchy, followed by center= s, groups, then clients.
Example: ClientRules.CenterHie= rarchyExists=3Dfalse causes Mifos to use a hierarchy of 1. Offi= ce, 2. Groups, and 3. Clients instead of 1. Office, 2. Centers, 3. Groups, = and 4. Clients. In other words, with a value of false= , Center is excluded from Mifos' representation of the MFI's hierachy. Opti= ons involving centers are also removed from the Mifos user interface. For e= xample, the Create new center option is removed = from the left navigation bar of the Clients & Accounts tab.
Can clients be independent of groups or must all clients belong to a gro= up? By default, Mifos assumes that a new client can be created without that= client needing to be part of a group. Instead, the client need only belong= to an office.
Example: ClientRules.ClientCan= ExistOutsideGroup=3Dtrue allows you to create a new client that= is assigned directly to an office instead of to a group, then to an office= . To use this capability, when you are prompted to select a group in the ne= w client creation process, click the link that reads "Click here to continu= e if group membership is not required for your client".
Can groups apply for loans in addition to clients or can only clients ap= ply for loans? By default, Mifos assumes that the entity applying for a loa= n can be a group or a client.
Example: ClientRules.GroupCanA= pplyLoans=3Dtrue allows groups, as well as clients, to apply fo= r loans.
Set the minimum age for new clients entered into Mifos. Setting th= is value to 0 means a minimum age will not be enforced.
Example: ClientRules.Mi= nimumAgeForNewClients=3D30 when entering a = client, if their birthdate shows the client is younger than 30 years old, a= n error message will be displayed and the client cannot be entered.
Set the maximum age for new clients entered into Mifos. Set this v= alue to 150 if you do not want this enforced.
Property name: ClientRules.MaximumAgeForNewClients
Example: ClientRules.Ma= ximumAgeForNewClients=3D60 when entering a = client, if their birthdate shows the client is older than 60 years old, an = error message will be displayed and the client cannot be entered.
Use the Process section in applicationConfiguration.custom.= properties to include or exclude optional steps when Mifos cr= eates clients, groups, and accounts. These settings will= be DEPRECATED in the release after Mifos 2.0.
Workaround for setting to false In the Mifos datab= ase, execute the following command: UPDATE&= nbsp;CUSTOMER_STATE SET= CURRENTLY_IN_USE=3D0 WHERE STATUS_ID=3D2;
To approve a newly added client:
If you use the default setting (true), an approval step is added to the = process of adding a new group. Specifically, instead of a newly added group= going straight to Active status, it goes to an Application Pending Approva= l status. Because of a problem with this property (issue 2252), don't use the properties file to set it to fals= e. Instead, use the workaround below.
Workaround for setting to false In the Mifos datab= ase, execute the following command: UPDATE&= nbsp;CUSTOMER_STATE SET= CURRENTLY_IN_USE=3D0 WHERE STATUS_ID=3D8
To approve a newly added group:
If you use the default setting (true), loans will go into pending approv= al after it is created. If you set this to false, loans are directly approv= ed. We do not recommend this
Workaround for setting to false In the Mifos datab= ase, execute the following command: UPDATE&= nbsp;ACCOUNT_STATE SET<= /span>CURRENTLY_IN_USE=3D0 WHERE ACCOUNT_STATE_ID=3D2
To approve a newly created loan account:
If you use the default setting (true), an approval step is added to the = process of creating a new savings account for a group or client. Because of= a problem with this property (issue 225= 2), don't use the properties file to set it to false. Instead, use the = workaround below.
Workaround for setting to false In the Mifos datab= ase, execute the following command: UPDATE&= nbsp;ACCOUNT_STATE SET<= /span>CURRENTLY_IN_USE=3D0 WHERE ACCOUNT_STATE_ID=3D14
To approve a newly created savings account:
Use the Reporting section in applictionConfiguration.custom= .properties to customize some of the reporting- and repayment= -related capabilities in Mifos.
Allows Mifos to upload both admin documents and report templates at a no= n-volatile location. A custom upload storage directory is reflected on the = System Information page.
Example: GeneralConfig.UploadStorageDirectory=3DC= :/reports
Allows Mifos to accept transactions dated earlier than the current date.=
Example: BackDatedTransactions= Allowed=3Dtrue allows users to enter transactions that have dat= es earlier than the date on which the transactions are entered in Mifos. If= the value is set to false, transactions must use the= current date.
This setting has no effect--it works with a collection sheet batch job t= hat was disabled in Mifos version 1.1. When the collection sheet batch job = is enabled, this setting allows you to generate collection sheet data for a= future meeting. The value you specify represents the difference (in days) = between the current day and the future meeting day for which you want to ge= nerate collection sheet data.
Example: If you set CollectionSheet.DaysIn= Advance to 1, the batch job will genera= te collection sheet data for tomorrow's meetings (1 day from today). If you= set it to 2, it will generate data for meetings that= happen the day after tomorrow (2 days from today).
This setting is currently invalid.
Property name: RolesAndPermissions.Br= anchManager.RoleName
If you are using a plugin in Mifos that needs an order= of accounts set for which the transactions should be applied, use this set= ting.
This example is for the MPESA plugin
where AL1, NL1, and SP1 are short names of the products to which you wan= t to apply the transactions to.
If you are using the MPESA plugin in Mifos for Loan Di= sbursals, MPESA has a maximum limit for Loan Disbursals. The default = is at 50000 right now.
Use the Batch Jobs section in applicationConfiguration.cust= om.properties to customize the batch job settings in Mifos.= p>
You can set Hibernate cache size for batch jobs.
By default, Mifos gives users up to 30 minutes of inactivity before it t=
imes out their sessions and requires them to log in again. To change this v=
alue, edit the following section in the deployment descriptor file, web.xml, which ships in the Mifos WAR at WEB-INF:
=09=09<session-config> <session-timeout>30</session-timeout> </session-config>
The data that you and other Mifos users work with is maintained by batch= jobs, which are a series of scripts that are executed on the computer wher= e Mifos is installed. These scripts perform calculations, act on the Mifos = database, and ensure, for example, that the repayment information entered i= n Mifos today is reflected in the reports that are generated tomorrow. Keep= the following tips in mind with regard to batch jobs:
Batch jobs are scheduled in task.xml. In Mifos ver= sion 1.3 and later, task.xml is placed in one of the MifosConfigurationLocations. In ea= rlier versions, task.xml can be customized by editing the Mifos WAR (WEB-IN= F/classes/org/mifos/framework/util/resources/batchjobs).
There is a 'Batch Jobs' page to display information about configured bat= ch jobs. You can check the latest batch job status, its next start time and= trigger details. Moreover, you can start selected batch jobs on-demand.
See Managing Batch Jobs in Mifos for more infor= mation.
You can customize various aspects of your database connection, such as w=
hich host to connect to, the database name, your user name and password, as=
well as the connection pool settings, by placing a file called
Note: The file deploymifosDB.properties is based on hibernate.properties. If the = latter changes in a future release of Mifos, your copy of depl= oymifosDB.properties may also require changes.
See MigratingToPostV12DatabaseConfiguratio= n for modifying your database connection if you upgrade from versi= on 1.2.x to 1.3.x (or later). See LocalPropertiesFile if you've started with Mifos version= 1.3.x (or later, including trunk development builds).
Some Mifos features are configured directly in the database. The setting= s described below are located in the config_key_value_integer<= /strong>table in the Mifos schema:
- The value for Minimum Days Between Disbursal and First Rep= ayment is used when Loan Schedule Independent of= Meeting is enabled. This setting determines how tight the in= terval can be between disbursing a loan and requiring the first repayment f= or same. The default value is 1, which ensures that a= loan disbursal and the first repayment can never be less than one day apar= t.
- The value for Maximum Days Between Disbursal and First Rep= ayment Day is used when Loan Schedule Independen= t of Meeting is enabled. This setting limits the number of da= ys that can pass between disbursing a loan and requiring the first repaymen= t for same. The default value is 365.
After you define the administrative se=
ttings that can only be configured when Mifos is not running (incl=
uding the one-tim=
e settings), it's time to configure some of the settings on the Admin tab in Mifos. Not every setting on the
To access the settings on the Admin tab, you need to start the Mifos app= lication.
To start Mifos:
The options in the Data Display and Rules gro= up allow you to customize certain labels and list-box items, hide or requir= e certain fields, and define new fields for additional information you want= to collect.
To define labels:
You can use Define Look-Up Options to populat= e the contents of list boxes. Once you add a look-up option and Mifos is in= production, you should not remove it because it may be in use. Additional = look-up options can be added after Mifos is in production.
To create new list box items or edit existing items:
Use the Define mandatory/hidden fields link t= o designate which fields are viewable in various parts of Mifos, which are = required, and which are hidden. Some sites that have interfaced with other = systems have found the External id field useful = as a required field.
To make a field viewable, required, or hidden:
Use the Define additional fields option to cr= eate a new user interface option, for example, to collect information from = clients that isn't already requested by Mifos. Use the View ad= ditional fields option to see which new options have already = been created.
To create a new field:
Office hierarchy is Mifos' view of how your MFI is organized. Mifos uses= the office hierarchy information you provide for a wide variety of essenti= al actions, including creating users defining new clients and groups, manag= ing transactions, and reporting. At minimum, Mifos requires two levels of h= ierarchy: a Head Office, provided by default (Mifos HO), and at least one B= ranch Office. At maximum, there can be five levels: Head Office, Regional O= ffice, Sub-Regional Office, Area Office, and Branch Office.
Defining office hierarchy in Mifos involves first removing office types = that aren't represented in your organization and then adding those offices = that are.
To remove office types:
To add offices:
After you define your MFI's office hierarchy in Mifos, it's time to crea= te roles, which are collections of actions that a user can perform in Mifos= .
To create a role:
Once you define roles in Mifos you can create the users who will be assi= gned those roles. There are two types of users in Mifos: Loan Officers or N= on-Loan Officers. A Loan Officer can only belong to a Branch Office.
To create a user:
Mifos uses Cash as the default value for acce= pted payments.
To specify a different or additional payment type: = ;On the Admin tab under Data Display and Ru= les, click Define Lookup options. Payment Modes= can be added or changed here.
To specify what payment types are accepted for each type of tran= saction: On the Admin tab under&nb= sp;Organization Preferences, click Define acc= epted payment types.
Most MFIs are applied following loan repayment order:
1. Penalty
2. Fees
3. Interest
4. Principal
as is the standard in banking solutions.
MFIs, which have a need to modify this repayment order, can do it by con= figure this repayment order in Mifos config file.
After enabling this option, all overdue interests will be paid f= irst, before principal amount.
To configure repayment order open applicationConfiguration.custom.proper= ties file and set:
OverdueInterestPaidFirst=3Dtrue (always repay over=
due interest first)
OverdueInterestPaidFirst=3Dfalse&nb=
sp;(standard payment order)
Before loan and savings products can be defined, the default loan latene= ss and savings dormancy definitions should be reviewed and changed, if nece= ssary. Both of these settings are configured on the Admin tab via the View lateness/dormancy definition link.
So that it can correctly calculate repayment schedules, Mifos needs to k= now what your MFI's holidays are and how you would like repayments handled = if a repayment happens to fall on a holiday. Mifos can either schedule the = repayment for the same day (regardless of it being a holiday), the next wor= kday, or the next scheduled meeting or repayment. Note that in Mifos, holid= ays are different from non-workdays.
To define a holiday:
As a system administrator you may also be reponsible for setting up repo= rts for your users and adding a PPI survey to your deployment. Use the foll= owing links for more information:
Cloud Foundry is an open platform as a service, providing a choice of cl= ouds, developer frameworks and application services. You can place there yo= ur application so others may see it in web. Thanks to Cloud Foundry you don= 't have to worry about infrastructure such as servers. If you want to provi= de data access to your database created in cloud, you need to configu= re your system variables.
There is a JSON array under VCAP_SERVICES that has complete information = for the bound services. System variable which contains JSON document looks = like following:
export VCAP_SERVICES=3D'{"mysql-5.1":[
{
"name":"mysql-4f700",
"label":"mysql-5.1",
"plan":"free",
"tags":["mysql","mysql-5.1","rel=
ational"],
"credentials":{
"name":"=
mifos",
"hostnam=
e":"localhost",
"host":"=
localhost",
"port":3=
306,
"user":"=
mifos",
"usernam=
e":"mifos",
"passwor=
d":"mifos"
}
},
]}'
Attribute | Explanation |
name | The name of database |
hostname/host | Database address |
port | Number of port |
username/user | Name of user |
password | Password |
Note: Variable VCAP_SERVICES has priority (before properties).