Bitta Commission guide

Plans, versions, and assignments

Build a commission plan and its versions, take them through Draft, Validate, Submit, Approve and Publish, and maintain plans with successors and stewardship.

status: verified applies-to: 1.1.2.0rev: 1

A commission plan describes how a group of participants earns commission. Each plan has governed versions, and each version holds the components, rates, calculation periods and assignments that apply for its dates. This page explains the plan lifecycle, how to build and publish a version, and how to maintain plans over time.

Before you start

  • You need the Bitta Commission Plan Designer permission set (BAA Comm Plan Dsgnr) to author plans, and a different user with the Bitta Commission Approver permission set to approve them.
  • An active plan approval policy must exist. The core includes a single-approver policy; see Approvals and notifications.
  • Participants and at least one open commission period should exist. See Participants and payees and Calendars and periods.

The quickest way to create a first plan is the guided setup wizard or an industry template. Both create normal Draft plans that you continue on the pages below.

The plan lifecycle

A plan version moves through these statuses:

Status Meaning
Draft The version can be edited.
In Review The version was submitted and waits for approval. It can return to Draft.
Approved An independent approver approved it. It can be published, or returned to Draft with a change reason.
Published The version is published and its assignments are active.
Active The version is in use. It can be suspended with a reason.
Suspended Use of the version is paused.
Superseded, Expired The version was replaced or reached its end.
Archived The version is archived.

The Next Action field on the plan card and the version card always explains the next governed step: Draft, Validate, Submit, independent Approve, then Publish.

Create a plan

  1. Open Commission Plans and choose New Plan.
  2. On Edit Commission Plan, enter the Code, Description, Purpose, KPI Description, Review Date, Retirement Criteria, Calendar, Business Owner and Technical Owner, and the Effective From and Effective To dates of the first draft.
  3. Choose OK. The plan and its first Draft version are created.

Edit Plan on the plan card changes stewardship and purpose while every version is still Draft.

Build a Draft version

On Commission Plans, choose Open Current Version to open Commission Plan Version.

  1. Components. Choose Components, then New Component to add one or more components. Each component has a model, a measure basis, a weight and its own rates. See Percent of sales, margin, and per unit, Tiered rates and Advanced models.
  2. Assignments. Choose Assignments to see who the version applies to, and create assignments on Commission Plan Assignments with New Assignment. An assignment targets a participant or a position and has dates, an allocation percent, a conflict policy and a priority. Native posted sales need one effective 100 percent assignment for the credited participant in the plan version.
  3. Calculation Periods. Choose Calculation Periods and Add Calculation Period so every assigned participant and component is tracked through the periods the version covers.
  4. Credit Splits (optional). Share a salesperson's sales with partner participants. See Crediting rules, splits, and overrides.

Edit Draft changes the effective dates and change reason while the version is Draft. Plan Details opens the plan purpose, owners and governance fields.

Validate, submit, approve and publish

  1. Choose Validate. Validation checks the governed definition without changing its status. If there are findings, Plan Validation lists each one with a severity, a code and a description. Choose Open Definition to jump to the component or rate schedule that needs fixing.
  2. Choose Submit. The version moves to In Review.
  3. The approver opens Approve: My Work Queue (the Commission Approval Work Queue) and approves. The requester cannot approve their own request.
  4. Choose Publish. Publishing checks that the validated definition has not changed, that approval evidence is complete, and that participants whose country policy requires a signed agreement have one. The version becomes Published and its assignments become active.

The version card shows the evidence: Definition Hash, Validation Evidence Hash, Blocking Validation Count, Approval Complete and Approval Evidence Hash, plus lifecycle dates such as Submitted At, Approved At and Published At.

NOTE

Published definitions are immutable. To change rates or components, create a successor version.

Change a published plan

  1. On the version card, choose Create Successor and enter the successor dates.
  2. The successor starts as Draft with copies of the independent components, policies, rates and draft assignments.
  3. Add the new calculation periods, adjust what changed, and take it through validation, approval and publication again.

Compare Versions compares a version with its predecessor in a read-only, field-level report. Suspend pauses an active version with a reason.

To roll a plan into next year, Copy Plan to Next Year on the Bitta Commission Setup Checklist copies the latest published version to next year as a Draft successor with the same components, rates and assignments.

Plan stewardship and reviews

Every plan has an accountable owner and a review date.

  • Plan Stewardship (from Stewardship on the plan card) names the Plan Owner and Steward, an owner participant, an escalation contact, notes, and the review cadence in months. Mark Reviewed Today records a review and moves the next review date forward by the cadence.
  • Plans Due for Review lists plans whose next review date has arrived. Show All lists every plan with stewardship. Escalate Overdue Reviews sends each overdue plan to its escalation contact once per review date.

Effective assignments and conflicts

A participant can be covered by several assignments. Effective Plan Assignments shows, for a participant and date, which assignments apply after conflict resolution, including assignments inherited through a position. Assignments on different plans always stack. Within a plan, the conflict policy (for example Stack, Exclusive, Priority or Most Specific) decides which assignment wins, and the page explains each outcome.

Plan documents and packages

  • Preview Plan Document shows the plan document. Draft, review and approved versions are watermarked and cannot be delivered.
  • Distribute Plan Documents delivers the document to every assigned participant of a published version. See Plan distribution and acceptance.
  • Export Reference Package and Export Embedded Package export the governed definition. Import as New Plan and Import as New Version import a package as a Draft.

What to check if it goes wrong

Message What to do
BAA-PLAN-STATE The requested status change is not allowed. Follow Draft, Validate, Submit, Approve, Publish.
BAA-WFL-POLICY Exactly one effective approval policy with complete stages is needed. Review Commission Approval Policies.
BAA-WFL-SELFAPPROVAL Another user must approve.
Validation findings Open Plan Validation and fix each finding.

Commission Plan Version card for a Draft version
Commission Plan Version card for a Draft version

The version card explains the next governed step and shows the evidence.

// next step

Ready to try Bitta Commission?