Database – Multiple Returns Entity (multiple_returns_entity)

Description

This table holds information for the multiple returns entity.

Table Values

Column

Data Type

Column Info

Value Notes

Other

id

int(11)

The id of the record

name

varchar(100)

The name of the record

rule

text

A Clojure rule dictating how source companies or loan settings should be updated when multiple payment returns occur for a single payment profile

codes

text

An optional NACHA return code associated with the return of a payment

number_of_returns

int(11)

The number of returns that need to happen before the rule is evaluated to determine whether the specified actual will be triggered.

evaluate_based_on

int(11)

Whether it will evaluate based on total returns or consecutive returns

0 - total;

1 - consecutive

payment_profile_action

char(60)

When a rule evaluates TRUE, it will trigger this action. The options are to (1) Cancel any AutoPay(s) using payment profile that failed (2) Inactivate payment profile that failed (3) None.

card_fee_amount

decimal(11,2)

The dollar amount for the fee

card_fee_type

char(30)

Whether the fee is a set dollar amount or a percentage

loan.cardfee.types.*

card_fee_percent

decimal(11,2)

The percentage for the fee

agent

int(11)

The agent assigned to the loan

loan_status_id

int(11)

The loan status

loan_sub_status_id

int(11)

The loan sub-status

source_company

int(11)

The source company

payment_type_default

int(11)

The default payment type, as determined by either your company-wide settings or Rules Applied on a specific loan.

ebilling

tinyint(1)

Whether the loan is signed up for ebilling

1 - yes; 0 - no

ecoa_code

char(30)

Borrower ECOA code

loan.ecoacodes.*

co_ecoa_code

char(30)

Co-Borrower ECOA code

loan.ecoacodes.*

credit_status

char(30)

Credit Status

loan.creditstatus.*

credit_bureau

char(30)

Credit Bureau

loan.creditburearu.*

reporting_type

char(30)

Reporting Type

loan.reportingtype.*

secured

tinyint(1)

Whether the loan is secured

1 - yes; 0 - no

autopay_enabled

tinyint(1)

Whether autopay is enabled

1 - yes; 0 - no

merchant_processor_group_id

int(11)

The ID of the merchant processor group assigned to the loan. Merchant processor groups can be found in the merchant_processor group_entity table.

repo_date

int(11)

The repossession date

repo_date_setting

char(100)

Settings for repo_date. Can be configured as Set as Null, Set as Blank, No Change, or a base date* and number of days after.

closed_date

int(11)

The closed date

liquidation_date

int(11)

The liquidation date

liquidation_date_setting

char(100)

Settings for liquidation_date. Can be configured as Set as Null, Set as Blank, No Change, or a base date* and number of days after.

followup_date

int(11)

The followup date

followup_date_setting

char(100)

Settings for followup_date. Can be configured as Set as Null, Set as Blank, No Change, or a base date* and number of days after.

is_stoplight_manually_set

tinyint(1)

Whether the stoplights are manually set

1 - yes; 0 - no

delete_portfolios

tinyint(1)

Whether to remove the associated loan from all portfolios

1 - remove; 0 - no

enroll_new_loans

tinyint(1)

Whether new loans will be enrolled

1 - yes; 0 - no

enroll_existing_loans

tinyint(1)

Whether existing loans will be enrolled

1 - yes; 0 - no

enabled

tinyint(1)

Whether it is enabled

1 - yes; 0 - no

eval_in_daily_maint

tinyint(1)

Whether it will be evaluated in daily maintenance

1 - yes; 0 - no

eval_real_time

tinyint(1)

Whether it will be evaluated in real time.

1 - yes; 0 - no

exec_pre_activation

tinyint(1)

Whether execute pre-activation is enabled. If it is enabled, it will execute on loans before they are activated.

1 - yes; 0 - no

forcing

tinyint(1)

Whether to force the rule application even if the required returns didn't occur

1 - yes; 0 - no

deleted

tinyint(1)

Whether the multiple returns entity has been deleted

1 - yes; 0 - no

global_order

int(11)

When two or more rules are set up with multiple consecutive or total returns each, they might get triggered to evaluate at the same time but would lead to conflicting actions. The global order dictates which actions supersede others.

lastUpdated

timestamp

The time the values were last updated

*The options for base date include the following:

  • Current Date
  • Next AutoPay Apply Date
  • Next AutoPay Process Date
  • Loan Creation Date
  • Last Human Activity Date
  • Date Last Current
  • Final Payment Date
  • Original Maturity Date
  • Insurance Start Date
  • Insurance End Date
  • Last Payment Date
  • Next Due Date
  • Next Scheduled Payment Date
  • Closed Date
  • Liquidation Date
  • Repossession Date
  • Follow Up Date
  • Contract Date
  • First Payment Due Date


How did we do?


Powered by HelpDocs (opens in a new tab)