What is a Compensable Events Table?

Compensable Events is the raw data you import into the system and use to drive the payout for your users. Typically, this data can be Orders, Bookings, Revenue, Churn, or any other data needed. Data can be imported or manually entered into the system. Once data is created in a Compensable Event table it can be filtered and made commission ready via creating a Compensable Report.   

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. 

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? It is not required that you identify the owner on the Compensable Event itself. Below are ways in which people can get credit for a specific deal. 

• Direct Assignment: The data will explicitly identify the user that should get credit for the given deal. This information should either match user information or can leverage a Lookup Table to match and return the user record. 
• Rollup / Hierarchy: If the hierarchy stays consistent (meaning the managers will always get credit for the same people/group of people), a Lookup Table can be created to manage the credit assignment.
• Regional Assignment: If the Compensable Event information includes a Region field, a Lookup Table can be created to manage the relationship between Region and User assignment.
• Team Assignment: If a specific Compensable Event is assigned to one user who is part of a larger team and shares credit to other users on that team, a Lookup Table can be created to manage the relationship between Region and User assignment.
• Other Methods: Lookup Table are the most common way to handle credit assignment rules. The important factors to keep in mind is that the Compensable Event line item will need to include the proper reference data to assign credit to a given user.
• Split Deals: Within the Rule Mapping screen, more than one data column from the Compensable Events table can be used to assign credit. If using this option, you can select the field and either hard code a percentage or select a corresponding Value column. 

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. 
  Territory 
  Deal Year: New, Year 1, Year 2, Recurring
  Account Name
   

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.

Compensable Event Table Options

On each row there is an option menu. These options apply to that specific row only. Below is an overview of the various options:

• Create Compensable Report: Will create a Compensable Report that is linked to the Compensable Event table. Compensable Reports allow you to filter and add additional columns to your Compensable Events. Once done, you can map your Report to your Plans.
• Delete: Will delete the entire table (including all data within the table).
• Delete All Rows: Will delete all rows of data in the table (the structure of the table will not be impacted).
• Rename: Rename the selected Lookup Table. No underlying data will be impacted.
• Upload: Upload new rows to the Lookup Table. Since there is no unique key concept on a Lookup Table, all rows will be inserted regardless if there is a duplicate.

Working with a Compensable Event Table

When viewing aCompensable Event Table, you can easily edit the structure of the table itself or add/edit/delete the data within the table. 

Compensable Event Table Options:

• Create a Column: Will insert a new column in the Compensable Event Table. You will be able to name the Column and select the column type (Text, Currency, Date, Number, or Percent).
• Insert a Row: Create a new row of data within the Compensable Event Table. 
• Upload Data: Upload new rows to the Compensable Event Table. Compensable Event Tables have a unique key (Order ID). As such, when importing data into a Compensable Event Table we check for duplicates and give you the option to either update the original transaction or ignore the duplicates.
• Search: Will show a search bar at the top of each column and allow you to search within the column. The search type is a 'contains' style search (meaning it will match on any value you type regardless of where it is in the string). For dates and numbers it is an exact match.