Product Package Flashcards

1
Q

Product Package Definition & Features

Product Package is a feature of the nCino bank operating system that allows users to package “x” together for an “x”.

A

Product Package Definition & Features

Product Package is a feature of the nCino bank operating system that allows users to package “multiple loans” together for an “approval submission”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Product Package: Definition & Features

Here are the key features:

  • “x” data from multiple loans into a “x”
  • Takes “x” or conducts “x” on “x” loans simultaneously.
  • Submits “x” for approval “x”..
  • Supports “x” loan structures
  • Supports “x” to loans from “x”.
A

Product Package: Definition & Features

Here are the key features:

  • “Summarises” data from multiple loans into a “Credit Memo”
  • Takes “Credit Actions” or conducts “reviews” on “multiple” loans simultaneously.
  • Submits “multiple loans” for approval “simultaneously”..
  • Supports “multi-tiered” loan structures
  • Supports “bulk updates” to loans from “Product Package”.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Product Package Use Cases: Organic/Life

Duration:
- This PP is used for the “x” of a “x”

Concept:
- “x” is aligned to “x”

Status:
- The PP is “x” and is a “x”, “x” entity.

Loan Life:
- The loans in such a PP are “x” and added upon one another. Other “x” reside in the same package.

A

Product Package Use Cases: Organic/Life

Duration:
- This PP is used for the “life” of a “relationship”

Concept:
- “One relationship” is aligned to “one product package”

Status:
- The PP is “ever changing” and is a “living”, “breathing” entity.

Loan Life:
- The loans in such a PP are “compounded” and added upon one another. Other “potential loans” reside in the same package.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Product Package Use Cases: Transactional

Duration:
- This PP has “x” for a “x”

Concept:
- “x” is aligned to “x”

Status:
- The PP is “x” and is “x”

Loan Life:
- The “x” loans are added “x” to the PP. Other “x” reside in separate packages within a relationship.

A

Product Package Use Cases: Transactional

Duration:
- This PP has “individual deals” for a “relationship”

Concept:
- “One relationship” is aligned to “many PP’s”

Status:
- The PP is “deal specific” and is “static”

Loan Life:
- The “deal-specific” loans are added “once” to the PP. Other “potential loans” reside in separate packages within a relationship.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Product Package: Option to Use

It’s up to the bank. But the process of “x” used in a bank helps to decide which PP to use.

When to use Organic?
- If a bank “x” all loans on a “x” at “x”.

When to use Transactional?
- If a bank “x” “x”.

Note:
- nCino would typically recommend the “x” due to the nature of the “x” enhancements on each release.

A

Product Package: Option to Use

It’s up to the bank. But the process of “reviews” used in a bank helps to decide which PP to use.

When to use Organic?
- If a bank “reviews” all loans on a “relationship” at “the same time”.

When to use Transactional?
- If a bank “reviews” “individual deals”.

Note:
- nCino would typically recommend the “transactional type” due to the nature of the “product development” enhancements on each release.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Total Loan Facilities Amount

This field can be “x” to include only loans in “x”

A

Total Loan Facilities Amount

This field can be “configured” to include only loans in “specific statuses”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Bulk Updates Overview

This allows users to update “x” simultaneously, instead of updating one “x” at a time.

Bulk update can be configured to “x” on any “x” within the nCino UI.

A

Bulk Updates Overview

This allows users to update “multiple records” simultaneously, instead of updating one “record” at a “time”.

Bulk update can be configured to “update records” on any “object” within the nCino UI.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

3 Ways to add/associate a Loan to a PP

(1) Converting from a “x” or an “x”
(2) Looking up an “x” loan to add to the package via “x”
(3) Creating a new loan via the “x” button on the “x”

A

3 Ways to add/associate a Loan to a PP

(1) Converting from a “lead” or an “opportunity”
(2) Looking up an “existing” loan to add to the package via “Manage Facilities”
(3) Creating a new loan via the “new facility” button on the “Product Package”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Product Package: Gold Standards

  • PP supports grouped “x”. If a relationship has multiple loans, submitting these for “x” individually creates inefficiencies for both the “x” and the “x”.
  • A PP supports “x” credit “x”. If a FI doesn’t use PP, then a user cannot represent a complex, “x” credit “x” in nCino.
  • Improve efficiency and end “x” by using nCino’s digital “x”.
  • Don’t assume a banks core can support “x”. Ensure you understand the process used by a bank to map the “x” loans and the “x” loans when “x” data.
