How are credit rating transactions created?

Credit rating transactions may be created as follows:

  • Certain types of severance events add credit rating transactions. The number of credit rating and cash-only points is defined on the severance event type.
  • Certain types of severance events add credit rating transactions. The number of credit rating and cash-only points is defined on the severance event type.
  • Certain types of write-off events add credit rating transactions. The number of credit rating and cash-only points is defined on the write-off event type.
  • If a payment tender is canceled with a cancellation reason that indicates the cancellation was due to non-sufficient funds, a credit rating transaction is created. The number of credit rating and cash-only points is defined on the payment cancellation reason code.
  • You may configure your system to create a credit rating transaction when a pay plan is broken. To do this, you must plug in an appropriate Broken Algorithm on the pay plan type.
  • A user may create credit rating transactions at their discretion.
  • Algorithms may add credit rating transactions. The system provides sample overdue event and cut event activation algorithms that add credit rating transactions. Refer to C1-OE-CR-RT and C1-CE-CR-RT for more information. Some examples of algorithms your implementation may decide to introduce: the creation of a late payment charge. To do this you could introduce a new adjustment freeze algorithm.
Note:

Created By Flag. The credit rating transaction includes a Created By flag that is customizable using the Lookup table. This field name is CR_​RAT_​CRE_​BY_​FLG. If your implementation uses algorithms to create credit rating history transactions, you may consider adding appropriate values to the Created By flag. Also note that the Created By flag includes the value Other , which may be used by your implementation specific algorithms if you do not want to add a new custom value.