Setting up application to contract mapping

  • Updated

Setting up application to contract mapping

You must map the fields of the CL product in Q2 Origination to the fields of the corresponding loan or lease product in CL Loan or CL Lease to enable the conversion of applications to contracts that can be serviced through CL Loan. 

The mapping of fields and objects is also used at the time of renewing a contract mapped to an application in Q2 Origination. 

In order to map the rate schedule fields, you must create distinct mappings for flexible loans and LOC loans. For example, you must create two sets of mappings for the following Q2 Origination application fields (genesis__Applications__c object), one for flexible loans, and the other for LOC loans:

  • genesis__Rate_Schedule_Setup__c.genesis__Start_Date__c

  • genesis__Rate_Schedule_Setup__c.genesis__Interest_Rate__c

  • genesis__Rate_Schedule_Setup__c.genesis__Sequence__c

  • genesis__Rate_Schedule_Setup__c.Floating_Rate_Index__c

  • genesis__Rate_Schedule_Setup__c.Margin_Rate__c

When you initiate conversion of an application to a contract, the Loan.ContractProcessor class retrieves these mappings and provides these as inputs to the loanAccountAction class class in CL Loan, which eventually creates the contract in CL Loan.

Before starting to define the mapping, navigate to the Application custom object and make note of the API names of all the fields you want to copy over to the contract during the conversion. Next, note the API names of these fields within the CL Contract object in CL Loan.

Child Objects: During conversion mapping, in addition to the fields of the Application and CL Contract object, you can map child objects, like, the disbursement schedule and its fields. If Disbursement Schedule is mapped, this is used at the time of disbursal of the CL contract. Similarly, any custom fields you have added to an application can also be incorporated into or mapped to existing or new custom fields in CL Loan. Child objects are of two types:

  • Type 1: This is a child object that is used in both, the application and the contract. For example, a Party. For Type 1 child objects, you do not need to map each field of the object. You can directly specify the object name in the mapping. The type of child relation in this case is Other.

  • Type 2: A child object that is available only in the application, but not in the contract. For Type 2 child objects, the child object has to be created in CL Loan. Each field of the object in the application is mapped to the field in the contract one by one. Therefore, a conversion mapping must be defined for each field of the child object. For example, Collateral in Q2 Origination. You need to create a child object in CL Loan and map it to the Collateral field of the application. Each field of Collateral would be mapped using the convention collateral API name.<field name>. 

For the mapping to be complete, you must also map the required CL product of Q2 Origination to the corresponding lending product of CL Loan. If you want to copy the CL Purpose, you must similarly map the CL Purpose between the two. Alternatively, this mapping can be defined through the field level conversion mapping. 

Example of Type 1 child object conversion mapping

In the following image, the Party object in Q2 Origination (clcommon__Party__c) is mapped to the Party (clcommon__Party__c) object in CL Loan.

Example of Type 2 child object conversion mapping

In the following image, the Value field of the Collateral object in Q2 Origination (clcommon__Collateral__c.clcommon__Value__c) is mapped to the Value (Collateral__c.Value__c) field of the new object Collateral in CL Loan. 

Prerequisites

The following are the prerequisites to setting up the conversion mapping:

  • Q2 Origination 1.2001 and CL Loan 1.2002 or higher versions are installed.

  • CL Product is set up in Q2 Origination.

  • The lending Product is set up in CL Loan.

