Lottery Affiliate and Agent Management: Attribution, Commission and Settlement
Lottery affiliate management and agent management solve different operating problems. Affiliates refer customers and receive compensation under a marketing agreement. Retail agents sell through an authorised channel and may also have settlement obligations. Putting both into one commission field makes attribution, finance and dispute handling harder. An operator should define channel rules before choosing software. […]
Lottery affiliate management and agent management solve different operating problems. Affiliates refer customers and receive compensation under a marketing agreement. Retail agents sell through an authorised channel and may also have settlement obligations. Putting both into one commission field makes attribution, finance and dispute handling harder.
An operator should define channel rules before choosing software. This guide explains the records, permissions and acceptance tests to evaluate, with platform cost and operating responsibilities kept separate from the commercial terms agreed with partners.
Separate attribution, commission and settlement
Attribution identifies the partner connected to a qualifying event. Commission calculates what the operator owes under the relevant agreement. Settlement records payment or other financial obligations. These are related processes, but they are not interchangeable.
Define whether eligibility depends on registration, an accepted ticket, completed play or another agreed event. Document exclusions, reversals, attribution windows, currency, rounding and when commission becomes payable. Version the rules with an effective date. A new agreement should not silently rewrite previously approved statements.
For agents, distinguish commission from cash collection, working balances and amounts due to the operator. Keep player balances separate from partner accounts.
Build a role and channel responsibility matrix
| Role | Relevant record | Financial basis | Required control |
|---|---|---|---|
| Affiliate | Referral and qualifying event | Agreed acquisition or revenue-based commission | Attribution evidence and adjustment history |
| Retail agent | Accepted channel sale | Sales commission and separate settlement obligations | Terminal identity and daily reconciliation |
| Sub-agent | Approved parent and sales assignment | Contracted allocation within the hierarchy | No orphan accounts or double counting |
| Finance administrator | Approved partner statement | Recorded payable and payment reference | Approval permissions and audit trail |
| Technical integration | Event and external reference | No independent commission entitlement | Restricted access and replay protection |
In a retail-to-online operating model, specify whether online activity belongs to a referral partner, an agent channel or neither. Do not allow overlapping rules to produce duplicate compensation without an explicit agreement.
Scenario: an attributed ticket is later refunded
A referred player buys a ticket. The purchase becomes a qualifying event, but the draw is subsequently cancelled and the ticket refunded. Request a demonstration of the entire adjustment path:
- The original event remains linked to its referral, ticket and commission calculation.
- The refund creates an adjustment under the applicable agreement, not an unexplained deletion of the event.
- A repeated refund notification cannot reverse the same commission twice.
- The next partner statement explains whether the adjustment affects a pending amount or a previously settled period.
Repeat the test when a player is associated with both an affiliate referral and a retail agent. The system should apply the operator’s documented priority or allocation rule and preserve the decision.
Acceptance tests for partner management
- A replayed registration, sale or refund event cannot produce duplicate commission.
- A commission rule change has a visible version and effective date.
- A partner cannot view another partner’s customers, statements or exports.
- A sub-agent’s reassignment preserves earlier hierarchy and settlement history.
- Finance can reconcile statement totals to eligible events, adjustments and recorded payments.
Address partner visibility, retention and export boundaries in the data ownership requirements. Partners do not need unrestricted access to player profiles to verify a commission statement. Define the minimum necessary fields and applicable consent requirements.
Specify reporting and integration evidence
Ask for a statement that separates eligible volume, commission, adjustments, payable balance and paid amounts. Agents additionally need channel settlement and discrepancy reports. Connect reconciliation to the payment architecture, and document partner IDs, event references and delivery behaviour in the API integration brief.
Include these scenarios in the provider evaluation checklist. A dashboard showing total sales is not enough to establish that attribution, commission and settlement agree.
Lottery affiliate and agent management FAQ
Should affiliates and agents use the same rules?
Not automatically. Their roles, eligible events and financial responsibilities differ. Shared reporting can be useful without merging their agreements.
Is revenue share the only commission model?
No. Agreements may use acquisition, sales or other defined bases. The software must represent the actual calculation and exclusions rather than assuming one universal formula.
What happens when a partner relationship ends?
Define access withdrawal, final statements, outstanding obligations and record retention. Ending access should not erase historical reconciliation evidence.
What should a partner-management demo prove?
Attribution, a rule-based calculation, a refund adjustment, a role-restricted statement and a reconciled settlement.
Discuss your channel requirements
Prepare your partner types, compensation agreements, channel structure and reporting needs. CONTACT WhiteLotto to discuss requirements for affiliate and agent workflows and the questions to test with a platform provider.