How does your data fit into the system?
Gather all of your data that is used to calculate commissions. Some examples are outputs from your CRM software, accounting software, excel spreadsheets, etc.
To calculate a payment you need...
1. Unique ID: Every deal in the system needs to have an ID that is unique. No line within the same Compensable Event can have the same Order ID. See the below example for what is not an acceptable unique ID.
|Opportunity ID||Product ID||Product Name||Opportunity Split ID||Owner||Amount|
All of the columns that are highlighted blue have repeating values and will produce an error message if identified as the Order ID in your import. Possible solutions include:
- Concatenating Columns: Concatenating two columns on a report often produce a unique ID. For example, the Opportunity ID and the Opportunity Split ID would produce a unique identifier in the table above. This is the best approach.
- Create your own Unique ID: If nothing in your data is unique, your own naming convention can be used to create uniqueness. It is suggested to use the date followed by a numbering system. For example, deals in December 2019 would start with 1219 and then a 1, 2, so on so forth.
2. Date: What date will determine when payment/attainment is generated?
3. Owner: Who is receiving credit for this deal? If multiple people are receiving credit for the deals see below.
- Multiple people via rollup or hierarchy? If the hierarchy stays consistent (meaning the managers will always get credit for the same people/group of people), see the lookup table section on how to create the rollup.
- Deals are split between multiple reps: If splits are a common occurrence, and the split percent is consistent between reps, list all of the reps on the same line. For example: the columns Split Rep 1, Split Rep 2, etc. If the percents are not consistent, also include the percent assigned to each associated person.
4. Deal Information: Look at your quotas and payment rules. If quotas or payment rules are tied to a specific subset of deals within your data, additional information is needed on your import. For example: New deals are paid out at a certain payment rate and recurring deals are paid out through a different payment rate. What field can you import that would differentiate between new and recurring deals? Some example of columns that help identify deals include:
- Type: Software, Services, etc.
Deal Year: New, Year 1, Year 2, Recurring
Where do I upload my data?
Identify which setup applies to your data...
- I have only one data source. Import into a compensable event.
- Both of my imports have nothing to do with each other and they both generate their own payments. Import both into Compensable Events.
- I have two (or more) sources of data. Each of the sources provide some of the components outlined above in the "To calculate a payment" section. One of the imports will go into a compensable event. One will go into a lookup table.
- The reports will have to have one field in common that links the two. The compensable event can bring in information from the lookup table using lookup logic.It is suggested to use the unique ID as the connecting field. Refer to the lookup table capabilities section of the Data system overview for more information on lookup table logic.
- The compensable event import should contain the date that will generate attainment and/or payments.