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”