Temenos Lifecycle Management Suite - Account Origination Product Guide
Origination
Administrator Guide > Origination

The Origination page enables institutions to manage parameter settings for the Account Origination module.

To access the Origination page, navigate to System Management > Modules > Origination.

Each tab contains a variety of parameters that optimize Temenos functionality. Parameters with an asterisk (*) require an Internet Information Services (IIS) reset on all Temenos Infinity servers in order for any configuration changes to take effect.

It is advised that the IIS reset occurs after business hours as it causes a disruption in the production environment.

Origination Tab

The Origination tab contains parameters that allow institutions to configure functions related to the origination stage:

Field Name Solution Parameter Description Valid Values
Application age for Select Application search (days) APPLICATION_AGE_IN_DAYS Determines the number of days old an application must be in order to display in the Select Application pop-up window during a search.

Textbox:

Integer > 0

Eligibility Required

 

 ELIGIBILITY_REQUIRED

Determines whether non-member applicant information is input on the Applicant screen of the sub-product (No) or on the Non-Member Information screen and Non-Member Eligibility screen (Yes).

Drop-down:

Yes or No  

If the value of this field is set to Yes, and the Primary applicant value for IsEligible is false, then disbursement cannot continue and an error message stating the following is received: "The primary applicant is not eligible."
Eligibility Segmentation ID ELIGIBILITY_SEGMENTATIONID Determines whether or not a value from Lending_Segmentation_Code is applied to the application. Drop-down list: Application > Applicants > Segmentation > Description
Include External Liabilities in Add On Refinance Panel INCLUDE_EXTERNAL_LIABILITIES Determines whether or not external liabilities are displayed on the Add On Refinance panel.

Drop-down: 

Yes or No
Load demographics and income from prior application for applicant with Invalid TIN INVALID_TIN_DEMOGRAPHICS Determines whether applicant demographics and income information are pulled from previous applications when an applicant has been flagged as having an invalid TIN.

Drop-down: 

Yes or No

This parameter defaults to No.

Default Virtual Capture Instance

This parameter only appears when Virtual Capture is enabled for the institution.
DEFAULT_VIRTUAL_CAPTURE_INSTANCE Determines the default instance of Virtual Capture where applicants are navigated to if they access Virtual Capture with a URL that does not include an instance code.

Drop-down:

All active instances configured in System Management > Origination > Virtual Capture > Virtual Capture Settings. The options available in this list are formatted as <Instance Type> - <Instance Name>.

While set as the default Virtual Capture instance in this parameter, the instance cannot be disabled or deleted in Virtual Capture Settings.

ShowTIN Validation Rules

The TIN Validation Rules multi-grid allows institutions to assign one or more Validation Rules to execute when an application is created or an applicant is added to an existing application. If the criteria within the rule fails validation when an application is created or an applicant is added, the Is Invalid TIN field is set to true.

It is imperative that only TIN validation rules are set here, as it may result in errantly flagging an applicant's TIN as invalid.
Only validations written at the Applicant level populate in this grid.

 

ShowApplication Initialization Validation Rules

The Application Initialization Validation Rules multi-grid allows institution to assign one or more Validation Rules to execute when the application is created. If the criteria within the rule fails validation, the application is not created.

 

Underwriting Tab

The Underwriting tab contains fields that allow institutions to configure functions related to application underwriting:

Field Name Solution Parameter Description Valid Values
Credit Report Format CREDIT_REPORT_FORMAT Determines the custom format for credit reports. If left blank, the LUXCOMMON SUMMARY profile is used.

Drop-down: 

  • HTML Common01 – Tradeline01
  • HTML Common01 – Tradeline02
  • HTML Common01 – Tradeline03
  • HTML Common01 – Tradeline04
  • HTML Common01 – Tradeline05
  • HTML Common01 – Tradeline06
  • HTML Lending01 – Tradeline01
  • HTML Lending01 – Tradeline02
  • HTML Lending01 – Tradeline03
  • HTML Lending01 – Tradeline04
  • HTML Lending01 – Tradeline05
  • HTML Lending01 – Tradeline06

For an overview of the Credit Report Formats that are available in Temenos Infinity, please see the HTML Credit Report Formats topics in the User Guide.
Credit Report Grouping CREDIT_REPORT_GROUPING Determines the criteria by which credit report data, or tradeline information, is grouped when the report is generated, such as Account Type, or Open/Closed Accounts.

Drop-down:

  • System - Default value, which disables grouping criteria, and displays credit report data by the existing sort configuration.
  • IdMatch - Groups data by applicant in the credit report, and displays a separate section for secondary applicants.
  • IdMatch2 - Groups data by applicant in the credit report, and displays a separate section for secondary applicants; however this option also sorts tradeline data by Subject and Spouse Accounts in the Tradeline Information section.
  • Open/Closed - Groups tradeline information by open and closed accounts.
  • Derogatory Accounts - Groups tradeline information by derogatory and good accounts.
  • Account Type - Groups tradeline information by account type.

