Deal registration helps identify potential conflicts between partners and ensures that the same deal is not claimed by multiple partners. It enables partner managers to review, approve, or reject deals submitted by partners, maintaining transparency and fairness across the partner ecosystem.



When a deal registration requires approval from Partner Managers, the submitted record goes through a validation and conversion process before becoming an actual Account and Deal record in the system. Learn more about Deal Registration here.

 Steps to configure Deal Registration 

Before partners can start registering deals, you must first configure Deal Registration. The Deal Registration module becomes available to partners only after the Deal Registration configuration is completed.

To configure Deal Registration:

1. Go to Setup.

2. Under PRM, select Deal Registration.

3. Complete the configuration in the following four steps.

 1. Module Mapping 

Module mapping defines what happens when a deal registration is approved.

When a partner submits a deal and it gets approved:

• A new Deal record is created

• And an Account record is created only if the customer type is New Customer. If the deal is registered for an existing customer, a new Account record is not created.

To enable this conversion:

1. Choose  Account module: Select the Accounts module or any other module in your organization that should act as the Account record for approved deal registrations.

2. Choose Deals/Opportunities module: Select the Deals module or any other module that should store approved deal registrations.

   
   
   
   
   By default, organizations use the standard Accounts and Deals modules. However, you can map custom modules if your CRM setup requires it.

The selected modules determine where approved deal registrations are created and maintained.

3. Click Save and Next.

 2. Configure Conflict Settings
 

Conflict settings help detect duplicate records and prevent overlapping deal ownership. In this step, you define how the system should identify conflicts.

Select fields and modules for conflict detection

1. Choose the field used for duplicate detection: By default, Email only is selected as the field type for detecting conflicts.
   You can change this setting to:

• Phone only

• Email or Phone
  

Changing the field type resets existing conflict settings for all modules except Deal Registrations and Accounts. Click Update and Save to apply the change.

2. Review the modules included for conflict detection.
   
   By default, the Accounts module is included. Additional modules can be added based on where the selected field values are stored in your organization.
   
   
   The system compares the selected field values from deal registrations against existing records in the selected modules. If a matching value is found, the registration is flagged as a conflict.
   
   For example, if Email or Phone is selected as the conflict field and the Accounts module does not store email values, you can include another module where email information is maintained to ensure accurate conflict detection.
   

Add Module for Finding Duplicates (Optional)

Use this option to include additional modules when detecting duplicate records during deal registration.

Duplicate finding module information

1. Module Name to Search for Duplicates: Select the module where the system should check for duplicate records.

2. Email Field Name: Select the field in the chosen module that stores email information. If multiple email fields are available, choose the one used for primary communication.

3. Phone Field Name: Select the field in the chosen module that stores phone values.

The system compares these field values with the information submitted in the deal registration to identify potential conflicts.

Related module information (optional)

Use this section to display additional information related to matched records in the duplicate records view.

1. Related Module Name: Select a module that is related to the duplicate-finding module to display additional information in the duplicate records view.

For example, if Contacts is used to find duplicates, you can select Deals to view deals associated with the matched contact.

2. Duplicate record lookup in related module: This lookup field appears after a related module is selected. Use it to choose the field that links the related module records to the matched duplicate record.

3. Criteria for related module records: Once a related module is selected, a Criteria field appears. Use it to define conditions for fetching related records.

Important note

The related module is used only to fetch and display linked information for matched records. It is not used to detect duplicates.

When to use this option

Add a module for finding duplicates when:

• The default module does not contain the selected conflict field

• Email or phone information is stored in a different module

• You want better visibility into related records during conflict review
  

3. Click Add Module.
   

4. Map the Email and Phone fields in the selected module.
   

5. Click Save and Next to continue.
   

3. Configure Conversion Settings

Conversion settings define how approved deal registrations are converted into CRM records.

Map Deal Registration fields to the appropriate fields in the Accounts and Deals modules so that all relevant information is automatically carried over during deal conversion.

Map fields for deal registration conversion

Review the list of fields available in the Deal Registration module.

1. For each field you want to map during conversion, select the corresponding field in the Accounts and/or Deals modules.

2. Fields can be mapped to:

• Accounts

• Deals

• Both, depending on how the data should be stored

3. By default, one field is automatically mapped to each target module (Accounts and Deals) to meet the minimum requirement for conversion. You can modify or add mappings as needed.
   

To avoid incomplete records, it is recommended to map all relevant fields such as names, contact details, and deal values.

Note: Once a field is mapped, it cannot be mapped to another field.

4. Review the mapped fields to confirm that the data will be transferred correctly during conversion.

5. Click Save and Next to continue.
   

What happens after conversion

When a deal registration is approved:

• The mapped fields are transferred to the corresponding Account and Deal records

• Unmapped fields are not carried over

• The created records remain associated with the partner who registered the deal.

4. Assign a Deal Registration Reviewer

1. You must select a Deal Registration Reviewer for the partner program.
   
   

The reviewer is responsible for:

• Reviewing submitted deal registrations

• Verifying deal details

• Ensuring compliance with partner policies

• Identifying and resolving conflicts

• Approving or rejecting deal submissions

Note: You can add up to 20 reviewers, and all reviewers must have the Admin profile.

2. Click Save to complete the configuration.

After you click Save, a confirmation message is displayed indicating that the deal registration has been configured.

You’re then redirected to the configuration page, where all configured settings are displayed.


Email Field and Domain Settings

In addition to email and phone-based duplicate checks, you can also configure domain-level conflict detection.

• You can list domain names (for example, company domains).

• The system uses these domains to identify potential duplicate or conflicting deals.
  

This helps prevent multiple partners from registering deals from the same organization.

Next step:

• Manage Deal Registrations and Resolve Conflicts - Learn how to review submissions and take action on conflicts.