A

Product Package: Gold Standards

  • PP supports grouped “loan approvals”. If a relationship has multiple loans, submitting these for “approval” individually creates inefficiencies for both the “submitter” and the “approver”.
  • A PP supports “multi-tiered” credit “structures”. If a FI doesn’t use PP, then a user cannot represent a complex, “multi-tiered” credit “structure” in nCino.
  • Improve efficiency and end “paper processes” by using nCino’s digital “Credit Memo”.
  • Don’t assume a banks core can support “complex structures”. Ensure you understand the process used by a bank to map the “master” loans and the “sub” loans when “migrating” data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Product Package: Required Configuration

  • Enable Product Package in nCino “x”
  • Update the PP “x” route
  • Provide the required “x” and required “x”
  • Configure the “x” list
A

Product Package: Required Configuration

  • Enable Product Package in nCino “UI layout”
  • Update the PP “Borrowing Structure” route
  • Provide the required “nFORCE” and required “LLC_BI System Properties”
  • Configure the “Pending Facility” list
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Product Package: Optional Configuration

  • Enable the optional “x” and optional “x”
  • Configure the “x” for the PP object
  • Provide “x” on the “x” tree
  • Define the “x” of “x” feature
A

Product Package: Optional Configuration

  • Enable the optional “nFORCE” and optional “LLC_BI System Properties”
  • Configure the “stage horizontal” for the PP object
  • Provide “edit labels” on the “hierarchy” tree
  • Define the “dependent structures” of “product” feature
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Product Package: Additional Configuration

  • Configure the “x” functionality.
  • Configure the PP “x”.
  • Configure “x”
A

Product Package: Additional Configuration

  • Configure the “Convert to nCino (PP)” functionality.
  • Configure the PP “Credit Memo”.
  • Configure “Credit Actions”
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Multi-Tiered Loans Overview

A multi-tiered loan is a loan that has been broken down into a hierarchy of “x” and “x” records.

These are common across the FI industry, for both “x” and complex “x” loans.

They allow banks to provide “x” to borrowers because they “x” the allowed “x” of the funds.

A

Multi-Tiered Loans Overview

A multi-tiered loan is a loan that has been broken down into a hierarchy of “parent” and “child” records.

These are common across the FI industry, for both “consumer” and complex “commercial” loans.

They allow banks to provide “better terms” to borrowers because they “narrow” the allowed “usage” of the funds.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Multi-Tiered Loans Characteristics: Approvals

Usually, the approval process is configured to “x” approvals from the “x” throughout the facility “x”.

It’s also possible to approve a “x” and then add multiple tiers, such as “x” and “x” to the facility structure.

A

Multi-Tiered Loans Characteristics: Approvals

Usually, the approval process is configured to “propagate” approvals from the “main loan” throughout the facility “hierarchy”.

It’s also possible to approve a “main facility” and then add multiple tiers, such as “limits” and “sublimits” to the facility structure.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Multi-Tiered Loans Characteristics: Exposure

Limits, sub-limits and takedowns are commonly excluded from exposure calculations. As the exposure for the “x” has already been calculated.

The ability to exclude these structure levels is available via “x”.

A

Multi-Tiered Loans Characteristics: Exposure

Limits, sub-limits and takedowns are commonly excluded from exposure calculations. As the exposure for the “main facility” has already been calculated.

The ability to exclude these structure levels is available via “custom settings”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

New Limit/Sub/Takedown Fields

Structure Level:
- This field displays the records “x” in the “x”

Borrower Type:
- This is auto-populated based on “x”. Don’t modify this.

A

New Limit/Sub/Takedown Fields

Structure Level:
- This field displays the records “level” in the “hierarchy”

Borrower Type:
- This is auto-populated based on “parent loan”. Don’t modify this.

17
Q

Importing Complex Deal Structures

Doing this from “x” can be done. But don’t assume they’ll be in the correct “x”.

A

Importing Complex Deal Structures

