Skip to main content
When a commission number or status looks wrong, follow this checklist to quickly isolate whether the issue is plan selection, a missing eligibility gate, or bad/missing source data — and how to prove it in Core8.

​
When to use this

  • A deal looks wrong and you need a step-by-step checklist.
  • A deal is Waiting and you need to identify what’s missing.
  • You need to gather evidence to share with support or stakeholders.

​
Step 1: Confirm you’re looking at the right deal and period

  • If the deal was split, confirm whether you should be reviewing the child deals (most calculations happen on children).
  • Make sure the selected period matches the deal’s anchor/selection timing.
  • See: Deal Splitting

​
Step 2: Validate the input data (variables)

Check the variables that drive most plans:
  • amount fields (TCV / commissionable base)
  • deal type (new/renewal/expansion)
  • key dates (close date, invoice date, payment received date)
  • currency
If a value is wrong, determine whether it’s:

​
Step 3: Confirm the plan selection is correct

If the wrong plan is being used:
  • check the rep’s plan assignments (effective windows)
  • check the deal’s selection date and required deal relevance (anchor) dates
  • check the plan effective/end date window
  • See: Plan selection and timing
  • See: Managing assignments

​
Step 4: Check eligibility gate (invoice/payment)

If the deal is stuck in “waiting”:

​
Step 5: Use calculation transparency

Review:
  • the selected plan
  • the calculator’s base amount and applied rate
  • any runtime variables emitted by the calculator (helpful for understanding tiers/accelerators)
  • the plan selection candidates and the anchor/selection dates used
  • gate metadata and whether the deal is WAITING_DATA vs waiting on invoice/payment
  • See: Deal calculation transparency

​
Step 6: Reparse vs recalculate (if needed)

If source data changed or you applied overrides, you may need to re-run calculations so totals reflect the latest effective values. Use:
  • Reparse when the underlying extracted deal data is wrong or incomplete (for example, a parsing/import issue).
  • Recalculate after changing variables, plan assignments, or plan configuration, so totals reflect the latest effective values.
Note: deals that are frozen or deleted may block these actions until unfrozen / restored. Also check Data Hub for errors or mapping issues:

​
Step 7: Escalate with the right evidence

If you still can’t resolve it, collect:
  • the deal URL
  • expected values (from CRM/contract)
  • what variables are wrong (and whether they’re source vs override)
  • the calculation summary / selected plan
This makes it much faster to diagnose.

​
What to collect before escalating

  • Deal URL and expected outcome (amount + status).
  • The plan assignment window for the rep.
  • Screenshots of Calculation steps 1 (Plan Selection), 2 (Anchor Date), and 6 (Gates).
  • The specific field(s) you believe are wrong (and whether they’re source vs override).

​
Common gotchas

  • If a number looks “wrong,” first confirm you’re looking at the right period and right plan (selection/timing vs payout timing).
  • If two places disagree, check whether one view is showing source values and another is showing effective values (after overrides).
  • When debugging, follow the chain: Deal → Plan selection → Eligibility gates → Calculation breakdown.