Testing Your Rules

Before activating a new commission rule, use ReportFlow's rule preview feature to simulate calculations on sample or historical clockouts. This ensures your rules produce the expected payouts and helps you catch configuration mistakes before they affect real earnings.

Sandbox Mode

Test rules without affecting live data.

Sample Clockout

Enter a mock clockout to see the calculation breakdown.

Historical Replay

Rerun past clockouts through new rules to compare results.

Using the rule preview

After creating or editing a rule, click Preview instead of Save. A modal opens where you can enter sample revenue amounts, select a model, and choose transaction types. ReportFlow evaluates your draft rule set (including any priority ordering) and displays the calculated commission with a step-by-step breakdown.

Input: Revenue = $1,500 | Model = Hanna | Type = purchase Rule matched: "15% for Hanna" (priority 2) Calculation: $1,500 × 15% = $225.00

Historical replay

Want to see how a new rule would have affected past earnings? Navigate to Commission Rules → Replay, select a date range, and choose the rule set you want to test. ReportFlow recalculates every clockout in that window using the new rules (without overwriting the original payouts) and shows a side-by-side comparison.

This is especially useful when adjusting rates—you can quantify the financial impact before committing to the change.

Sandbox mode

For more complex testing, enable Sandbox Mode in Settings. In sandbox mode, incoming Discord clockouts are processed but marked as "sandbox only"—they don't affect real commission balances or appear in official reports. This lets you test the full end-to-end pipeline (AI extraction, fraud checks, rule evaluation) with live messages before going live.

Best practices

  • Always preview before saving a new rule.
  • Use historical replay when changing rates to understand financial impact.
  • Test edge cases: zero-revenue shifts, high-revenue outliers, model-specific rules.
  • Keep sandbox mode enabled during initial rollout until you're confident the system is working correctly.

Next steps