Doing this from “core systems” can be done. But don’t assume they’ll be in the correct “format”.

18
Q

Approval Process: Overview

This automates “x” in Salesforce. It also specifies each “x” of the approval process, including “x” to request approval “x” and what to do at each point of the process.

The nCino objects that use an approval process are:

  • “x”
  • “x”
  • “x”
  • “x”
  • “x”

A standard loan processed in nCino typically goes through “x” approval processes.

A

Approval Process: Overview

This automates “record approval” in Salesforce. It also specifies each “step” of the approval process, including “who” to request approval “from” and what to do at each point of the process.

The nCino objects that use an approval process are:

  • “Loan”
  • “Memo”
  • “Product Package”
  • “Adverse Action”
  • “Risk Rating Review”

A standard loan processed in nCino typically goes through “multiple” approval processes.

19
Q

nCino Approval Process Types

“x” Propagation and “x” Propagation.

“x”:
- Approval occurs at the “x” level. The “x” then trickles “x” to “x”.

“x”:
- Approval occurs at the “x” level. The “x” then propagates “x” to the “x”.

A

nCino Approval Process Types

“Standard” Propagation and “Reverse” Propagation.

“Standard”:
- Approval occurs at the “PP” level. The “process” then trickles “down” to “loans”.

“Reverse”:
- Approval occurs at the “loan” level. The “process” then propagates “up” to the “PP”.

20
Q

Approve a Product Package

Once the PP is submitted for approval, the “x” displays on the “x” route on the “x”.

Navigate to “x”. Approve or reject from here.

Note: The user who submits the record for approval, has the option to “x” the approval request.

A

Approve a Product Package

Once the PP is submitted for approval, the “approval request” displays on the “Approval History” route on the “PP”.

Navigate to “Approval History”. Approve or reject from here.

Note: The user who submits the record for approval, has the option to “recall” the approval request.

21
Q

Approval Process: Best Practices

  • “x” the approval process to “x” where a “x” is being made.
  • For “x”, it’s advisable to “x” to one “x” per “x”.
A

Approval Process: Best Practices

  • “Limit” the approval process to “objects” where a “business decision” is being made.
  • For “loans”, it’s advisable to “limit approvals” to one “process” per “product line”.
22
Q

Approval Process: Key Considerations

  • “x” v “x” approval - consider whether the bank requires “x”.
  • “x” selection of approvers versus “x” of the entire approval process.
    • Build-in approval grid(s)
    • Manage approval authority levels in nCino
    • Implement validation rules for approver selection.
A

Approval Process: Key Considerations

  • “Loan” v “PP” approval - consider whether the bank requires “both”.
  • “Manual” selection of approvers versus “automation” of the entire approval process.
    • Build-in approval grid(s)
    • Manage approval authority levels in nCino
    • Implement validation rules for approver selection.
23
Q

Renewal and Modification Overview

Banks use these to “change” the “terms” of the loan after it has been “booked” to the “core”.

A renewal is an “extension” of the “maturity date” of the loan, often “90 days” or more into the future.

Modifications are changes to the “rate”, “term”, “loan amount” or any loan “attribute”, which could also include the “maturity date”.

“No Action” is an nCino specific term as opposed to an “industry” term. This action is typically used when working with “multi-tiered” credit structures. When this action is taken, the “loan’s terms” don’t change.

A

Renewal and Modification Overview

Banks use these to “change” the “terms” of the loan after it has been “booked” to the “core”.

A renewal is an “extension” of the “maturity date” of the loan, often “90 days” or more into the future.

Modifications are changes to the “rate”, “term”, “loan amount” or any loan “attribute”, which could also include the “maturity date”.

“No Action” is an nCino specific term as opposed to an “industry” term. This action is typically used when working with “multi-tiered” credit structures. When this action is taken, the “loan’s terms” don’t change.

24
Q

Once a credit action is taken?

A

A new loan record is created in nCino

25
Q

Credit Action: Benefits

Provides a “x” view of the customer’s “x”.

Supports “x” and “x” hierarchy.

Provides a complete picture of “x” and “x” history.

A

Credit Action: Benefits

Provides a “real time” view of the customer’s “loans”.

