Why commission adjustments deserve their own review
Affiliate reports may show different stages of a referral over time. An initially credited event can later be reclassified, reversed or adjusted. That does not by itself show that an error occurred: the program may apply eligibility rules, correct duplicate records or update a referral’s status. The operational question is whether you can understand the change and match it to documented terms.
This review is different from checking whether an individual referral qualified in the first place. Focus here on what happens after a commission appears in reporting: how the status changes, how the reason is communicated, and whether the resulting figures can be traced. A clear process helps you identify questions early and avoid treating provisional figures as settled earnings.
- Keep initial reported amounts separate from adjusted or payable totals.
- Record the date you observed each change, not only the period to which it relates.
- Do not assume a reversal is valid or invalid without checking the applicable terms and records.
Map the stages from reported event to final amount
Write down the labels used in the program’s dashboard and statements. They might distinguish tracked events, approved amounts, adjustments, reversals and completed payments, but labels vary. Use the program’s own definitions where available. If a label is unexplained, request clarification rather than assigning it a meaning based on another program’s terminology.
Then map which report or document is authoritative for each stage. A real-time dashboard, a period statement and a payment record may serve different purposes. Note whether each view can be exported and whether a later correction changes the old report or appears as a separate entry. That difference matters when you investigate a change months after the original event.
| Stage or record | Question to answer | Evidence to retain |
|---|---|---|
| Initial report | When and where did the referral first appear? | Dated report or export, with relevant filters noted |
| Status change | What label changed, and when? | Before-and-after records or dated screenshots |
| Adjustment or reversal | What explanation and term are cited? | Program notice, support response and applicable terms |
| Period statement | How is the change reflected in the period total? | Statement or export and your reconciliation notes |
| Payment record | Does the completed payment correspond to the statement? | Payment confirmation and related period reference |
Read adjustment and reversal terms closely
Look for the terms that describe when an amount can change, who may make the adjustment and how long the program may review an event. Confirm whether the rules distinguish between cancellation, refund, duplicate activity, invalid activity, correction of tracking data or other events. These are examples of categories to clarify, not claims that every program uses them.
Check whether the terms explain how the program communicates a change and whether there is a process for asking questions. If the dashboard uses broad labels such as ‘adjustment’ without a definition, request the specific basis and the relevant reporting period. Keep your questions narrow and reference the relevant event or statement so a response can be matched to your records.
- Find the clause that governs the reason given for a change.
- Check whether the terms describe notice, review or dispute steps.
- Save a dated copy of the applicable terms when you conduct the audit.
- Record whether a response resolves the question or leaves a specific point open.
Create a repeatable reconciliation workflow
Choose a regular review interval that fits your reporting operations. For each period, compare the initial export with the later statement, list additions and deductions, and link each difference to an explanation or a pending question. Where reports can be filtered by date, campaign or referral identifier, note those settings so that a later comparison uses the same scope.
Avoid editing original exports to make them match. Preserve the source file and create a separate working copy or reconciliation sheet. Add a status such as ‘explained’, ‘awaiting response’ or ‘needs follow-up’. That creates an audit trail without presenting an unresolved difference as a proven loss or a confirmed program error.
- Save an untouched copy of each original report.
- Use consistent identifiers and period boundaries across reports.
- Log the amount, reported status, date observed and reason supplied.
- Keep explanations attached to the corresponding record rather than only in informal notes.
Investigate an unexplained change without jumping to conclusions
Start by confirming that the two reports cover the same date range, currency, campaign filters and status definitions. A difference can result from comparing different reporting scopes. Next, locate the affected event, check whether the program issued a notice, and compare that explanation with the relevant program terms.
If the change remains unclear, send a concise inquiry with the event identifier, the report dates and the specific change you observed. Ask which rule or status caused the change and where it is documented. Retain the response and record the result of the inquiry. If you cannot obtain an explanation, classify the item as unresolved and consider the uncertainty when deciding how much operational reliance to place on that program.
- Confirm the report period and filters first.
- Ask for the event-level reason and applicable written rule.
- Keep a copy of the question and response with the record.
- Escalate only through channels described by the program; do not assume an appeal process exists.
Use the audit to improve program oversight
A useful review gives you a clearer view of reporting quality, not a guarantee about future earnings. Note whether explanations are consistent, whether records can be matched across reporting stages, and whether the program’s written rules answer the questions that matter to your business. These observations can inform your internal reconciliation process and your decision about how much time to allocate to follow-up.
Repeat the audit when terms change, reporting formats change, or you see a material shift in the way statuses are presented. Keep the scope modest: document what the program reports and what you can verify. Do not present a provisional dashboard figure as an assured payment or generalize one unresolved case into a claim about the entire program.
Common questions
Does a commission reversal always mean the referral was invalid?
Not necessarily. A reversal may reflect a program rule, a correction, a changed status or another documented reason. Check the event-level explanation and the applicable terms before drawing a conclusion.
Which record should I use as the final amount?
Use the program’s definitions to identify which report or statement represents the relevant stage, and match it to any payment record. A dashboard total and a completed payment record may describe different points in the process.
What should I do if a dashboard adjustment has no explanation?
Preserve the report, confirm its date range and filters, then ask the program for the specific event, reason and governing term. Track the item as unresolved until you have enough information to classify it.
How often should I review adjustments?
Set a cadence that suits your reporting and recordkeeping needs. Review each statement period consistently, and perform an additional check when terms, report formats or status labels change.