End-User Guide > Application Processing > Underwriting > Decision Processing Introduction |
When an application is decisioned, three separate decisions are determined: a loan decision, an account decision, and a decision for the overall application. Reference the table below for an overview of when decisions are calculated during the application process:
Decision | When Calculated | ||
Loan | Calculated when the Loan Application Type has a Decision Model assigned. Once a decision is rendered for a loan, the decision value populates within the LoanDecisionId field. | ||
Account |
Calculated when the Loan or Account Application Type has an Account Decision Model assigned, the primary applicant is a non-account holder, or the Account Decision for Existing Account Holder parameter is set to Require Decision by the system administrator in the System tab of the Origination page (System Management > Modules >Origination). Once a decision is rendered for an account, the decision value populates within the AccountDecisionId field.
|
||
Application |
Calculated when a Loan or Account Decision is required.
The Application Decision is calculated as the lowest possible decision value when combining the Loan Decision and Account Decision. The decision values are ranked lowest to highest in the following order:
Once a decision is calculated for the overall application, the decision value populates within the DecisionId field. |
The following table provides an overview of the possible Application Decisions calculated when an application requires both a Loan and Account decision, and the Decision Order is set to Loan First for the Origination module:
![]() |
The value set within the Decision Order parameter in the Underwriting tab of the Origination page in System Management determines whether a loan decision or account decision is rendered first during the application process. For more information, please see the Underwriting Tab section of the Origination topic in the Administrator Guide. |
Loan Decision | Account Decision | Application Decision | Application Status | ||
Approved | Approved | Approved | Decisioned | ||
Approved | Declined | Declined | Decisioned | ||
Declined |
Not Executed
|
Declined | Decisioned | ||
None | Not Executed | None | Pending Review |
The table below displays the possible Application Decisions for an application requiring both a Loan and Account decision when the Origination module is configured to decision the Account first:
Account Decision | Loan Decision | Application Decision | Application Status |
Approved | Approved | Approved | Decisioned |
Approved | Declined | Declined | Decisioned |
Declined | Approved | Declined | Decisioned |
Declined | Declined | Declined | Decisioned |
None | Not Executed | None | Pending Review |
Application decisions are able to be rendered by two processes:
Both processes are accessible from the Application Toolbar and Workflow. Decisioning occurs one of the following ways:
Clicking runs the Decision Models assigned to the Sub-Product.
![]() |
System administrators have the ability to determine whether or not account applications for existing account holders are automatically approved or require a decision within the System tab located in System Management > Modules > Origination. Reference the section below for an overview of the behavior that occurs in an account application when the system is configured to automatically approve or require a decision for an existing account holder:
The table below provides an overview of the behavior that occurs in an account application when the system is configured to automatically approve or require a decision for an existing account holder:
|
Additionally, users are able to issue Counteroffers if the original loan terms are undesirable.
Once a decision is rendered for a loan and/or an account, as well as the overall application, the values populate within the applicable Decision Id fields.