Core Banking System Parameters

• AccountingAnalyticChar

• DaysPastDueInstallmentsReport

• AccountingRealTime

• DefaultIntervalLimitsReport

• AdvanceNotification

• DelayDaysForBlockNewContractApproval

• BankAccountTransactionFeeMarkDown

• DepositAggregateItemValues

• CalendarYearEnd

• EarlyRepaymentFee_IndividualNotification

• CalendarYearStart

• FrontEndFee

• CreditFacilityLimitPercent

• FTOS_CB_CalculatedProvisions

• CurrentAccount_WithOverdraft_DaysBeforeExpire

• FTOS_CB_ExchangeRate_UseLatest

• DaysBeforePurge

• LimitMandatoryForIndividuals

• DaysFutureInstallmentsReport

• LogScheduleJobError

This parameter instructs the system how to process bank account transaction operations. Possible values:

• Total - the system creates 4 operations – 2 for debit and 2 for credit for the transaction value and sum(fees)

• Individual - the system creates 2 * (1+NoFees) operations – debit and credit for the transaction value and each fee.

Specifies if the deposit interest is split in two lines or displayed in one line.

• For False value, the system splits the Deposit interest to recover in two lines (- paid interest -> recover all; sight interest to pay, pay all).

• For True value, the system displays the Deposit interest to recover in one line with the aggregate value.

Specifies whether Core Banking should validate the limits for individual customers or only validate them for legal entity customers.

• For False value, Core Banking does not validate any limits for the individual customers.

• For True value, Core Banking validates all the limits for the individual customers the same way it does for legal entity customers.

Specifies whether job errors should be logged (for True value) as custom job error records or not (for False value). The custom job error records are purged at the interval given by the DaysBeforePurge parameter.

• For False value, the banking product has only one Repayment Fee commission type on its commission list.

• For True value, the banking product's commission list displays all the commissions stored in the FTOS_BP_Commission entity with type Repayment Fee.

Read more information about the effects of this parameter's value in the Transaction Fees section.

• For NoMessage value, there is no error or warning message displayed if the disbursement event that is being approved would result in a negative balance of the associated reconciliation account. The event can be approved and the balance can go below zero.

• For Warning value, there is a warning message displayed if the disbursement event that is being approved would result in a negative balance of the associated reconciliation account. The event can be approved and the balance can go below zero.

• For Error value, there is an error message displayed if the disbursement event that is being approved would result in a negative balance of the associated reconciliation account. The event can't be approved and the balance can't go below zero.

For False value, two bank account transactions are generated with two payments:

• One transaction with source account = Settlement Account and destination account = Reconciliation Account with the value of Total Amount To Recover;

• Another transaction with source account = Reconciliation Account and destination account = Settlement Account with the value of Total Amount To Pay.

For True value, Core Banking calculates the difference between Total Amount To Recover and Total Amount To Pay. Only one bank account transaction is generated and only one payment, representing the non-zero value between the Total Amount To Recover and the Total Amount To Pay, as follows:

• If Total Amount To Recover - Total Amount To Pay > 0, a new bank account transaction is generated with source account = Settlement Account and destination account = Reconciliation Account, and a payment is generated for the invoice.

• If Total Amount To Recover - Total Amount To Pay = 0, a bank account transaction is generated, and the transaction's status changes to Paid.

• If Total Amount To Recover - Total Amount To Pay < 0, a new bank account transaction is generated with source account = Reconciliation Account and destination account = Settlement Account, and a payment is generated for the invoice.

When the payments are approved, the invoice's status becomes Paid.

• For True value, the Credit Facility module is used and the Credit Facility menu item is displayed within the Core Banking Operational menu.

• For False value, the Credit Facility module isn't used and the Credit Facility menu item is not displayed within the Core Banking Operational menu.

• For True value, risk contamination is used for loan classification, thus one unpaid contract affecting all the loan contracts of that customer.

• For False value, risk contamination is not used for loan classification, thus unpaid contracts don't affect other loan contracts of the same customer.