Deprecated: See our developer documentation for updated resources

Warning: This tool is an advanced feature and should be used with the guidance of an experienced compensation plan expert.

The Compensation Plan XML page is where you create or edit your commission template using an EXtensible Markup Language (XML) editor.

Creating an entire compensation plan template can be complicated and confusing; however, the individual pieces are simple. When you combine the elements, you have infinite options to build your custom plan.

What We’ll Cover

Finding the XML Editor
Getting Started
Using XML
Main Outline for the Template
Defining Commission Period
Defining Volume Ranges
Defining Volumes
Defining Tree Volumes
Defining Pools
Defining Default Volume and Tree Volume
Defining Rules
Defining KPIs
Stats and Projected Commissions Template Names
Full Example Template

Finding the XML Editor

In Corporate Office, navigate to: Commissions > Compensation Plan XML.

[CLIENTID].corpadmin.directscale.com/Corporate/CRM/Commissions/ComPlanDesigner

Getting Started

The Compensation Plan XML page uses XML to describe compensation plans. Every template will begin with the line:

<?xml version="1.0" encoding="UTF-8"?>

This defines the XML version and the character encoding (8-bit Unicode Transformation Format (UTF-8)).

Next, we have to define the template. Templates are contained within the opening and closing <Template> tag.

<Template> 

</Template>

Using XML

Every element in an XML document must have a beginning and ending tag or begin and end within one tag:

<SetRank Rank="5" />

The “<SetRank>”tag above is self-closing because it ends with “/”. Meaning, it doesn’t need a separate “</SetRank>”closing tag.

This “<SetRank>”element also has an “attribute” named “Rank”. Attributes are used to set simple values for an element. For more complex values, elements are nested inside each other.

For example, the “<Template>”below has “<Rules>”within it. One of the rules is “`Name=” G2" Description=" Gold 2" ```, which has conditions required to meet. If those conditions are met, you will become a rank five associate:

<Template>
   <Rule Name="G2” Description="Gold 2">
        <And>
            <MeetsRule Rule="Active" />
            <MeetsRule Rule="G1" />
            <PVCondition Max="-1" Min="150" Volume="pqv" />
        </And>
        <Result>
            <SetRank Rank="5" />
        </Result>
   </Rule>
</Template>

In this example, the associate will need to meet the conditions (“<MeetsRule>”) for “= "Active" ``` and "=”G1" , as well as have a minimum of 150 ("`Min= "150") personal volume from “Volume=" pqv "```. These terms should be defined elsewhere in the "`”.

As you build your commission template, you will define the different types of volume, where they come from, and how they are earned. Then you can use these volumes later on in calculating payouts and determining what rank the associate has earned.

Main Outline for the Template

This guide will go through each element (“<ComPeriod>”through “<KPIs>”) and help you define a basic compensation plan.

<Template>
    <ComPeriod></ComPeriod>
    <VolumeRanges></VolumeRanges>
    <Volumes></Volumes>
    <TreeVolumes></TreeVolumes>
    <Pools></Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

Defining Commission Period

<Template>

    <ComPeriod Usage="CommissionRun, RealtimeStats" RoundPrecision="3" EnrollTree="Enrollment" TrackRealtimeRankAdvancements="False" Name="Monthly-Template">

        <VolumeRange>
            <VolumeRange Name="Monthly">
                <RangeType>
                    <Monthly StartOffset="0"  EndOffset="0" />
               </RangeType>
            </VolumeRange>
        </VolumeRange>
    </ComPeriod>

    <VolumeRanges></VolumeRanges>
    <Volumes></Volumes>
    <TreeVolumes></TreeVolumes>
    <Pools></Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

<ComPeriod> has general information about the template, such as the Name="" and <VolumeRange> (date range) included for each period. The “Name=" "``` here must match the name of the file in the **Template Selector** and must be the last attribute defined in "`”.

Note: the “<VolumeRange Name=”can’t be referenced directly. It will be used by default, but you can only use the “<VolumeRanges>”defined in the section below.