For an overview of each credit report grouping option, please see HTML Credit Report Formats topic in this guide.
Liability Match - Balance Amount % Tolerance Factor DEDUPE_BALANCE_TOLERANCE_FACTOR Determines the balance amount tolerance factor used when searching for a liability to map to an address.

For example, if the Balance Amount % Tolerance Factor is set to 0.05 (5%) and the liability balance amount in the core is within 5% of the liability balance amount in the credit report, the liability is considered a duplicate.

For information on how the system de-duplicates liabilities, please see the Pulling Credit topic of the User Guide.

Textbox:

Decimal > 0
Liability Match - Payment Amount % Tolerance Factor DEDUPE_PAYMENT_TOLERANCE_FACTOR Determines the payment amount tolerance factor used when searching for a liability to map to an address.

For example, if the Payment Amount % Tolerance Factor is set to 0.05 (5%) and the liability payment amount in the core is within 5% of the liability payment amount in the credit report, the liability is considered a duplicate.

For information on how the system de-duplicates liabilities, please see the Pulling Credit topic of the User Guide.

Textbox:

Decimal > 0
Liability Match - Consider Trade Type DEDUPE_COMPARE_BY_TRADETYPE Determines whether or not the trade type is considered when searching for a liability to map to an address.

Drop-down: 

Yes or No
Liability Partial Account Number Length LIABILITY_ACCOUNT_MATCH_LENGTH Determines the amount of Credit Report Account Number digits that are compared during the applicant credit reporting de-duplication process.

For example, if the Liability Partial Account Number Length is set to 6, the first six digits of the Credit Report Account Number on the application are compared to the first six digits of the Credit Report Account Number on the credit report. If the first six digits match, the credit reports are de-duplicated. If the first six digits do not match, the last six digits of the Credit Report Account Numbers are compared.

Textbox: Numerical value between 0 and 999

The default value of the Liability Partial Account Number Length field is 0, which indicates that the whole Credit Report Account Number is compared.
The recommended value of the Liability Partial Account Number Length field is 6.

 
Apply Liability Partial Account Number Match only when from Host LIABILITY_ACCOUNT_MATCH_FROM_HOST

Determines how liabilities are de-duped between applicants when there is a partial account number match for credit report tradelines.

Drop-down: 

Yes or No

If this parameter is set to No, credit report tradelines that have a partial account number match between applicants are de-duped if the partial account number length is greater than zero, and the liabilities have the same open date and Trade category.

 

If this parameter is set to Yes, credit report tradelines are NOT de-duped when there is a partial account number match if the liability partial account number length is greater than zero, and the liabilities have the same open date and Trade category. 

 

This parameter has no effect on the de-duping logic for core liabilities with a partial account number match when the liability partial account number length is greater than zero, and the liabilities have the same open date and Trade category.
Include concurrent applications in aggregates and ratios INCLUDE_CONCURRENT_APPS Determines whether or not concurrent applications are used in the Account Origination module

Drop-down: 

Yes or No
Remote Signature Provider REMOTE_SIGNATURE_PROVIDER Determines the remote signature provider used by the financial institution. Drop-down: IMM, DocuSign, or Silanis

Setting this parameter determines whether DropSpot functionality is used for the following connectors:

  • IMM - Sets IMM as the document signature provider. If selected, documents generated by IMM are signed using the IMM Signature Pad or remotely by printing documents out, signing them, and scanning them.
  • DocuSign - Sets DocuSign as the document signature provider. If selected, documents generated by IMM are saved as a password protected zip file to allow them to be converted into DocuSign documents.
  • Silanis - Sets Silanis as the document signature provider. If selected, documents generated by IMM are saved as a password protected zip file to allow them to be sent to Silanis.
For additional information about using these connectors, please see the applicable connector guides.
Decision Order DECISION_ORDER Determines whether the loan or account decision is rendered first during the automated decision process for an application that requires both decisions.

Drop-down: Account First, Loan First

Regardless of the module(s) active for an institution, values of Account First and Loan First appear in this drop-down, and the default value for this parameter is Loan First.

The system has checks in place during the decisioning process to verify the type of decision required for an application, and perform the appropriate action for the account decision when a loan product is not present; therefore, if the value of this parameter is set to Loan First, but a loan decision is not required, the account is automatically decisioned first regardless of the value set for this parameter..
Reuse Credit Report REUSE_CREDIT_REPORT Determines if the system reuses the most recent credit report from any credit bureau, or the most recent report based on the credit bureau sequence logic for an application type.

