JMP Global Operations validates accounts to confirm the correct legal entity at a specific address. Accounts must be submitted in Salesforce to be validated and approved as JMP First Accounts.
CPQ Basics
What are JMP First Accounts?
They are accounts that are run exclusively through JMP systems.
What can be submitted for account validations?
CPQ is for business-to-business transactions only. Legal entities are validated. A legal entity at a specific address can only have one account in Salesforce. We want to avoid duplicate accounts to keep our data clean. A salesforce record can have different contracts.
What are duplicate accounts?
Multiple Salesforce records with the same Account Name AND Shipping Address.
How do I avoid duplicate accounts?
Before submitting an account in Salesforce, conduct a search to determine if there already is a JMP First Account with the account name and shipping address you want to request.
How do I search for duplicate accounts in Salesforce?
- Type the legal entity name into the search bar.
- At the bottom of the search results, click on more results.
There are duplicate accounts. What should I do next?
There should be one record per company at a specific address. Multiple contracts can be associated with that Salesforce record.
If there is an account with the company at the specific address that has been approved and is marked as JMP first, use the JMP First account. Do not create a new account.
Account Validations
What sources are used to validate accounts via CPQ?
Global Operations utilizes multiple tools, including Duns & Bradstreet, customer website, Secretary of State (for US based accounts only), country specific business registration sites, etc., to confirm a legal entity at a specific address. If we are unable to validate, JMP Global Operations will reach out to the sales rep via Chatter for documentation.
Best practices for account validation and approvals:
- Account Name
- The Account Name is the full legal entity name of the customer that is utilizing the software at the validation address.
- Write the Account Name in English in proper case
- CORRECT EXAMPLE
JMP Statistical Discovery LLC
- INCORRECT EXAMPLES
- JMP
- Jmp
- JMP, LLC
- JMP LLC
- Jmp LLC
- Jmp Llc
- AKA Account Name (not a required field but could be used for the following)
- Legal entity’s trade style name
- Local language name
- Shipping Address
- Write address in English in proper case
- Include the following
- Street Name
- City
- State/Province
- (For US Only) Write State Names in Upper Case Abbreviations
- E.g. Massachusetts = MA
- Country
- Territory
- Ensure the account owner is with the correct territory requesting the account
- Ensure correct currency
Communication about Accounts
My account was flipped to “Waiting on Information.” Why is that?
The Global Operations team was unable to validate the account. Global Operations will tag the sales rep in Chatter requesting clarification or legal documentation.
What qualifies as legal documentation?
- W-9 (for US only)
- Business Certificate
- Financial tax records
- Bank statements
My account was flipped to “Descartes Review.” Why is that?
As part of the validation process, any Restricted Party Screening alerts will be reviewed. The Global Operations team will change the status to “Descartes Review” while it’s under review. The sales rep will be updated in Chatter if an alert is unable to be cleared and next steps.
Best practices to responding to Global Operations in Salesforce Chatter:
Always access Chatter through the account record. After clicking on the relevant account page on Salesforce, click on the Chatter tab. Do not respond to Chatter via email notifications as this communication isn’t tracked on the account.
How do you provide documentation provided by the customer verifying their legal name and address to Global Operations for account validations?
Respond in the corresponding account’s Chatter. Attach the document to the account under files. Then resubmit the account for approval so that it may pull back into the Account Approval Queue.
Very helpful! Thank you, Kayla.