Reward Statements That Explain the Math
A reward statement should show the eligible inputs, the period, the rule version, any deductions, and how to request a correction. If a creator cannot reproduce the number from the statement alone, the statement is not doing its job.
Show the inputs that actually count
Start by listing every figure that feeds the reward: hours, diamonds, streaks, or other tracked activity. For each input, state the source and the cutoff. A creator should see not just the total but which days or sessions contributed and which were excluded.
Exclusions matter as much as inclusions. If a session fell outside the period, failed a validation rule, or was reversed after review, say so plainly. A statement that only shows the final number invites disputes that take longer to resolve than the original calculation.
Name the period and the rule version
Every statement needs a clear period, such as a calendar month or a payout cycle, with start and end dates. Ambiguity about when a period closes is a common source of confusion, especially when activity spans midnight or time zones.
Rules change. A statement should reference the specific version of the reward formula that applied during that period. If the formula was updated mid-period, show how the change was handled, whether by splitting the period or applying the new rule from a stated date. This prevents a creator from comparing two months and assuming an error when the rule simply changed.
Make deductions and adjustments visible
Deductions should never appear as a single unexplained line. Break them into categories: reversals, corrections from a prior period, or adjustments for ineligible activity. Each line should carry a short reason and, where possible, a reference to the underlying event.
Suppose an agency runs a monthly reward based on valid LIVE hours. A creator sees a deduction labeled 'ineligible hours' with no detail. After a support request, staff find that two sessions were flagged for a technical issue and reversed. If the statement had shown those sessions and the reason, the creator could have verified the outcome without contacting support. The test is simple: can a creator match every deduction to a specific event or rule? If not, the statement fails.
Give a clear correction route
A statement should end with instructions for disputing or correcting a figure. State the channel, the deadline, and what information the creator should include. A vague 'contact us' is not enough.
The correction route should also set expectations about timing. If a correction is accepted, say whether it will appear in the current statement, the next one, or as a separate adjustment. This reduces repeated follow-ups and keeps the ledger consistent.
Test the statement against a real month
Before publishing a statement format, run it against a completed month with known figures. Pick a creator with a mix of eligible and ineligible activity, at least one deduction, and a rule change if one occurred. Then ask someone who did not build the statement to reproduce the final number using only the statement and the published rules.
If that person cannot arrive at the same total, the statement is missing a step. This test is more useful than a visual review because it checks whether the explanation is complete, not just whether it looks clean. Repeat the test whenever the reward formula changes.
Continue reading
A practical next step
Explore the related Devign work, then discuss your requirements before committing to a project scope.