Steps

  1. Log in to your Salesforce account.

  2. Go to Origination Configuration > Company and Application Setup, and Conversion Setup.

  3. Select Conversion Mapping Header.

  4. Select New and select Loan, Line of Credit, Lease, or Package from the Product Type list and specify the Custom Contract Generation Class name.

  5. Go to Related and select New in the Conversion Mapping section.

  6. In the New Conversion Mapping window, specify the mapping for each field one by one.

    1. Specify the Product Type. This is the type of application that you are converting. For example, a Loan, Line of Credit, or Package.

    2. Specify the Target Object Name. This is the API name of the contract's object to which the mapped field belongs.

    3. Specify the Target Field Name. This is the corresponding API name of the field of the CL Loan lending product to which you want to map the application field name.

    4. Specify the Source Object Name. This is the API name of the application's object to which the mapped field belongs.

    5. Specify the Source Field Name. This is the API name of the field of the Q2 Origination application that you want to map.

    6. Select the Required For Conversion checkbox if this field is mandatory for the conversion of the application. If you select this, and a value for this field is not provided, an error is displayed during the conversion of the application to a contract.

    7. Specify the Type of child relation in case you are mapping child objects of the application and CL contract. The options include None, Disbursal Distribution, Rate Schedule, and Other.

    8. Select the Use For Renewal checkbox if this field is mandatory for renewing the related loan contract.

    9. Select Save to save this mapping.

  7. Repeat step 4 to map all the required fields.

  8. Map the CL Product in Q2 Origination to the Lending Product in CL Loan. 

    1. Go to Origination Configuration > CL Product.

    2. Select the CL product to be mapped. The CL Product Detail page is displayed.

    3. In the Lending Product field, select the product from the list of lending products in CL Loan to map to the CL product.

      Note:

      At the time of implementing Q2 Origination, a lookup field on CL Product from CL Loan or CL Lease product must be created and added to the page layout.

    4. Select Save. 

  9. Perform step 6 to map the CL Purpose in Q2 Origination to the Loan Purpose in CL Loan.

  10. Map a custom field Status to Convert to the Loan Status field of the contract. For example, the Application Field Name is Status_to_Convert__c, and the Contract Field Name is loan__Loan_Status__c. 

  11. Associate the CL Loan class for contract generation in the Custom Logic Parameters. Refer to the Converting Applications to Contracts procedure in the Q2 Origination User Guide for steps to do this.

While defining the conversion mapping for child objects, ensure that:

  • No two fields with the same API name (ignoring namespace) in an object are mapped.
  • The type of the application's Field Name and the CL contract's Field Name is the same. For example, both must be text fields, or both must be lookup fields of the same object.
  • You create a lookup for CL Contract on the Application object so that upon successful conversion, this field is updated with the ID of the newly created CL contract.

In case any of the above fields are not displayed in your application's user interface, refer to the Converting Applications to CL Contract procedure in the Appendix of this guide that describes the UI changes and Salesforce setups that you must do and the procedures for doing these, to be able to fully use the conversion functionality. 

Field reference

Field NameDescription
Source Field Name

The API name of the Q2 Origination application's field that is to be mapped. For example, genesis__Interest_Rate__c, for the Interest Rate field.

Target Field NameThe API name of the corresponding field of the CL contract in CL Loan is being mapped. For example, loan__Contractual_Interest_Rate__c, for the Interest Rate field in the CL contract.
Required For ConversionIndicates whether the mapped field is mandatory for converting the application to a CL contract. If this is selected, the system displays an error in case a value for this field is not specified during conversion.
Use For RenewalIndicates whether the mapped field is mandatory for renewing a contract created from the related application.
Source Object NameThe API name of the Q2 Origination application's object whose field is mapped.
Target Object NameThe API name of the corresponding object of the CL contract in CL Loan whose field is mapped.
Product TypeIndicates the type of product for which the application is created. For example, a Loan, Line of Credit, Lease, or Package.
Note:

On converting the Package application, only the Package application should get converted. The child application should get converted independently, just like a loan application, by selecting a button on the child application. And if the status of the child application is not Closing Document Generated and the status of the Package application is Closing Document Generated, the package application can be converted.

Type of child relation

Indicates the relationship between the CL Contract or the Application object and the field being mapped.

None: If the field belongs to the CL Contract object.

Rate Schedule: If the field is used in the Rate Schedule

Disbursal Distribution: If the field is used to define the disbursal distribution and schedule

Other: For any other field that is a child object for the application and the contract or that belongs only in the application and is being copied over to the contract.

In This Article