Deal registration needs configuring before partners can use it. The Deal Registration module only becomes available to partners once configuration is complete. When a registration needs approval, the submission is validated and converted into an Account and a Deal before it becomes a real record in the system.

Go to Setup, choose Deal Registration under PRM, and complete the four steps below.

1. Module Mapping

This defines what happens when a registration is approved. A new Deal record is always created. An Account record is created only if the customer type is New Customer; for an existing customer, no new Account is created.

1. Choose the Account module: Accounts, or another module that should act as the Account record.
2. Choose the Deals or Opportunities module: Deals, or another module that should hold approved registrations.
3. Click Save and Next.

Most organisations use the standard Accounts and Deals modules, but custom modules can be mapped if your setup needs it.

2. Conflict Settings

Here you define how duplicates and overlapping ownership are detected.

The Field Used to Detect Duplicates

By default this is Email only. You can change it to Phone only, or Email or Phone.

The Modules Searched

Accounts is included by default. The system compares the chosen field values on a registration against existing records in the selected modules, and flags a match as a conflict. If Accounts doesn't store email or phone values, add another module where they are kept.

Adding a Module for Finding Duplicates (Optional)

• Module to search. The module to check for duplicates.
• Email field and Phone field. The fields in that module holding those values. If it has several email fields, choose the one used for primary communication.

Use this when the default module lacks the conflict field, when email or phone live in a different module, or when you want better visibility into related records during conflict review. Click Add Module, map the fields, and click Save and Next.

Related Module Information (Optional)

This shows extra information about matched records in the duplicate records view. Pick a related module (for example Deals, if Contacts is used to find duplicates, to see deals linked to the matched contact), the lookup that links the two, and criteria for which related records to fetch.

3. Conversion Settings

These define how an approved registration becomes CRM records. Map each Deal Registration field you want carried over to a field in Accounts, Deals, or both.

• One field is mapped to each target module by default, which is the minimum needed for conversion. You can change or add mappings.
• Map everything relevant, such as names, contact details, and deal values, to avoid incomplete records.
• Once a field is mapped, it can't be mapped to another field.
• Unmapped fields are not carried over. The created records stay associated with the partner who registered the deal.

4. Assign a Deal Registration Reviewer

You must choose at least one reviewer. Reviewers check submitted registrations, verify the details, ensure they comply with partner policies, identify and resolve conflicts, and approve or reject submissions. You can add up to 20 reviewers, and all of them must have the Admin profile. Click Save to finish. A confirmation appears and you return to the configuration page, which shows every setting.

Domain-Level Conflict Detection

In addition to email and phone checks, you can list company domain names, which the system uses to spot potential duplicate or conflicting deals. This helps stop several partners registering deals for the same organisation.