Drop-down:

  • Any credit bureau - The system uses the most recent report from any credit bureau that meets reuse criteria.
  • Credit bureau sequence - The system reuses the most recent credit report from a specific credit bureau, which is based on the credit bureau sequence assigned to the application type in the Credit Bureaus tab in System Management > Origination >Account > Account Application Types.
    • The system automatically uses the most recent credit report that meets reuse criteria from the first credit bureau in the specified sequence.
    • If no report from the first credit bureau meets reuse criteria, the system proceeds through the credit bureau sequence order, and uses the most recent report that meets criteria from the second credit bureau in the sequence.
    • If a match is not found for the credit bureau in sequence two, the system proceeds to the reports from the credit bureau in sequence three.
    • If there are no other bureaus assigned to the sequence, or a match cannot be found among all of the credit bureau reports, a new credit report is pulled. 
To learn more about the criteria to reuse a credit report, please see the Pulling Credit topic in the User guide. For more information on the credit bureau sequence for an application type, please see the Credit Bureaus section of the  topic in the Administrator guide.

Approved Tab

The Approved tab contains fields that allow institutions to configure functions related to approved applications:

Field Name Solution Parameter Description Valid Values
Method for determining “Decision By” user DECISIONED_BY_METHOD Determines the value used to set the Decisioned By user.

Drop-down: 

FINAL or SUGGEST
Type of email address for sending custom emails FROM_EMAIL_ADDRESS_TYPE Determines the email address used when sending custom emails from within Temenos Infinity.

Drop-down: 

SYSTEM or USER

Declined Tab

The Declined tab contains fields that allow institutions to configure functions related to declined applications, including the ability to automate the decline process for applications with counteroffers that have not been accepted.

Field Name Solution Parameter Description Valid Values
Default Adverse Action DEFAULT_ADVERSE_ACTION Determines the default Adverse Action ID used for the ADVERSE_ACTION lookup type. Drop-down: Select lookup based on “ADVERSE_ACTION” lookup type
Default Decline Reason DEFAULT_REJECT_REASON Determines the default Reject Reason ID used for the REJECT_REASON lookup type when an application is auto declined. Drop-down: Select lookup based on “REJECT_REASON” lookup type
Prefer Mailing Address when sending Adverse Actions PREFER_MAILING_ADDRESS Determines the address that is used in the Adverse Action Export.
If the Prefer Mailing Address option is set to Yes, the Mailing Address for an Applicant is used instead of the current address.		 Drop-down: 

Yes or No

System Tab

The System tab contains fields that allow institutions to configure Temenos Infinity or host configuration policies:

Field Name Parameter Description Valid Values
Number of application tabs allowed per session MAXLENDINGWORKSPACE Determines the maximum number of application tabs that can be open during a user's session in Temenos Infinity.

Textbox:

Integer > 0
Host supports account number auto-generation HOST_AUTOGEN_LOANNUMBER Determines whether the host supports auto-generation of loan account numbers (Yes) or if account numbers must be entered by the user (No).

Drop-down: 

Yes or No
Host supports person account number auto-generation HOST_AUTOGEN_PERSONNUMBER Determines whether the host supports auto-generation of person account numbers (Yes) or if account numbers must be entered by the user (No).

Drop-down: 

Yes or No    
Account Product Number (suffix) is editable and required ACCOUNT_PRODUCT_SUFFIX_IS_REQUIRED Determines whether or not the account product number suffix is required and can be edited.

Drop-down:

Yes or No
Credit Union routing number ROUTING_NUMBER Determines the default routing number used for internal transfers.

Textbox:

Number, 9 digits
GL Code (OSI only) HOST_CHECK_CODE Determines the GL Code used for DNA (OSI). Textbox: Optional
Update Demographics for Account Search CHANGEACCOUNT_INCLUDE_DEMOGRAPHICS Determines whether or not demographics are updated when the Change Loan/Account Number pop-up window is saved in the application workspace. Drop-down:

Yes or No
Include Addresses when updating Demographics CHANGEACCOUNT_INCLUDE_ADDRESS Determines whether or not addresses are included in demographic updates when the Change Loan/Account Number pop-up window is saved in the application workspace.

Drop-down:

Yes or No
Update Core Messages for Account Search CHANGEACCOUNT_INCLUDE_COREMESSAGES Determines whether or not Core Messages are updated when the Change Loan/Account Number pop-up window is saved in the application workspace.

Drop-down:

Yes or No
Account Decision for Existing Account Holder ACCOUNT_DECISION_FOR_EXISTING_ACCOUNT_HOLDER Determines whether account applications for existing account holders are automatically approved or require a decision.

Drop-down:

  • Auto Approve - automatically approves all account applications for existing account holders. When this value is set, the user is navigated directly to the Approval stage in the application.
  • Require Decision - requires users to begin the account application process for an existing account holder in the Origination stage and collect the necessary information to decision the application. When this value is set, all account applications are processed through the Account Decision Model assigned to the Account Application Type and decisioning/validation rules are executed.
