Skip to main content
Choose multi-currency when your deals are booked in one currency but commissions must be reported or paid in another. Before configuring anything, decide (1) which currency is the commission “source of truth” for each deal, and (2) which exchange-rate policy you will use (what date, what provider, and whether you lock rates). After setup, validate on one known deal by checking the deal’s effective values and calculation breakdown to confirm the FX logic matches your policy. Common multi-currency scenarios include:
  • deals are booked in different currencies by region
  • the company reports in one “base” currency
  • reps are paid in their local payout currency

​
When to use this

  • You close deals in multiple currencies and need consistent conversion rules.
  • You need reporting and payouts in a single org currency.
  • You want to audit which exchange rates were used in calculations.
Core8 is designed to keep commission calculations consistent and auditable even when currencies differ. Report by currency

​
How Core8 approaches currencies (high level)

Core8 separates calculation from FX:
  • Your plan’s calculator logic is evaluated in a single working (quota) currency.
  • Core8 handles FX conversion outside the calculator and stores an FX snapshot for audit.
This prevents double-conversion issues and makes results explainable later.

​
Prerequisites

  • Deals have the correct deal currency set (from your CRM/import).
  • FX rates are available for the relevant anchor dates (Core8 stores FX snapshots for audit).
  • Team members have their payout currency configured (where relevant).

​
What to do in Core8

  1. Confirm the deal currency and amounts are correct in the deal detail view.
  2. Ensure exchange rates are available for the relevant dates (Core8 stores anchor-dated FX snapshots for audit).
  3. Use Report by Currency to:
    • verify totals by currency
    • spot unusual FX effects
    • reconcile reporting views

​
How to verify

  1. Pick one known multi-currency deal and confirm the deal currency and amount are correct.
  2. Open the deal’s Calculation view and confirm the effective values and FX conversion match your policy.
  3. Open Report by Currency for the same period and reconcile totals across currencies.
  4. If a deal is Waiting due to missing FX, confirm FX exists for the relevant anchor/payment date (and re-run if needed).

​
What to expect in the UI

  • If FX is required but missing for a deal/period, the deal may show a waiting state until required data is available.
  • Reports can group totals by currency to make reconciliation easier.

​
Common gotchas

  • Decide (and document) which date anchors the behavior: booking date vs invoice date vs payment date.
  • If the pattern depends on fields from an integration, confirm those fields actually exist in Data Hub and aren’t overridden.
  • Test with a tiny set of deals first, then expand—patterns often “work” but break on edge cases like refunds, partial payments, or split deals.