Skip to main content
This page is a practical checklist of what Core8 supports today and how to model common edge cases, so you can plan around limitations.

​
When to use this

  • You want to confirm whether a plan structure or feature is supported.
  • You need to set expectations for edge cases and limitations.
  • You’re deciding whether something should be modeled in-plan or handled manually.

​
Common plan patterns (supported)

RequirementSupportRecommended approach
Multi-currency deals✅Multi-Currency Commissions
Multi-year contracts✅Multi-Year Deals
Pay-on-Payment (cash collected)✅Pay-on-Payment
Product-based rates✅Product buckets
Bonuses / SPIFFs✅Bonuses & SPIFFs
Deal splitting✅Deal Splitting
Multiple Participants✅Multiple Participants
Paid vs unpaid tracking✅Paid vs unpaid payout tracking
Audit trail & transparency✅Auditability and History
Disputes workflow⚠️Support varies by configuration; if you need formal dispute tracking, contact support.
Net of partner fees✅Net of partner fees
Clawbacks (adjustments)✅Record clawbacks as adjustments; see Clawbacks and early-exit clauses.
Global parsing rules✅Global rules

​
Important limitations / “plan around it”

These items are commonly requested but often require a specific approach:
  • Automated clawbacks: Core8 supports recording clawbacks via adjustments, but automating clawbacks end-to-end depends on your data pipelines and contract requirements.
  • Quarterly/fiscal complexity: Core8 supports fiscal year start configuration and quarterly true-ups, but don’t assume calendar-quarter defaults match your fiscal calendar.
  • Data availability: invoice/payment gates require invoice/payment evidence. If your integrations don’t provide those fields reliably, deals can remain “waiting”.

​
Where to check when something isn’t supported

​
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.