Virtual Capture Configuration Refresh Frequency (Minutes) CONFIG_REFRESH_MINUTES

Determines the number of minutes to pass before an automatic refresh of the virtual application occurs. After the set amount of time passes, Virtual Capture automatically refreshes to apply the updated configurations made in Temenos Infinity to the virtual application.

This is a global setting for all instances of Virtual Capture.

Textbox:

Integer > 0
This parameter defaults to 30.

 
Document Virus Scan in Virtual Capture and API VIRTUAL_CAPTURE_SCAN_TYPE Determines whether documents uploaded in Virtual Capture are sent through a virus scan at the financial institution.

Drop-down:

None or Virus Scan

For more information on this functionality, please see the Getting Started with Virtual Capture topic in this guide.
Document Import File Location QUARANTINE_PATH

Identifies the file path location on the institution's network where documents are to be placed to await a virus scan when attached to a Virtual Capture application.

The Document Import File Location should be accessible by the DMZ server (either local to the DMZ server, or an accessible UNC path) to have files dropped into for scanning.

Textbox

This parameter is disabled when the Document Virus Scan in Virtual Capture parameter is set to None. When the above parameter is set to Virus Scan, a value must be defined for the Document Import File Location in order to save the Origination page.
Document Export File Location DESTINATION_PATH

Identifies the file path location on the institution's network where documents are to be placed by the institution once they successfully complete a virus scan.

The Document Export File Location should be accessible by the Application server (either local to the Application server, or an accessible UNC path) so that the documents picked up in this location can be attached to the application.

Textbox

This parameter is disabled when the Document Virus Scan in Virtual Capture parameter is set to None. When the above parameter is set to Virus Scan, a value must be defined for the Document Export File Location in order to save the Origination page.
Host supports Organization HOST_SUPPORTS_ORGS

Identifies whether the core system supports the Organization functionality, and enables the ability to create applications for Organizations.

Drop-down:

Yes or No

This parameter defaults to No, and should remain No if the institution's core system does not support Organizations.

 

If the core system supports Organizations, set the parameter to Yes to enable the functionality required to create an application for an Organization, as well as transmit Organization data between Temenos Infinity and the core during the application process.

To learn more about the Organization functionality supported for a specific core, please see the applicable core connector guide for the institution.
Host supports Real Time Payoff HOST_SUPPORTS_REAL_TIME_PAYOFF Identifies whether the core system supports real-time payoff requests as part of Applicant Import and Disbursement.

Drop-down:

Yes or No

By default, this parameter is set to Yes for all institutions, and should remain Yes if the institution's core supports real-time payoff requests. If real-time payoff requests are not supported by the core interface, set this parameter to No.
Host supports Member Account Number HOST_SUPPORTS_MEMBER_ACCOUNT_NUMBER Identifies whether the core system supports the creation of member accounts in their interface.

Drop-down:

Yes or No

By default, this parameter is set to Yes for all institutions. If Member Accounts are not supported by the core interface, set this parameter to No.

 

When set to No, the Account Number field is removed from the New Application screen that appears when creating an application. Additionally, the Select Applicant windows are updated to display a column for Customer Identifier, rather than Account and Role.

 

Blacklist Tab

The Blacklist tab provides administrators with the ability to define the parameters that are used to prohibit certain IP addresses from accessing Temenos Infinity's Virtual Capture solution to submit account applications.

The Blacklist tab contains the following fields:

Field Description
Number of applications allowed per IP Address Enter the number of Virtual Capture applications that can be submitted from each unique IP address within the time-frame specified in the below parameter for Number of Days to Blacklist an IP Address. When an IP address has reached the maximum number of applications within the specified number of consecutive days, the applicant is redirected to an error page in Virtual Capture.
Number of Days to Blacklist an IP Address Enter the number of consecutive days that must pass before an IP address can be blacklisted if the number of applications allowed for the IP Address is reached within the specified timeframe. Applications cannot be submitted from a blacklisted IP address.
When an IP address is blacklisted, the IsIPBlacklisted flag is set to true on the application in Temenos Infinity.
A list of IP addresses that have been blacklisted for the financial institution can be found in System Management > Virtual Capture > Blacklist IP Addresses.

In the above image, both parameters are set to a value of three. Using that example, if three applications are submitted from the same IP Address in three consecutive days, the IP Address is added to the blacklist. If one application is submitted from the IP Address on Monday, one on Tuesday, and then another on Friday, the IP Address is not blacklisted as the applications were not submitted consecutively; however, if two more applications are submitted from the IP Address on Saturday and Sunday, the IP Address will then be blacklisted.

 

 

©2020 Temenos Headquarters SA - all rights reserved.

Send Feedback