Skip to content

Create a commission plan

A commission plan sets what performance is measured against and how the commission rate steps up as attainment rises. One plan can serve a whole sales team, because individual targets are set separately against it.

Required role: Administrator.

Create an active earning pay element for the commission to pay into. The element is what sets how the payout is taxed and whether it enters the social-insurance base, so a plan cannot be finished without one.

  1. Go to Payroll → Commission Plans.

  2. Select New plan.

  3. Enter a Plan name.

    Example: UK Sales Commission.

  4. Set the Legal entity, or leave it as All entities.

  5. Choose the Currency.

  6. Choose what the plan is Measured on.

  7. Choose the Attainment period and the Payout timing.

  8. Choose the Pay element the commission pays into.

  9. Under Who it reaches, set the criteria.

  10. Build the Commission ladder, using Add band for each band.

  11. Select Save plan.

OptionDescription
RevenueAttainment is revenue against target. Commission is the rate percentage applied to revenue.
UnitsAttainment is units against target, such as deals, renewals, or installs. Units carry no money on their own, so you also set what one unit is worth.

Example: HC Corp UK Ltd’s Sales department runs a revenue plan in GBP. A plan counting renewals instead would need a value per unit, because a renewal count is not an amount.

OptionDescription
MonthlyPerformance is scored against target every month.
QuarterlyPerformance is scored against target every quarter.
OptionDescription
Paid in the same periodThe computed payout reaches the payslip for the period it was earned in.
Paid the following periodThe payout reaches the next period’s payslip.
Paid at quarter endThe payout reaches a payslip at quarter end.

Targets are set in the plan’s currency and payouts are paid in it. A plan only reaches employees paid in that same currency, because there is no exchange rate anywhere in Humavera. An entity-scoped plan takes its currency from its entity.

Example: a GBP plan reaches HC Corp UK Ltd’s sales team. It does not reach anyone employed by HC Corp Inc. and paid in USD — they need their own plan.

Each band starts where the previous one ends, so there are no gaps, and the top band is always open-ended so over-performance always earns.

Example: a ladder reading 0–80% pays 2%, 80–100% pays 4%, and 100% and above pays 6% means a seller at 90% of target earns at 4%.

Humavera restates the ladder back to you as a sentence as you build it. Read that sentence before saving — it is the fastest way to catch a band that does not mean what you intended.

A plan naming an entity beats an all-entities plan inside that entity. Criteria under Who it reaches combine with AND, so every filter you set must be true of the employee, and setting none reaches everyone in scope paid in the plan’s currency.

A plan pays nothing on its own. It defines the shape; each person’s target is set on the plan’s targets table, per period, and commission is only calculated once actual attainment is recorded against those targets. Deleting a plan leaves targets already set on record and changes nothing already paid.