Loan Origination and Workflow Flashcards
nCino Loan Life Cycle: High-Level Flow:
nCino represents the complex processes involved in commercial lending with a simple system of “x”.
- Entity (relationship/entity)
- Lead/Opportunity (convert to product package)
- Product Package
- Loan (pre-underwriting loan)
nCino Loan Life Cycle: High-Level Flow:
nCino represents the complex processes involved in commercial lending with a simple system of “related objects”.
- Entity (relationship/entity)
- Lead/Opportunity (convert to product package)
- Product Package
- Loan (pre-underwriting loan)
Conversion in nCino: Behind the Scenes
The system automatically creates:
Opportunity
- “x”
- “x”
- “x”
- “x”
- “x”
Conversion in nCino: Behind the Scenes
The system automatically creates:
Opportunity
- “Entity Involvement”
- “Relationship”
- “Product Package”
- “Loan”
- “Document Manager”
Complex “x”
nCino can be configured to convert “x” that are tied to a “x” simultaneously.
Complex “Opportunity Conversion”
nCino can be configured to convert “multiple opportunities” that are tied to a “single relationship” simultaneously.
Field Maps: Overview
These are used to “x” on two different “x”. Field maps are used for two major purposes:
- When converting an opportunity to a Product Package or Loan in nCino, a field map can “x” the fields on the opportunity to the fields on the Product Package or Loan.
- Field maps are also used to “x” “x” to a value brought in “x”.
Field Maps: Overview
These are used to “relate fields” on two different “objects”. Field maps are used for two major purposes:
- When converting an opportunity to a Product Package or Loan in nCino, a field map can “relate” the fields on the opportunity to the fields on the Product Package or Loan.
- Field maps are also used to “relate” “object fields” to a value brought in “via integration”.
Custom Settings for Loans
- There are two custom settings in relation to the loan creation UI fields
(a) “x”
(b) “x”
Custom Settings for Loans
- There are two custom settings in relation to the loan creation UI fields
(a) “Hide Loan Name”
(b) “Display Additional Fields”
What’s the default nCino loan naming convention?
Relationship Name - Product Name - Loan Amount
What happens if you turn on the custom setting status for “Hide Loan Name” but there’s a custom WF field update to the set the loan name?
The loan name will respect the custom workflow field update.
Display Additional Fields
“x” different sets of additional display fields by “x”.
Display Additional Fields
“Conditionally render” different sets of additional display fields by “product”.
Entity Involvement: Overview
Entity involvement is a junction object between “x” and “x”.
- Entity involvement describes the “x” of a loan.
- Entity involvement is similar to “x” that link two relationships.
- Entity involvement drives many things in nCino.
Entity Involvement: Overview
Entity involvement is a junction object between “relationships” and “loans”.
- Entity involvement describes the “borrowing structure” of a loan.
- Entity involvement is similar to “connections” that link two relationships.
- Entity involvement drives many things in nCino.
Entity Involvement: Households
When a “x” is created on a “x” that is associated with a “x”, an entity involvement record for both the “x” and the “x” is automatically created.
Relationships in nCino are grouped using both “x” and “x” records. This functionality is used to build the total “x structure”.
Entity Involvement: Households
When a “loan product” is created on a “relationship” that is associated with a “household”, an entity involvement record for both the “relationship” and the “household” is automatically created.
Relationships in nCino are grouped using both “entity involvement” and “connection” records. This functionality is used to build the total “householding structure”.
Viewing Entity Involvement
Entity Involvement is located when selecting the “x” navigation route within the nCino UI.
Viewing Entity Involvement
Entity Involvement is located when selecting the “Borrowing Structure” navigation route within the nCino UI.
Entity Involvement Optional Configuration
nCino Entity Involvement workflow is mostly a standard process with “x” that requires little “x”. However, there are some optional items that may be configured based on client-specific requirements.
Entity Involvement Optional Configuration
nCino Entity Involvement workflow is mostly a standard process with “OOTB functionality” that requires little “configuration”. However, there are some optional items that may be configured based on client-specific requirements.
Entity Involvement Optional Configuration: 1 - Disable Add Signer Workflow
If “authorised signers” aren’t needed by the client, this workflow can be disabled by editing a “custom setting”.
Entity Involvement Optional Configuration: 1 - Disable Add Signer Workflow
If “x” aren’t needed by the client, this workflow can be disabled by editing a “x”.
Entity Involvement Optional Configuration: 2 - Hide Add New Relationship Button
If adding a new relationship from the “x” is not needed by the bank, this workflow can be disabled by editing a “x”.
Entity Involvement Optional Configuration: 2 - Hide Add New Relationship Button
If adding a new relationship from the “EI Experience” is not needed by the bank, this workflow can be disabled by editing a “custom setting”.
Entity Involvement Optional Configuration: 3 - Change Default View of Authorised Signers
The default view to display the Authorised Signers “x” may be “x”, thus hiding from user view.
Entity Involvement Optional Configuration: 3 - Change Default View of Authorised Signers
The default view to display the Authorised Signers “table” may be “disabled”, thus hiding from user view.
nCino Product Catalog
The nCino product catalog is a “x” of the “x” offered by a financial institution.
The product catalog includes “x”, nCino-managed product catalog “x”.
These product catalog “x” are different from the standard Salesforce “x”.
nCino Product Catalog
The nCino product catalog is a “representation” of the “products” offered by a financial institution.
The product catalog includes “custom”, nCino-managed product catalog “objects”.
These product catalog “objects” are different from the standard Salesforce “product objects”.
Impacts of Product Catalog in nCino
- “x” by product type
- “x”
- “x” to nCino/”x”
- “x” placeholders
- “x” from a relationship
- “x” to the bank’s core system
- “x”
Impacts of Product Catalog in nCino
- “UI rendering” by product type
- “Page layouts”
- “Conversion” to nCino/”Product Package”
- “Document Manager” placeholders
- “Loan creation” from a relationship
- “Integration” to the bank’s core system
- “Credit actions”
Determining a Loan Product
nCino uses a “three-tier hierarchy” to determine a loan product.
Product Line
- “Highest” level of categorisation
- It often includes categorisation by “Line of Business (LOB)”
Product Type
- Is the “middle” level of categorisation
- Often used to drive “conditional rendering”
Product
- “Lowest” level of categorisation
- The “metadata aspects” of the “actual product” are defined at this level.
Determining a Loan Product
nCino uses a “x” to determine a loan product.
Product Line
- “x” level of categorisation
- It often includes categorisation by “x”
Product Type
- Is the “x” level of categorisation
- Often used to drive “x”
Product
- “x” level of categorisation
- The “metadata aspects” of the “x” are defined at this level.
Product Data: Metadata and Record Data
Each “x” has two components, “x” and “x”.
Metadata
- What the user “x”.
- This is a picklist value on the loan object.
Record Data
- This is the “x” of the “x”.
The “x” of the “x” must exactly match the “x” record data.
Product Data: Metadata and Record Data
Each “product catalog” has two components, “metadata” and “record data”.
Metadata
- What the user “sees”.
- This is a picklist value on the loan object.
Record Data
- This is the “backend name” of the “product catalog object”.
The “spelling” of the “product name” must exactly match the “product catalog” record data.
Product Catalog Configuration: High-Level Steps
Product catalog configuration must be completed in “x”.
- Access the “x” tool
- Click the “x” tab
- Add your “x”
- Update the “x” values
- Add “x”
Product Catalog Configuration: High-Level Steps
Product catalog configuration must be completed in “Salesforce Classic”.
- Access the “DM Admin” tool
- Click the “Products” tab
- Add your “product matrix”
- Update the “loan picklist” values
- Add “field dependencies”
Product Features: Overview
Product features help “x” a “x” further by assigning “x” to it.
By using product features you can specify whether a product is:
- “x”
- “x”
- “x”
- “x”
Product Features: Overview
Product features help “classify” a “product” further by assigning “additional attributes” to it.
By using product features you can specify whether a product is:
- “Secured”
- “Unsecured”
- “Syndication”
- “Participation”
Loan Stage: Overview
A loan stage is a representation of where the loan is in a financial institution’s “x”.
Reasons for using a loan stage?
- Track “x”
- Highlight “x”
- Manage “x” and “x”
Loan Stage: Overview
A loan stage is a representation of where the loan is in a financial institution’s “business process”.
Reasons for using a loan stage?
- Track “milestones”
- Highlight “ownership”
- Manage “Service Level Agreement” and “reporting”
Stages with Special Meaning in nCino: Booked
A loan can only be advanced to Booked once it has been “x” to the FI’s “x” and nCino has the “x” “x”
Stages with Special Meaning in nCino: Booked
A loan can only be advanced to Booked once it has been “boarded” to the FI’s “core system” and nCino has the “core system’s” “unique ID (loan number)”
Stages with Special Meaning in nCino: Complete
The purpose of the Complete stage is to flag loans that no longer require “x” by any user or admin at the FI.
Once the loan is marked as complete:
- No longer used in any “x”
- No longer appears in “x” for the active “x”
However, complete loan records are still available for “x”.
Stages with Special Meaning in nCino: Complete
The purpose of the Complete stage is to flag loans that no longer require “attention” by any user or admin at the FI.
Once the loan is marked as complete:
- No longer used in any “relationship statistics”
- No longer appears in “reports” for the active “loan portfolio”
However, complete loan records are still available for “future reference”.
Naming the nCino Loan Stages
- Names of all stages can be “x” to meet each FI’s needs
- nCino recommends keeping the changes to a “x” wherever possible.
- Maintaining the standard “x” and “x” across the client base enables the Support team to easily “x” and provide “x”.
Naming the nCino Loan Stages
- Names of all stages can be “customised” to meet each FI’s needs
- nCino recommends keeping the changes to a “minimum” wherever possible.
- Maintaining the standard “naming conventions” and “best practices” across the client base enables the Support team to easily “identify issues” and provide “quick solutions”.
Moving from One Stage to the Next
A loan object “x” and a Salesforce “x” (lightning) allow you to manually set a loan stage.
Best practice is not to enable “x” change. Set the stage field to “x” and disable the “x”. Some FI’s may allow a small group of users change the stage manually.
Moving from One Stage to the Next
A loan object “picklist field” and a Salesforce “path” (lightning) allow you to manually set a loan stage.
Best practice is not to enable “manual stage” change. Set the stage field to “read-only” and disable the “Salesforce path”. Some FI’s may allow a small group of users change the stage manually.
Stage Change Recommendation
Use a separate “x” for each “x” in the loan lifecycle that requires a user to “x” that the loan is ready to move to the next “x”.
Why is a “x” preferred?
They can be placed closer to other fields that may be required when a “x” appears.
Stage Change Recommendation
Use a separate “checkbox” for each “stage” in the loan lifecycle that requires a user to “manually confirm” that the loan is ready to move to the next “stage”.
Why is a “x” preferred?
They can be placed closer to other fields that may be required when a “validation error” appears.
Moving Back a Stage
A loan should not move back:
- Once the loan is in the “x” or “x” stage
- Once the loan has been “x”
- Once the loan has been marked as a “x”
Moving Back a Stage
A loan should not move back:
- Once the loan is in the “Booked” or “Complete” stage
- Once the loan has been “approved”
- Once the loan has been marked as a “complete application”
Status: Open
This indicates the loan is “x” and currently being “x”/”x” as part of an “x” portfolio.
The loan is not “x” or “x” but is available for action (“x” or “x”)
Status: Open
This indicates the loan is “in process” and currently being “worked”/”serviced” as part of an “active loan” portfolio.
The loan is not “paid off” or “charged off” but is available for action (“renewal” or “modification”)
Status: Hold
This status is used to indicate that the loan is “x” but cannot be “x”.
This is often due to an incomplete “x” or missing “x”.
Status: Hold
This status is used to indicate that the loan is “in process” but cannot be “moved forward”.
This is often due to an incomplete “credit application” or missing “documentation”.
Status: Decisioning
Indicates that the loan is actively being “x” by a “x”.
Status: Decisioning
Indicates that the loan is actively being “reviewed” by a “credit approver”.
Status: Withdrawn
Indicates that the “x” no longer wishes to “x” with his/her “x”.
Status: Withdrawn
Indicates that the “borrower” no longer wishes to “proceed” with his/her “credit application”.
Status: Declined
Indicates the “x” has decided not to “x” to the “x”.
Status: Declined
Indicates the “bank” has decided not to “extend credit” to the “borrower”.
Status: Superseded
Indicates that the “x” loan was “x” or “x”.
The new “x” or “x” has replaced the “x” loan.
Status: Superseded
Indicates that the “booked” loan was “modified” or “renewed”.
The new “modification” or “renewal” has replaced the “previous” loan.
Status: Paid Off
Indicates that the customer has “x” the entire “x” of the loan plus any “x”.
Therefore, the bank no longer needs to “x” the loan.
Status: Paid Off
Indicates that the customer has “repaid” the entire “principle balance” of the loan plus any “applicable interest”.
Therefore, the bank no longer needs to “service” the loan.
Status: Charged Off
Indicates that the loan is in “x” and the bank has “ceased” attempts to “x” the “x”
Status: Charged Off
Indicates that the loan is in “default” and the bank has “ceased” attempts to “reclaim” the “funds”
Product State Configuration: Overview
This is a tool that maps custom “x” & “x” values to the standard “x” and “x” values.
Why is it important?
- nCino runs “x” that checks for the “x” loan stage
Without Product State Configuration?
- “x” would need to be written to handle “x” nCino “x” & “x”
Product State Configuration: Overview
This is a tool that maps custom “stage” & “status” values to the standard “booked” and “closed” values.
Why is it important?
- nCino runs “logic” that checks for the “Booked” loan stage
Without Product State Configuration?
- “custom code” would need to be written to handle “non-standard” nCino “stages” & “statuses”
Product State Configuration: How does it work?
- Product State Config “x” are created on the “x” object
- The Product State Configuration “x” monitors “x”
- If Product State Configuration finds a loan in a stage that has been “x” to the standard nCino “x” or “x” stages. Then it recognises that loan as “x” and populates the background “x” and “x” fields with the current date.
Product State Configuration: How does it work?
- Product State Config “records” are created on the “Product Type” object
- The Product State Configuration “object” monitors “opportunity history”
- If Product State Configuration finds a loan in a stage that has been “mapped” to the standard nCino “booked” or “closed” stages. Then it recognises that loan as “booked” and populates the background “Booked Date” and “Closed Date” fields with the current date.
What is exposure?
The amount of credit extended to a borrower by a lender.
Proposed Exposure
- Loan is in a “x” stage, “x” stage
- The amount used is the “x” amount field on the “x”
Proposed Exposure
- Loan is in a “post-Qualification” stage, “pre-Approval” stage
- The amount used is the “original” amount field on the “loan”
Exposure Type: Committed
- Loan is in a “x” but “x” stage
- The amount used is the “x” amount field on the “x”
Exposure Type: Committed
- Loan is in a “post-approval” but “pre-booked” stage
- The amount used is the “original” amount field on the “loan”
Exposure Type: Booked
- Loan in the “x” stage
- The amount that the “x” still “x”
Exposure Type: Booked
- Loan in the “booked” stage
- The amount that the “borrower” still “owes”
Exposure Type: Total
- The sum of “x”, “x” and “x” exposure
Exposure Type: Total
- The sum of “booked”, “committed” and “proposed” exposure
Exposure Method: Direct Exposure
- “x” is related to the “x” as a “x” or “x”
Exposure Method: Direct Exposure
- “Entity” is related to the “loan” as a “borrower” or “co-borrower”
Exposure Method: Indirect Exposure
- “x” is related to the “x” as a “x” or “x”
Exposure Method: Indirect Exposure
- “Entity” is related to the “loan” as a “guarantor” or “limited guarantor”
Exposure Method: Affiliated Exposure
- “x” is related to the “x” as any “x” type with “x” or more ownership
Exposure Method: Affiliated Exposure
- “Entity” is related to the “loan” as any “borrower” type with “25%” or more ownership
Impact of Household on Exposure Calculation
Household membership impacts exposure calculation
- Household exposure includes the exposure of “x” of the “x”
- Booked Household Exposure, is the sum of the “x” for every “x” of the “x”
Impact of Household on Exposure Calculation
Household membership impacts exposure calculation
- Household exposure includes the exposure of “all the members” of the “household”
- Booked Household Exposure, is the sum of the “booked exposure” for every “member” of the “household”
Net New Funds
- This is the “x” in “x” from a loan “x”
- It’s a calculated field that represents the “x” between the “x” of the “x” and the “x” of the “x” or “x”
- This field is “x” any time there is a loan “x” or “x”
Net New Funds
- This is the “difference” in “loan amounts” from a loan “modification”
- It’s a calculated field that represents the “difference” between the “original amount” of the “booked loan” and the “new proposed loan amount” of the “renewal” or “modification”
- This field is “automatically populated” any time there is a loan “renewal” or “modification”
Exposure Configuration
Exposure “x” can be configure to calculate exposure for any combination of “x”
Example:
- “x” Proposed Exposure doesn’t include loans in the “x”.
- A bank could choose to include this stage in the Proposed Exposure calculations.
Exposure Configuration
Exposure “types” can be configure to calculate exposure for any combination of “loan stages”
Example:
- “OOTB” Proposed Exposure doesn’t include loans in the “qualification stage”.
- A bank could choose to include this stage in the Proposed Exposure calculations.
Total Exposure Admin Console
Here you can define “x” tailed to your banks needs.
Total Exposure Admin Console
Here you can define “calculations” tailed to your banks needs.