Defining Volume Ranges

“<VolumeRanges>”is mostly used for setting the date ranges to count volume.

<Template>
    <ComPeriod> . . . </ComPeriod>

    <VolumeRanges>
        <VolumeRange Name="First7DaysOfTheMonth">
            <RangeType>
                <MovingDays BeginDays="0" EndDays="7" />
            </RangeType>
        </VolumeRange>

        <VolumeRange Name="LastMonth">
            <RangeType>
                <Monthly StartOffset="1"  EndOffset="0" />
            </RangeType>
        </VolumeRange>
    </VolumeRanges>

    <Volumes></Volumes>
    <TreeVolumes></TreeVolumes>
    <Pools></Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

The “<VolumeRange>”in “<ComPeriod>”is the master default used by everything. It is “Monthly”with no offsets, meaning that it will only be looking at what has happened this month.

The “<VolumeRanges>”you set within this section are for when you want a separate range to count volume.

For example: if you gave for orders placed in the first week of every month double volume, you could define another range in this section for the beginning of every month and use it in the next section to sum up the volume. You can use the other range to count volume on orders placed in the previous month.

When you create “<VolumeRanges>,”you set the “`Name=” "``` to anything you want, and then you can use that name later on in the range.

The core part of the “<VolumeRange>”is the “<RangeType>”, there are multiple different “<RangeTypes>”available to use. In the example above, you can see “<Monthly>”and “<MovingDays>”used:

<RangeType>
    <Monthly StartOffset="1"  EndOffset="0" />
</RangeType>

<RangeType>
    <MovingDays BeginDays="0" EndDays="7" />
</RangeType>

All available <RangeTypes> can be found in the Documentation section of the Compensation Plan XML page, under the section RangeType.

Defining Volumes

In the “<Volumes>”section, you define the different kinds of volumes your plan needs to keep track of and how the volume is counted.

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>

    <Volumes>   
         <VA_Personal Name="QualifiedVolume" AssociateBaseTypes="1,2,3,4">
             <VolumeType>
                 <DefVolType VolumeGroup="QV" AssociateBaseTypes="1,2,3,4"/>
             </VolumeType>
         </VA_Personal>   

         <VA_Personal Name="pcv">
             <VolumeType>
                 <DefVolType VolumeGroup="CV" />
             </VolumeType>
         </VA_Personal>

       <Retail Name="Retail-Orders" VolumeRange="First7DaysOfTheMonth">
           <VolumeType>
              <DefVolType VolumeGroup="OrderCount" />
           </VolumeType>
       </Retail>
    </Volumes>

    <TreeVolumes></TreeVolumes>
    <Pools></Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

<Volumes> uses VolumeGroups="" to determine from where the volume comes. Possible options include:

