Plan Administration: Building Compensation Plans

Plan Administration is Layer 1 of SAP SuccessFactors IM, and it's where your incentive strategy becomes executable. A plan defines the rules of compensation: who gets paid what for doing what. This lesson covers how to think about plans, structure them in SAP SuccessFactors IM, and prepare them for operational use.

What is a Compensation Plan?

A compensation plan is a formal document that specifies how participants earn incentive compensation based on their performance. In SAP SuccessFactors IM, a plan is a persistent object in the database (CSC_COMP_PLAN table) with a name, type, period range, and a set of configuration parameters that drive the calculation engine.

Every plan answers these questions:

• What performance metric is measured? — Orders, revenue, units sold, customer satisfaction, cost savings, etc.
• What is the target performance level (quota)? — Per participant, per period. $2M annual revenue, 100 units monthly, etc.
• How much is earned at target? — The base rate or tier structure. 2% commission on revenue, $500 per unit, $50K bonus at 100% attainment, etc.
• What happens above and below target? — Accelerators (earn more for over-quota performance), floor minimums (don't earn below 50% attainment), caps (don't pay above 200%), clawbacks (deductions for chargebacks).
• When does the plan apply? — The period range (e.g., Jan 1–Dec 31, 2026) and effective dates for participants (e.g., new hire starts March 15).

Plan Types in SAP SuccessFactors IM

SAP SuccessFactors IM supports several plan type templates, though custom types are also possible:

Commission Plans

The most common type. Participants earn a percentage or per-unit amount for each transaction. Example: 2% commission on all deals closed. The formula is straightforward: Result × Rate = Incentive. Commission plans scale with transaction volume and are used for direct sellers, channel partners, and account executives.

Example: A sales rep closes $2M in revenue against a $2M quota. With a 2% commission rate, they earn $40K.

Bonus Plans

A fixed bonus amount that scales with attainment. The plan defines a target bonus (e.g., $10K) and a tier structure that maps attainment percentages to payout percentages. Example: At 100% attainment, pay 100% of the bonus ($10K). At 75–100% attainment, pay 50% of the bonus ($5K). Below 75%, no bonus.

Example: A manager has a $30K target bonus. Their team achieves 120% attainment. The bonus tier says "above 100%, pay 100% + 25% accelerator," so they earn $37.5K.

Management by Objectives (MBO) Plans

Bonuses tied to achievement of qualitative goals, not just quantitative metrics. The IM system stores goal definitions and scores; the plan applies tiers based on the overall MBO achievement percentage. These require close integration with SAP SuccessFactors Performance Management for goal tracking.

Special Payment Funds (SPF) Plans

Discretionary bonus pools that are allocated to participants by managers or administrators. Example: A regional manager has a $100K pool to distribute among their team. Rather than a formula, the manager enters each team member's SPF allotment individually. IM tracks these allocations and produces statements.

Plan Periods and Effective Dating

Plans operate in time windows called periods. A period is the interval over which performance is measured and incentives are calculated. Common periods are:

• Monthly — 12 periods per year, for transaction-intensive businesses (retail, e-commerce)
• Quarterly — 4 periods per year, common for enterprise sales
• Annual — 1 period per year, for bonus and MBO plans
• Custom — Non-standard periods (e.g., "fiscal weeks" if the company uses a 4-4-5 calendar)

A plan period is defined in CSC_PLAN_PERIOD with:

• PERIOD_ID — Unique identifier (e.g., "2026-Q2", "2026-JULY")
• PERIOD_NAME — Human-readable label (e.g., "2nd Quarter 2026")
• START_DATE and END_DATE — The calendar range
• PLAN_ID — The plan this period belongs to

Effective dating is critical. A plan might have a global EFFECTIVE_START_DATE and EFFECTIVE_END_DATE (e.g., Jan 1, 2026–Dec 31, 2026), but individual participant assignments to the plan have their own effective dates (e.g., a new hire is assigned starting March 15, 2026). The pipeline respects these dates — it will not calculate results for a participant outside their assignment date range.

-- Query active plans with period dates
SELECT
  cp.ID              AS PLAN_ID,
  cp.NAME            AS PLAN_NAME,
  cp.PLAN_TYPE,
  cpp.PERIOD_ID,
  cpp.PERIOD_NAME,
  cpp.START_DATE,
  cpp.END_DATE,
  DATEDIFF(cpp.END_DATE, cpp.START_DATE) AS DAYS_IN_PERIOD,
  COUNT(DISTINCT cpa.PARTICIPANT_ID)
                     AS ASSIGNED_PARTICIPANTS
