Skip to main content
This guide shows where calculation inputs come from (source systems vs Core8) and how overrides change the effective values used in calculations. Use it to answer: “Why does Core8 show X when my CRM shows Y?” and to choose between fixing a mapping vs applying an override.

​
When to use this

  • You need to know whether a value came from a source system or an override.
  • You want to understand what changes when you edit a value in Core8.
  • You’re debugging inconsistent inputs across deals or periods.
Core8 tracks variables in three important layers:

​
1) Source values (baseline)

Source values are the baseline variable values imported into Core8 from:
  • your CRM integration (HubSpot, Salesforce, etc.), and/or
  • parsed documents (contracts, PDFs), and/or
  • other connected data sources (invoices/payments, where applicable)
These are the “starting point” for calculations.

​
2) User edits (overrides)

If someone changes a value in Core8 (for example editing a deal amount, deal type, or a date), Core8 records a user edit for that variable. Overrides are intended for:
  • fixing missing/incorrect source data
  • applying an agreed-upon adjustment to match the contract
  • handling one-off operational corrections (with an audit trail)

​
3) Effective values (what Core8 uses)

Effective values are what Core8 uses for:
  • plan selection (which plan applies)
  • anchor date computation
  • eligibility gates (invoice/payment gates)
  • calculator inputs
High level rule:
  • if a variable has an override value, use it
  • otherwise, use the source value

​
Example: source value vs override

Scenario: CRM shows amount = 100,000, but the signed order is 90,000.
  1. The source value is 100,000 from CRM.
  2. You override the deal amount to 90,000 in Core8.
  3. The effective value used in calculation becomes 90,000.
  4. Recalculate the deal and confirm the Build Input step shows 90,000.
How to verify: open the deal’s Calculation view and compare Source values vs Effective values.

​
Important notes

  • A calculation snapshot is stored for auditability, but snapshots do not change the current effective values. If you edit a variable after a calculation run, you may need to recalculate to see updated totals.
  • Variable names are flat strings (not nested JSON paths).

​
After editing: recalculate

Edits update effective values, but deal totals won’t change until you run recalculation.
  1. Open the deal details page.
  2. Click Recalculate to queue a new calculation run.
  3. If the deal is frozen or deleted, you’ll need to unfreeze/restore it before you can recalculate.
Sales reps may have read-only access, depending on your organization permissions.

​
How to troubleshoot variable issues

  1. Open the deal details view and verify the key variables (amount, dates, deal type, currency, etc.).
  2. Check whether the value is coming from source data or an override.
  3. If you change a variable, click Recalculate to update totals.

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