Skip to main content

Commission Domain Model

This guide defines the key objects Core8 uses (orgs, team members, commission deals, plans, assignments) and how they connect, so you can debug where a number or status comes from.

When to use this

  • You want a mental model of how deals, plans, periods, and payouts connect.
  • You’re mapping a UI field to what it represents in a calculation.
  • You’re troubleshooting where a number or status comes from.

Key objects

Organization

Your Core8 workspace. Most configuration (integrations, variables, plan library) is organization-scoped.

Team member (personnel)

A person who can earn commission (sales rep) or manage commissions (manager). Plans are assigned to team members over time.

CRM deal vs commission deal

Core8 ingests CRM deals from your connected system (like HubSpot/Salesforce) and turns them into commission deals used for commission logic, editing, splitting, and calculations.

  • CRM deal: what your sales team manages in the CRM

  • Commission deal: what Core8 uses to calculate commission, including:

    • variables (source values and overrides)
    • split hierarchy (parent/child deals)
    • calculation snapshots and totals

  • See: Deals and Reviewing deals

Deal participants

One commission deal can have multiple participants (for example: AE + SDR + manager override). Each participant can have their own plan assignment and payout share, depending on your plan and configuration.

Commission plan

A plan defines:

  • time rules (anchor date + eligibility gate)

  • plan effective/end dates

  • the calculator logic (how base amount, rate, and commission are computed)

  • See: Understanding plans

Plan assignment

A plan assignment connects:

  • a plan
  • a team member (personnel)
  • an effective window (when that plan applies)

When a deal is calculated, Core8 selects the plan that applies based on plan selection rules (anchor/selection date + plan effective/end dates).

Calculation snapshot

When Core8 runs calculations for a deal, it stores a snapshot so you can audit:

  • which plan was selected

  • what inputs were used (effective variables at calculation time)

  • what outputs were produced (base amount, commission amount, runtime vars)

  • See: Deal calculation transparency

Split deals (parent/child)

Core8 can model one contract as multiple commission deals by splitting it into child deals.

Common reasons:

  • multi-year rate changes

  • pay-on-payment schedules

  • mixed deal types (new vs renewal vs expansion)

  • See: Deal splitting

Where you’ll see this in the UI

  • Team members (personnel): Team Members and the team member detail page.
  • Deals: Deals and the commission dashboard (open a deal to view its detail page).
  • Plans: Plans Library and the plan editor (open a plan from the library).

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.