FROM   CSC_COMP_PLAN cp
JOIN   CSC_PLAN_PERIOD cpp
  ON  cpp.PLAN_ID = cp.ID
LEFT JOIN CSC_PLAN_PARTICIPANT cpa
  ON  cpa.PLAN_ID = cp.ID
  AND cpa.EFFECTIVE_START_DATE <= cpp.END_DATE
  AND cpa.EFFECTIVE_END_DATE >= cpp.START_DATE
WHERE  cp.EFFECTIVE_START_DATE <= CURRENT_DATE
  AND cp.EFFECTIVE_END_DATE >= CURRENT_DATE
GROUP BY cp.ID, cp.NAME, cp.PLAN_TYPE, cpp.PERIOD_ID, cpp.PERIOD_NAME,
         cpp.START_DATE, cpp.END_DATE
ORDER BY cp.NAME, cpp.START_DATE;

Plan Components: The Building Blocks

A plan is composed of smaller, reusable components. These are the pieces you configure to define how money flows:

Quotas

The performance target. Stored in CSC_QUOTA with a participant ID, plan ID, period ID, and quota amount. A sales rep might have multiple quotas: a $2M annual quota split into four $500K quarterly quotas. Quotas are the denominator in attainment calculations.

Rates and Rate Tables

The commission or bonus amount. A simple rate is "2% of revenue." A rate table is more complex: "1% on revenue 0–$500K, 1.5% on revenue $500K–$1M, 2% above $1M." Rate tables model progressive commission structures and are stored in a separate configuration table.

Rules and Tiers

Conditional logic. Example: "If attainment is 0–50%, pay 0%; 50–75%, pay 50% of base; 75–100%, pay 100%; 100%+, pay 100% + 25% accelerator." Tiers are stored in CSC_PLAN_TIER and evaluated by the calculation engine at result generation time.

Measures and Metrics

What is being measured. A measure might be "Q2 Revenue" or "New Customer Acquisitions." Measures are tied to credit transaction types — when a credit comes in labeled with a specific measure, the pipeline routes it to the appropriate plan component for calculation.

Modifiers and Adjustments

Special multipliers or deductions. Example: Regional modifier ("Americas reps earn 1.1x, EMEA reps earn 0.9x due to market differences"), product-line modifier ("high-margin products earn a 1.5x multiplier"), or manager override (a one-time adjustment to a participant's result).

Plan Hierarchy and Inheritance

Plans can have parent-child relationships. A parent plan might define baseline rates and tiers; child plans inherit and override specific components. This is useful for:

• Regional Variation — A global plan defines the structure; regional child plans override rates and quotas per geography.
• Product-Line Variation — A base commission plan; product-specific child plans adjust rates for high-margin vs. low-margin products.
• Role-Based Variation — Different rates for account executives vs. sales development reps on the same base plan.

Inheritance in SAP SuccessFactors IM is explicit: you define which components are inherited (via the INHERITANCE_RULE field) and which are overridden in the child plan. This is more flexible than Callidus's implicit inheritance model.

-- Complete plan inventory with assignment and quota stats
SELECT
  cp.ID              AS PLAN_ID,
  cp.NAME            AS PLAN_NAME,
  cp.PLAN_TYPE,
  cp.EFFECTIVE_START_DATE,
  cp.EFFECTIVE_END_DATE,
  COUNT(DISTINCT cpa.PARTICIPANT_ID)
                     AS ASSIGNED_PARTICIPANTS,
  COUNT(DISTINCT cq.PARTICIPANT_ID)
                     AS PARTICIPANTS_WITH_QUOTA,
  SUM(cq.QUOTA_AMOUNT)  AS TOTAL_QUOTA,
  ROUND(AVG(cq.QUOTA_AMOUNT), 2)
                     AS AVG_QUOTA_PER_PARTICIPANT
FROM   CSC_COMP_PLAN cp
LEFT JOIN CSC_PLAN_PARTICIPANT cpa
  ON  cpa.PLAN_ID = cp.ID
  AND cpa.EFFECTIVE_START_DATE <= CURRENT_DATE
  AND cpa.EFFECTIVE_END_DATE >= CURRENT_DATE
LEFT JOIN CSC_QUOTA cq
  ON  cq.PLAN_ID = cp.ID
  AND cq.PARTICIPANT_ID = cpa.PARTICIPANT_ID
WHERE  cp.EFFECTIVE_START_DATE <= CURRENT_DATE
  AND cp.EFFECTIVE_END_DATE >= CURRENT_DATE
GROUP BY cp.ID, cp.NAME, cp.PLAN_TYPE,
         cp.EFFECTIVE_START_DATE, cp.EFFECTIVE_END_DATE
ORDER BY cp.NAME;