Each volume defined will assign a value to each associate that can then be used to qualify them for a rank, calculate a commission bonus, or be displayed as a KPI. The names of the volumes are chosen by the compensation plan writer (i.e., "````) and are referenced later in the template.

<VA_Personal Name="QualifiedVolume" AssociateBaseTypes="1,2,3,4">
   <VolumeType>
       <DefVolType VolumeGroup="QV" AssociateBaseTypes="1,2,3,4"/>
   </VolumeType>
</VA_Personal>

“Name=" QualifiedVolume" ``` will track how much "VolumeGroup=”QV" each associate has earned from orders they have directly placed. As long as they areAssociateBaseTypes=“1,2,3,4”```.

<VA_Personal Name="pcv">
    <VolumeType>
        <DefVolType VolumeGroup="CV" />
    </VolumeType>
</VA_Personal>

“Name=" pcv "``` will track how much "VolumeGroup=”CV" ``` each associate has earned from orders they have directly placed, no matter what associate type they are.

<Retail Name="Retail-Orders" VolumeRange="First7DaysOfTheMonth">
    <VolumeType>
        <DefVolType VolumeGroup="OrderCount" />
    </VolumeType>
</Retail>

“Name=" Retail-Orders" ``` will count how many orders have been placed by the "`”customer below each associate.

All volumes will use the template’s “<ComPeriod>”“<VolumeRange>”if there are none specified. In this example template, each calendar month is a separate period. Name="QualifiedVolume" and Name="pcv" use the default range and will include volume from orders placed this month.

“Name=" Retail-Orders" ``` overrides the default range with "VolumeRange=” First7DaysOfTheMonth" ``` so it will only count the orders made in the first seven days of the month.

All available “<Volumes>”can be found in the Documentation section of the Compensation Plan XML page, under the Volume Accumulators section.

Defining Tree Volumes

“<TreeVolumes>”is different from the previous “<Volumes>”because they will sum up each person’s downline volume. The previous “<Volumes>”didn’t reference a tree; they assigned individuals values.

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>
    <Volumes> . . . </Volumes>

    <TreeVolumes> 
        <TreeVolume Name="GroupVolume" Tree="Unilevel" Volume="pcv" />
    </TreeVolumes>

    <Pools></Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

All you need to do is: - Name the new TreeVolume (e.g., <TreeVolume Name="">) - Reference a tree (e.g., <Tree="Enrollment, Unilevel, Binary, or Matrix">) - Reference a Volume="" defined in the previous section (e.g., Volume="pcv").

<TreeVolumes> 
    <TreeVolume Name="GroupVolume" Tree="Unilevel" Volume="pcv" />
</TreeVolumes>

Defining Pools

“<Pools>”are used to make payments.

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>
    <Volumes> . . . </Volumes>
    <TreeVolumes> . . . </TreeVolumes>

    <Pools> 
        <GVPaymentPool Name="MasterPool" TreeVolume="GroupVolume" GVPercent="100"  /> 
    </Pools>

    <PVAccumulator />
    <GroupVolumeTree />
    <Rules></Rules>
    <KPIs></KPIs>
</Template>

All you need to do is: - Define the <Pool> (e.g., <GVPaymentPool />). - Name the <Pool> (e.g., Name="MasterPool"). - Reference a <TreeVolume> defined above (e.g., TreeVolume="GroupVolume"). - Specify what percent of the volume will be used for this <Pool> (e.g., GVPercent="100").

<Pools> 
    <GVPaymentPool Name="MasterPool" TreeVolume="GroupVolume" GVPercent="100"  /> 
</Pools>

Defining Default Volume and Tree Volume

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>
    <Volumes> . . . </Volumes>
    <TreeVolumes> . . . </TreeVolumes>
    <Pools> . . . </Pools>

    <PVAccumulator Volume="pcv" />

    <GroupVolumeTree TreeVolume="GroupVolume" />

    <Rules> </Rules>
    <KPIs></KPIs>
</Template>

Defining Rules

This section is the largest and includes all of the logic for ranks and payments. A “<Rule>”is comprised of conditions required to meet that rule. “<Rules>”are typically used for qualifying and defining ranks and bonuses. Then they are referenced other rules as requirements that the associate or their downline have to meet.

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>
    <Volumes> . . . </Volumes>
    <TreeVolumes> . . . </TreeVolumes>
    <Pools> . . . </Pools>
    <PVAccumulator />
    <GroupVolumeTree />

    <Rules>
        <Rule Name="Active" Description="Qualified for payments">
            <And>
                <PVCondition Volume="QualifiedVolume" Min="100" Max="-1" />
            </And>
        </Rule>
    
        <Rule Name="Silver" Description="Silver level rank">
            <And>
                <MeetsRule Rule="Active" />
                <GVCondition TreeVolume="GroupVolume" Min="500" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />
            </And>
            <Result>
                <SetRank Rank="10" />
            </Result>
        </Rule>
    
        <Rule Name="Gold" Description="Gold level rank">
            <And>
                <MeetsRule Rule="Silver" />
                <GVCondition TreeVolume="GroupVolume" Min="1000" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />        
                <LegsWithRule Tree="Unilevel" RequiredLegs="2" Rule="Silver" PersonalSponsored="False" />
            </And>
            <Result>
                <SetRank Rank="20" />
            </Result>
        </Rule>

        <Rule Name="EB" Description="Early Bird order bonus">
            <And>
                <MeetsRule Rule="Active" />
                <PVCondition Volume="Retail-Orders" Min="2" Max="-1" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="EB bonus" Tag="" MetaData="">

                        <Group>
                            <CurrentAssociateGroup />
                        </Group>

                        <Source>
                            <FixedAmountPay Amount="5" Comment="Early Bird Bonus" GroupSize="0" OneTimeKey="" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>

        <Rule Name="SB" Description="Lvl 1 Silver">
            <And>
                <MeetsRule Rule="Silver" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="Lvl1 Silver Bonus" Tag="" MetaData="">

                        <Group>
                            <GenerationGroup Tree="Unilevel" Generation="1" CompressRule="" BeginLevel="1" />
                        </Group>

                        <Source>
                            <PVPay Volume="QualifiedVolume" Percent="10" Comment="[backofficeId] ([percent]% of [acrVolume])" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>

        <Rule Name="GB" Description="Lvl 2 Gold">
            <And>
                <MeetsRule Rule="Gold" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="Lvl2 Gold Bonus" Tag="" MetaData="">

                        <Group>
                            <GenerationGroup Tree="Unilevel" Generation="2" CompressRule="" BeginLevel="1" />
                        </Group>

                        <Source>
                            <PVPay Volume="QualifiedVolume" Percent="5" Comment="[backofficeId] ([percent]% of [QualifiedVolume])" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>

    </Rules>

    <KPIs></KPIs>
</Template>

Let’s break this into sections:

<Rule Name="Active" Description="Qualified for payments">
    <And>
        <PVCondition Volume="QualifiedVolume" Min="100" Max="-1" />
    </And>
</Rule>

This first “<Rule>”section determines a status used by other rules.

The next section of rules are for ranks:

<Rule Name="Silver" Description="Silver level rank">
    <And>
        <MeetsRule Rule="Active" />
        <GVCondition TreeVolume="GroupVolume" Min="500" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />
    </And>
    <Result>
        <SetRank Rank="10" />
    </Result>
</Rule>

<Rule Name="Gold" Description="Gold level rank">
    <And>
        <MeetsRule Rule="Silver" />
        <GVCondition TreeVolume="GroupVolume" Min="1000" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />        
        <LegsWithRule Tree="Unilevel" RequiredLegs="2" Rule="Silver" PersonalSponsored="False" />
    </And>
    <Result>
        <SetRank Rank="20" />
    </Result>
</Rule>

They have conditions and results, which set the rank. The first (<Rule Name="Silver" Description="Silver level rank">) is for the Silver rank, which requires you to be active (<MeetsRule Rule="Active" />) and have 500 group volume (Min="500").

The second <Rule> if for Gold rank (<Rule Name="Gold" Description="Gold level rank">), which requires Silver rank (<MeetsRule Rule="Silver" />) and 1000 group volume (Min="1000").

The last section is the “<Payments>”section, which defines what requirements are necessary to earn a payment, the group of associates that contribute a volume to the payment, and the details of how much you will get paid.

<Rule Name="EB" Description="Early Bird order bonus">
    <And>
        <MeetsRule Rule="Active" />
        <PVCondition Volume="Retail-Orders" Min="2" Max="-1" />
    </And>

    <Result>
        <Payments>
            <Payment Pool="MasterPool" Bonus="EB bonus" Tag="" MetaData="">

                <Group>
                    <CurrentAssociateGroup />
                </Group>

                <Source>
                    <FixedAmountPay Amount="5" Comment="Early Bird Bonus" GroupSize="0" OneTimeKey="" />
                </Source>

            </Payment>
        </Payments>
    </Result>
</Rule>

The above “<Rule>”is the simplest. The first qualification is to be “Active” (“<MeetsRule Rule= "Active"/>```) which was defined in the first "`”section:

<Rule Name="Active" Description="Qualified for payments">
   <And>
        <PVCondition Volume="QualifiedVolume" Min="100" Max="-1" />
   </And>
</Rule>

Next, they must have “Volume”of 2 (“Min= "2" ```) in ``` "Retail-Orders" ``` ("``), which we defined earlier as orders placed by retail associates under this distributor in the first week of the month in the "`”:

<Retail Name="Retail-Orders" VolumeRange="First7DaysOfTheMonth">
   <VolumeType>
      <DefVolType VolumeGroup="OrderCount" />
   </VolumeType>
</Retail>

Finally, if those conditions are met, the result is a $5 payment (“`<FixedAmountPay Amount=”5" ```):

<Result>
    <Payments>
        <Payment Pool="MasterPool" Bonus="EB bonus" Tag="" MetaData="">

            <Group>
                <CurrentAssociateGroup />
            </Group>

            <Source>
                <FixedAmountPay Amount="5" Comment="Early Bird Bonus" GroupSize="0" OneTimeKey="" />
            </Source>

    </Payment>

“<Group>”doesn’t have to specify anyone other than the associate that met the condition ("````).

Alternatively, we could have used the retail associates that placed the orders and reward a percentage of the order price or volume.

The last two payments are earning commissions based on their downline.

If you are a Silver rank:

<Rule Name="SB" Description="Lvl 1 Silver">
    <And>
        <MeetsRule Rule="Silver" />
    </And>

    <Result>
        <Payments>
            <Payment Pool="MasterPool" Bonus="Lvl1 Silver Bonus" Tag="" MetaData="">

                <Group>
                    <GenerationGroup Tree="Unilevel" Generation="1" CompressRule="" BeginLevel="1" />
                </Group>

                <Source>
                    <PVPay Volume="QualifiedVolume" Percent="10" Comment="[backofficeId] ([percent]% of [acrVolume])" />
                </Source>

            </Payment>
        </Payments>
    </Result>
</Rule>

Then you will get 10% (“`Percent=” 10 "```) of personal volume from the people directly below you in the Unilevel tree:

<Group>
    <GenerationGroup Tree="Unilevel" Generation="1" CompressRule="" BeginLevel="1" />
</Group>

If you are a Gold rank:

<Rule Name="GB" Description="Lvl 2 Gold">
    <And>
        <MeetsRule Rule="Gold" />
    </And>

    <Result>
        <Payments>
            <Payment Pool="MasterPool" Bonus="Lvl2 Gold Bonus" Tag="" MetaData="">

                <Group>
                    <GenerationGroup Tree="Unilevel" Generation="2" CompressRule="" BeginLevel="1" />
                </Group>

                <Source>
                    <PVPay Volume="QualifiedVolume" Percent="5" Comment="[backofficeId] ([percent]% of [QualifiedVolume])" />
                </Source>

            </Payment>
        </Payments>
    </Result>
</Rule>

Then you will get an additional 5% (“`Percent=”5" ```) of personal volume from the next level below that in the Unilevel tree:

<Group>
    <GenerationGroup Tree="Unilevel" Generation="2" CompressRule="" BeginLevel="1" />
</Group>

Adding Rank Values to the Database

For these ranks to apply, you’ll have to manually add the rank names (e.g., Gold) and values (e.g., 20) to the CRM_Ranks table in the Database using the Data Editor.

Read more: Using the Data Editor

In Corporate Office, navigate to: Administration > Data Editor.

https://[CLIENTID].corpadmin.directscale.com/Corporate/Admin/SQLEditor

Step-by-step guide: How To Add Compensation Plan Rank Values to the Database Using the Data Editor

Defining KPIs

This section is for any additional information that you want to be tracked and displayed:

<Template>
    <ComPeriod> . . . </ComPeriod>
    <VolumeRanges> . . . </VolumeRanges>
    <Volumes> . . . </Volumes>
    <TreeVolumes> . . . </TreeVolumes>
    <Pools> . . . </Pools>
    <PVAccumulator />
    <GroupVolumeTree />
    <Rules> . . . </Rules>

    <KPIs> 
        <TemplateKPI Key="PS" Description="Personal Sales Volume">
            <Accumulator>
                <VolumeSumAccumulator PersonalVolume="pcv" />
            </Accumulator>
        </TemplateKPI>
        <TemplateKPI Key="TS" Description="Team Sales Volume">
             <Accumulator>
                 <VolumeSumAccumulator TreeVolume="GroupVolume" />
             </Accumulator>
        </TemplateKPI>
    </KPIs>

</Template>

Stats and Projected Commissions Template Names

In Corporate Office, navigate to: Administration > Advanced Settings > Commissions.

https://[CLIENTID].corpadmin.directscale.com/Settings?category=Commission

Stats Template

To define your commission stats template:

Select one of your commission templates (Weekly, Monthly, Quarterly).
Define Usage="CommissionRun, StateStats, RealTimeStats" in the <ComPeriod>
Enter the template name in Stats Template Name in Administration > Advanced Settings > Commissions.

https://[CLIENTID].corpadmin.directscale.com/Settings?category=Commission

Stats Template Name

Projected Commissions Template

In Administration > Advanced Settings > Commissions.

https://[CLIENTID].corpadmin.directscale.com/Settings?category=Commission

Under the Commission Profiles section, to enable the associate to view their projected commissions in their Web Office > Pay History report, click the Enable Project Commissions checkbox.

In the Projected Template Names field, enter the template names/revisions included in projected commissions.

Full Example Template

<Template>

    <ComPeriod Usage="CommissionRun, RealtimeStats" RoundPrecision="3" EnrollTree="Enrollment" TrackRealtimeRankAdvancements="False" Name="Monthly-Template">

        <VolumeRange>
            <VolumeRange Name="Monthly">
                <RangeType>
                    <Monthly StartOffset="0"  EndOffset="0" />
               </RangeType>
            </VolumeRange>
        </VolumeRange>
    </ComPeriod>

    <VolumeRanges>
        <VolumeRange Name="First7DaysOfTheMonth">
            <RangeType>
                <MovingDays BeginDays="0" EndDays="7" />
            </RangeType>
        </VolumeRange>

        <VolumeRange Name="LastMonth">
            <RangeType>
                <Monthly StartOffset="1"  EndOffset="0" />
            </RangeType>
        </VolumeRange>
    </VolumeRanges>

    <Volumes>   
        <VA_Personal Name="QualifiedVolume" AssociateBaseTypes="1,2,3,4">
            <VolumeType>
                <DefVolType VolumeGroup="QV" />
            </VolumeType>
        </VA_Personal>   

        <VA_Personal Name="pcv" AssociateBaseTypes="1,2,3,4">
            <VolumeType>
                <DefVolType VolumeGroup="CV" />
            </VolumeType>
        </VA_Personal>

        <Retail Name="Retail-Orders" VolumeRange="First7DaysOfTheMonth">
            <VolumeType>
                <DefVolType VolumeGroup="OrderCount" />
            </VolumeType>
        </Retail>
    </Volumes>

    <TreeVolumes> 
        <TreeVolume Name="GroupVolume" Tree="Unilevel" Volume="pcv" />
    </TreeVolumes>

    <Pools> 
        <GVPaymentPool Name="MasterPool" TreeVolume="GroupVolume" GVPercent="100"  /> 
    </Pools>

    <PVAccumulator Volume="pcv" />

    <GroupVolumeTree TreeVolume="GroupVolume" />


    <Rules>
    
        <Rule Name="Active" Description="Qualified for payments">
            <And>
                <PVCondition Volume="QualifiedVolume" Min="100" Max="-1" />
            </And>
        </Rule>
    


        <Rule Name="Silver" Description="Silver level rank">
            <And>
                <MeetsRule Rule="Active" />
                <GVCondition TreeVolume="GroupVolume" Min="500" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />
            </And>
            <Result>
                <SetRank Rank="10" />
            </Result>
        </Rule>
        <Rule Name="Gold" Description="Gold level rank">
            <And>
                <MeetsRule Rule="Silver" />
                <GVCondition TreeVolume="GroupVolume" Min="1000" Max="-1" MaxPerLeg="-1" Level="-1" CompressRule="" IncludeCompressed="True" MaxPersonal="-1" />        
                <LegsWithRule Tree="Unilevel" RequiredLegs="2" Rule="Silver" PersonalSponsored="False" />
            </And>
            <Result>
                <SetRank Rank="20" />
            </Result>
        </Rule>



        <Rule Name="EB" Description="Early Bird order bonus">
            <And>
                <MeetsRule Rule="Active" />
                <PVCondition Volume="Retail-Orders" Min="2" Max="-1" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="EB bonus" Tag="" MetaData="">

                        <Group>
                            <CurrentAssociateGroup />
                        </Group>

                        <Source>
                            <FixedAmountPay Amount="5" Comment="Early Bird Bonus" GroupSize="0" OneTimeKey="" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>
        <Rule Name="SB" Description="Lvl 1 Silver">
            <And>
                <MeetsRule Rule="Silver" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="Lvl1 Silver Bonus" Tag="" MetaData="">

                        <Group>
                            <GenerationGroup Tree="Unilevel" Generation="1" CompressRule="" BeginLevel="1" />
                        </Group>

                        <Source>
                            <PVPay Volume="QualifiedVolume" Percent="10" Comment="[backofficeId] ([percent]% of [acrVolume])" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>
        <Rule Name="GB" Description="Lvl 2 Gold">
            <And>
                <MeetsRule Rule="Gold" />
            </And>

            <Result>
                <Payments>
                    <Payment Pool="MasterPool" Bonus="Lvl2 Gold Bonus" Tag="" MetaData="">

                        <Group>
                            <GenerationGroup Tree="Unilevel" Generation="2" CompressRule="" BeginLevel="1" />
                        </Group>

                        <Source>
                            <PVPay Volume="QualifiedVolume" Percent="5" Comment="[backofficeId] ([percent]% of [QualifiedVolume])" />
                        </Source>

                    </Payment>
                </Payments>
            </Result>
        </Rule>



    </Rules>

    <KPIs> 
        <TemplateKPI Key="PS" Description="Personal Sales Volume">
            <Accumulator>
                <VolumeSumAccumulator PersonalVolume="pcv" />
            </Accumulator>
        </TemplateKPI>
        <TemplateKPI Key="TS" Description="Team Sales Volume">
             <Accumulator>
                 <VolumeSumAccumulator TreeVolume="GroupVolume" />
             </Accumulator>
        </TemplateKPI>
    </KPIs>

</Template>

Compensation Plans

Creating a Basic Compensation Plan

What We’ll Cover

Finding the XML Editor

Getting Started

Using XML

Main Outline for the Template

Defining Commission Period

Defining Volume Ranges

Defining Volumes

Defining Tree Volumes

Defining Pools

Defining Default Volume and Tree Volume

Defining Rules

Adding Rank Values to the Database

Defining KPIs

Stats and Projected Commissions Template Names

Stats Template

Projected Commissions Template

Full Example Template

Comments

Compensation Plans

What We’ll Cover

Finding the XML Editor

Getting Started

Using XML

Main Outline for the Template

Defining Commission Period

Defining Volume Ranges

Defining Volumes

Defining Tree Volumes

Defining Pools

Defining Default Volume and Tree Volume

Defining Rules

Adding Rank Values to the Database

Defining KPIs

Stats and Projected Commissions Template Names

Stats Template

Projected Commissions Template

Full Example Template

Related articles