Advanced
What-if scenarios
Model a plan change before rollout: project a hypothetical sale with What-If, or replay past sales under new rates or a draft plan without touching any ledger.
updated: applies-to: 1.2.0.0
Bitta Commission lets you ask "what would happen if" before you change a plan or chase a deal. Commission What-If projects what extra sales would earn one participant, and Commission Scenarios replays credited sales from a historical window under changed rates or a draft plan version, so you can compare total cost, gains and losses, and fairness. Both belong to the Simulation and forecasting module and write only their own results: no source fact, earning, balance, settlement or G/L entry is created.
Before you start
- Switch on the Simulation and forecasting module in Commission Feature Management. While it is off, creating a scenario stops with BAA-FEATURE-OFF and the simulation pages are not offered in search. See Optional modules.
- Creating, freezing and replaying scenarios requires the Bitta Commission Setup Administrator permission set or a Finance (all participants) user scope. Other users get BAA-SIM-SCOPE.
- On Commission What-If you can choose only participants within your own commission scope.
- A scenario replays credits that already exist, so calculate at least one period first. See Calculate commission.
Project a participant's earnings
- Search for Commission What-If and open it. As Of Date defaults to the work date, and when your scope covers exactly one participant, that participant is filled in.
- Fill in the inputs:
| Field | What to enter |
|---|---|
| Participant No. | The participant to model. |
| As Of Date | The date used to pick the plan version, period and rates. |
| Hypothetical Additional Sales (LCY) | The extra credited base to add to period-to-date attainment. Enter a negative value to model a return. |
| Expected Customer Payment Date | The payment date assumed for payment-triggered eligibility. |
- Choose Project Earnings. Nothing is written.
- Read Projected Additional Earnings and the line per component: Period-To-Date Base, Period-To-Date Earned, Projected Base, Projected Cumulative Entitlement, Estimated Commission, Effective Rate %, Quota Target, Attainment After %, Eligibility Trigger, Expected Eligible Date and Explanation.
For a ranking, contest, bonus or other component that earns only at period close, Calculated at Period Close is selected and Period Close Entitlement shows what the close would pay on the results posted so far.
Scenario kinds
| Action on Commission Scenarios | What it models |
|---|---|
| New Ghost Rule Scenario | Replays production credits with component rate overrides or a uniform rate adjustment. Hidden from participants and never paid. |
| New Shadow Plan Scenario | Replays production credits against a draft plan version. |
| New Plan Simulation | Compares a proposed plan version with the live definition over a historical window. |
Build and replay a scenario
- Open Commission Scenarios and choose one of the New actions. The Commission Scenario card opens in Draft, with a fact window from the first day of the month two months before the work date through the work date.
- Enter a Name and a Description of the purpose and assumptions.
- In Definition, check Fact Window From and Fact Window Through. Rates are read as of the through date.
- Use the assist button on Baseline Plan Version to pick the live version whose credits you replay, or leave it blank to replay every credited plan.
- For shadow and plan scenarios, pick a Comparison Plan Version. Its components replace the live ones by matching component code.
- For a ghost rule, enter Rate Adjustment % (10 means ten percent higher on every rate cell), or add lines in Rate Overrides: choose the component and enter Override Rate (decimal) between 0 and 1, for example 0.05 for five percent. An override takes precedence over the adjustment for its component.
- Choose Freeze Inputs. The app validates the window, the comparison version and the adjustment, records an Input Hash and sets the status to Input Frozen.
- Choose Replay. The app recalculates the arithmetic over the credited bases in the window and stores per-participant results and statistics. The status becomes Completed, or Completed with Exceptions when some rows could not be replayed.
To change a frozen or replayed scenario, choose Reopen: it returns to Draft and its results are cleared. Archive retires a scenario you no longer need.
The replay covers Flat Rate, Flat Amount, Per Unit, Progressive Tier, Retroactive Tier and Formula components, plus any other model the model catalog marks as previewable. Period-close components are not re-priced: both sides keep the entitlement the period close recorded for the window.
Line Rate components are not replayed: their rows carry BAA-SIM-MODEL, and on Commission What-If the Explanation says the model can't be previewed. To see the commission of a Line Rate component on an open document, use the line estimate. See Estimated commission and Line rates and margin pools.
Read the results
The Financial impact group shows Credited Facts Replayed, Total Credited Base, Baseline Payout, Scenario Payout, Payout Delta, Baseline Payout Ratio %, Scenario Payout Ratio % and Cost per Revenue Unit. Behavioral and fairness signals shows Participants Modeled, Participants Gaining, Participants Losing, Payout Ratio Dispersion and Exception Count.
- Results opens Scenario Results, one row per participant and component plus a participant total. Ledger Earnings in Window and Replay minus Ledger compare the replay with what the ledger recorded; a gap means the window cuts across period accumulation. Calculation Trace opens the trace of the recorded earning behind a row.
- Financial and Behavioral Impact opens Scenario Impact and Fairness with total payout, payout ratio, cost per revenue, payout bands, gains and losses, and the component mix.
- Fairness View shows payout ratio mean, dispersion, minimum and maximum across participants, teams and territories.
NOTE
Fairness statistics are suppressed for cohorts with fewer than three participants with credited base. Gains and losses are modeled associations, not causal promises.
Compare two scenarios
- On a scenario, choose Compare With, or choose Compare Scenarios on the list.
- On Scenario Comparison, choose Scenario A and Scenario B, then choose Compare.
- Review Total A, Total B and B minus A, and per participant the payouts under each scenario, the difference, the percent change, the rank in each scenario and participants present in only one of them.
Check Grain Check first: totals over different fact windows are not comparable.
Validation messages
The first four codes stop the action. The component codes are written to the Explanation of the affected result row instead.
| Code | Meaning |
|---|---|
| BAA-SIM-WINDOW | The fact window needs a from date and a through date, with from not later than through. |
| BAA-SIM-COMPARISON | Plan and shadow scenarios need a comparison plan version. |
| BAA-SIM-ADJUSTMENT | The rate adjustment must be greater than -100 percent. |
| BAA-SIM-STATUS | The scenario is in a status that does not allow the action, for example overrides changed outside Draft. |
| BAA-SIM-MODEL | A component uses a model the replay does not simulate. |
| BAA-SIM-LIVE-RATE, BAA-SIM-COMPARE-RATE | A component has no rate table at the end of the fact window. |
| BAA-SIM-COMPARE-COMPONENT | The comparison version has no component with a live component's code. |
Each row with a component problem is counted in Exception Count, and the rest of the replay continues. For other limits of the module, see Known limitations.
What's next
Look forward instead of back: Payout forecast.