Key takeaway
Treat a possible referral reward as conditional until the applicable terms and actual events are evidenced. A published program page, a successful introduction and a wallet credit are different states.
Build the register around the program’s actual events
A referral can be useful even when it produces no payment. Before assigning revenue to it, establish the specific receiving program, the referrer’s actual eligibility, the version of applicable terms, required attribution and the reward conditions. A category appearing on a public program page is not evidence that an introduction will be accepted, a license will close or a reward will be paid.
The public Handshake referral page describes a bonus when a company’s deal closes. The micro1 company-referral FAQ describes distinct attribution and qualifying events, including unique-link handling and conditional reward/payment steps. These examples demonstrate why one generic “referred successfully” status is inadequate. They are observations of those pages on 10 October 2026, not evidence that VOID is enrolled in either program or that their full binding terms have been accepted.
Keep the seller’s license economics separate from compensation paid to a referrer. VOID’s authoritative model is receiving-program-paid referral, with no upfront seller referral fee. A receiving program’s conditional referrer reward does not establish the price, royalty or expected earnings of the record owner. Compensation disclosure and permission for the named introduction belong in the handoff record even when no payment follows.
A completed reward-control register
Hypothetical example: fictional receiving program R offers a conditional USD 2,400 reward to an eligible referrer for a qualifying opportunity under its stated terms. This is an invented control example, not a real program quote, VOID result or seller forecast. The coordinator has permission for the named introduction and documented attribution, but the required acceptance event has not occurred.
Use separate evidence fields so a later operator can distinguish an earned event from a notification, and a notification from money actually received. An unresolved eligibility or terms-version field should remain unresolved. Do not backfill it from memory after a payout dispute.
| Control | Illustrative current entry | Evidence needed to advance |
|---|---|---|
| Terms and eligibility | Program R, terms version R-1; eligibility recorded for the fictional case | Retain actual accepted conditions and any exclusions in a real referral. |
| Introduction permission | Named-recipient metadata permission recorded | No sample or license permission inferred from this entry. |
| Attribution | Required attribution identifier retained | Match the submitted opportunity and any pre-existing applicant exclusion. |
| Qualifying event | Acceptance condition not met | Document the program’s actual qualifying event; status remains conditional. |
| Reward amount | USD 2,400 if all example conditions are met | Check the applicable calculation and any lawful withholding separately. |
| Credit and withdrawal | No credit or withdrawal evidence | Keep credited amount, withdrawable status and withdrawal action distinct. |
| Bank receipt and reconciliation | USD 0 actually received | Match actual receipt to the opportunity and expected amount. |
Price the work without treating the reward as certain
For this hypothetical opportunity over twelve months, assume twelve coordination hours at USD 100 per hour, no other incremental cost and no upfront seller referral fee. The internal time cost is USD 1,200. If all conditions are met and USD 2,400 is actually received, the referrer’s before-tax contribution after that time cost is USD 1,200. If no reward arrives, the same spent work produces a negative USD 1,200 contribution. These are illustrative arithmetic outcomes, not program probabilities or a data valuation.
This calculation is deliberately separate from the owner’s license proceeds. It also is not a revenue-recognition or tax opinion. A terms dispute, withheld payment or an uncompleted qualifying event could leave the cash outcome different from a promotional headline. Record what actually happened and what the relevant conditions require rather than assigning an invented probability to the hoped-for reward.
Assign responsibility for reviewing terms changes, retaining attribution, confirming qualification and reconciling cash. Use introduction brief for the allowed handoff and offer comparison to keep the owner’s separate license discussion understandable. An operational register should make the next missing event visible; it should never encourage unnecessary record uploads or misleading claims about earned income. VOID does not promise referral eligibility, a receiving relationship, license acceptance or any payout.