Customer Survey Incentive Accounting and Fulfilment Controls

Executive summary

Core workflow

Approve the offer before invitations

Record research purpose, audience, survey length, incentive type and value, budget, eligibility, dates, and fulfilment deadline. Confirm that participation remains voluntary and the invitation explains the qualifying steps. Sensitive or regulated research may require additional ethics, legal, or privacy review.

State whether every eligible completion receives a reward, a random subset wins, or supply is limited. These promises differ. Define handling of duplicate entries, incomplete responses, fraud signals, and technical failures before launch. Store the approved public wording alongside the budget approval.

Minimise eligibility data

Collect only information needed to determine eligibility and deliver the reward. Keep contact details separate from survey answers where practical. Explain why details are collected and how long they are retained. Use a unique fulfilment key to prevent duplicate payment without exposing unnecessary survey content.

Restrict the participant-to-reward mapping file. Do not share full response exports with vendors when a minimal recipient list is sufficient. Define handling for shared email addresses, corrected addresses, resubmissions, and multiple household members.

Reconcile the reward ledger

Track response ID, reward type and value, eligibility, approval date, delivery status, provider reference, exception reason, and reconciliation date. Separate eligible, approved, sent, delivered, claimed, and expired states when the provider supports them. A sent reward is not necessarily received.

Use a second-person spot check where possible. Reconcile invoices, unused codes, failed deliveries, and cancelled rewards. Finance should be able to verify spend without receiving survey answers. Retain evidence needed for accounting while minimising participant data.

Resolve exceptions fairly

Create a queue for invalid addresses, provider errors, duplicates, disputed eligibility, and delays. Each case needs a category, owner, next action, deadline, and resolution note. If the system failed to record a legitimate completion, review evidence under a documented rule rather than automatically denying the reward.

Communicate what is being checked and when the participant can expect an update. Do not ask people to resend sensitive answers just to prove eligibility. If a vendor owns delivery, define escalation and a fallback when it cannot resolve the issue.

Close and improve

Reconcile approved budget, rewards issued, failed delivery, unused inventory, provider fees, and outstanding obligations. Track fulfilment rate, time to delivery, exception rate, and support contacts per hundred eligible participants. Do not treat every unclaimed reward as a saving if the published terms still require fulfilment.

Use results to improve future estimates and instructions. Review false-positive fraud flags and provide a fair appeal path. Keep the approved terms and ledger summary, with participant-level data retained only for a justified period.

Worked example

Worked example: A team promises a digital voucher to each eligible respondent. It reconciles responses against a unique eligibility list, shares only necessary contact details with the provider, tracks failed deliveries separately, and reconciles the invoice without exposing survey answers to finance.

Implementation checklist

• Terms approved before launch
• Public wording matches offer
• Only necessary data collected and shared
• Unique keys prevent duplicate fulfilment
• Sent and delivered states distinguished
• Exceptions have an owner and resolution path
• Budget and provider invoice reconciled

Key takeaways

• Terms approved before launch.
• Public wording matches offer.
• Only necessary data collected and shared.
• Unique keys prevent duplicate fulfilment.
• Sent and delivered states distinguished.
• Exceptions have an owner and resolution path.
• Budget and provider invoice reconciled.