Supports “bulk actions” and “multi-tier” hierarchy.

Provides a complete picture of “renewal” and “modification” history.

26
Q

Renewal and Modification Configuration

For these to work, “x” are configured and the “x” section is added to the “x”.

If a bank is using loan modifications, a “x” needs to be added.

Include “x” or “x” loans as part of “x”.

“x” a record based on “x” and “x”.

A

Renewal and Modification Configuration

For these to work, “CFG_ConfigValues” are configured and the “Loan Renewal and Modification” section is added to the “page layout”.

If a bank is using loan modifications, a “related list” needs to be added.

Include “renewed” or “modified” loans as part of “calculated exposure”.

“Lock” a record based on “stage” and “status”.

27
Q

Credit Review: Overview

This is a “x” of a client/customers “x”.

Banks typically conduct “x” to refresh their customers’ “x”.

If a customers ability to repay has significantly changed, the bank may work with the customer to “x” the debt in order to reduce “x” for both parties.

A

Credit Review: Overview

This is a “periodic assessment” of a client/customers “financial health”.

Banks typically conduct “annual credit reviews” to refresh their customers’ “risk profiles”.

If a customers ability to repay has significantly changed, the bank may work with the customer to “restructure” the debt in order to reduce “risk” for both parties.

28
Q

nCino Credit Review Process

This enables a bank to:

  • Initiate a “x” from a “x”
  • Initiate a “x” from a “x”
  • Select the loans to be “x” without necessarily taking any action on them.

This allows the end users to view the “x” they want to “x” without creating a “x” of the loan records.

A

nCino Credit Review Process

This enables a bank to:

  • Initiate a “Credit Action” from a “PP”
  • Initiate a “Review” from a “Relationship”
  • Select the loans to be “Reviewed” without necessarily taking any action on them.

This allows the end users to view the “loans” they want to “review” without creating a “clone” of the loan records.

29
Q

nCino Credit Review Process Flow

  • A review is initiated from the “x” by using the credit action “x” action.
  • The review record details can be edited, however the details included in the review are accessed and “x” through other “x”.
  • Based on a PP approval process and when the PP is in the final review step, there is a “x” to update the review status to “x”.
A

nCino Credit Review Process Flow

  • A review is initiated from the “PP” by using the credit action “wand” action.
  • The review record details can be edited, however the details included in the review are accessed and “edited” through other “objects”.
  • Based on a PP approval process and when the PP is in the final review step, there is a “trigger” to update the review status to “complete”.
30
Q

Credit Review: Required Configuration

  • Configure reviews for either a “x” or a “PPx.
  • Ensure that “x” and “x” match.
  • Configure the review “x”.
  • Configure the “x” picklist
  • Configure “x” “x”
  • Configure the review “x”
  • Configure “x” for review “x”
  • If configuring credit review for a relationship, “x” on the “x” Page and add “x” and “x” on the relationship page layout.
A

Credit Review: Required Configuration

  • Configure reviews for either a “relationship” or a “PP”.
  • Ensure that “page layouts” and “record types” match.
  • Configure the review “page layout”.
  • Configure the “review type” picklist
  • Configure “LLC_BI” “System Properties”
  • Configure the review “approval process”
  • Configure “alerts/tasks” for review “frequency”
  • If configuring credit review for a relationship, “disable reviews” on the “PP” Page and add “buttons” and “fields” on the relationship page layout.
31
Q

Credit Review: Optional Configuration

  • Check “x” assignments
  • Add the review “x” to the relationship page layout
  • Remove the review option from the “x” picklist menu
  • Configure “x”
  • Configure “x” for PP, loan and relationship information.
A

Credit Review: Optional Configuration

  • Check “page layout” assignments
  • Add the review “button” to the relationship page layout
  • Remove the review option from the “credit action” picklist menu
  • Configure “page layout”
  • Configure “field sets” for PP, loan and relationship information.
32
Q

Bulk Update Configuration

When configuring this, the option is displayed to either allow or restrict “x”.

The credit action “x” must be properly altered to enable “x”.

A

Bulk Update Configuration

When configuring this, the option is displayed to either allow or restrict “cascading credit actions”.

The credit action “cascading system property” must be properly altered to enable “cascading credit actions”.