← Back to blog
OpsMar 14, 2026

Affiliate payout audit checklist: what to verify before you pay

Pay fast, but pay from clean data

Affiliate payout audit checklist

Most affiliate payout drama is not fraud. It is unreviewed edge cases: refunds posted late, self-referrals, coupon leakage, or a tracking bug that quietly doubled commissions.

This checklist helps you pay on time while keeping payouts defensible. It is written for SaaS, where subscriptions, upgrades, and refunds make affiliate payouts harder than they first appear.

Table of contents

Quick answer

Before you pay affiliates, confirm five things: the commission cleared your lock window, no refund or chargeback changed the payout basis, no self-referral or coupon-policy violation exists, no duplicate attribution slipped in, and the payout export still reconciles to billing data. If those five checks pass, you can usually pay with confidence.

Define your payout rules (once)

Before you audit anything, write down the rules you’ll audit against. Keep them simple and publish them (affiliate terms / portal):

  • What’s commissionable: new customers only vs upgrades/expansions too.
  • Commission base: net revenue (after refunds/chargebacks) vs gross.
  • Lock period: when commissions become ‘approved’ (e.g., after 14–30 days).
  • Disqualifiers: self-referrals, prohibited coupons, trademark bidding, resold/stolen leads, etc.
  • Attribution precedence: coupon code vs last-click vs first-click; what happens on conflicts.

If you don’t define these, your ‘audit’ becomes ad hoc negotiation. The checklist below assumes you can answer those questions.

Pre-payout checklist (every cycle)

Run this right before you mark commissions as approved or payable. The goal is not a giant forensic review. The goal is to catch the handful of issues that create payout disputes later.

  • Confirm the payout window: are you paying for activity in a specific date range, or for commissions that just cleared the lock period?
  • Filter to ‘approved/eligible’ only: exclude pending, reversed, and disputed items.
  • Refund/chargeback sweep: ensure refunds posted in the period reverse commissions (or keep them pending until the refund window closes).
  • Coupon policy sweep: check for commissions tied to prohibited coupons (internal coupons, influencer-only coupons used on deal sites, etc.).
  • Self-referral sweep: look for matches on email domain, billing name, IP range (if available), or same card fingerprint — depending on your privacy rules.
  • Duplicate attribution sweep: same customer credited to multiple affiliates, or multiple conversions for one subscription.
  • Outlier sweep: affiliates with sudden spikes (clicks, conversions, refund rate, or unusually high AOV).
  • Manual approvals log: review any one-off exceptions you granted (brand bidding permission, co-marketing, special rates) and apply them consistently.

Common flags + what to do

FlagUsually meansAction
High refund rateLow-quality traffic or misaligned messagingHold payouts until lock period; ask for traffic sources; consider reducing exposure
Many ‘brand + coupon’ conversionsCoupon leakage / deal site last-click captureAudit coupon usage; enforce coupon rules; reverse where policy was violated
Same customer attributed multiple timesTracking bug or lifecycle events counted as newDeduplicate; pay once per rule; fix event mapping
Spike overnightBot traffic, paid ads, or a viral postAsk for explanation; sample-check conversions; temporarily cap or hold approvals
Self-referral indicatorsAffiliate buying their own plan or routing internal leadsPause/deny per terms; document evidence; communicate clearly

A simple payout workflow

  • Weekly: quick sweep for obvious issues (refund spikes, coupon abuse patterns).
  • Payout day: run the full checklist; export a payout report; save it (date-stamped).
  • If you reverse/deny: record the exact rule and supporting evidence (screenshot, order id, coupon code).
  • Communicate exceptions: one short email beats ten back-and-forth messages later.

FAQ

How long should the lock period be?

Match your refund/chargeback window. For many SaaS plans, 14–30 days is a good default. If you offer extended refunds, keep commissions pending longer — or pay partially with a clawback rule.

Should I ever pay fast without an audit?

Paying fast builds trust, but paying wrong creates disputes. The compromise is a lightweight audit (outliers + refunds + coupon rules) every cycle, and a deeper audit only when something looks off.

Want this Playbook in your inbox?

I share practical notes on affiliate programs for SaaS.No spam. No hype.

Unsubscribe anytime. No spam.

Ready to launch?

If Rewardful feels like overkill, start simple: signup page + links + Stripe-attributed revenue.

Related posts

Affiliate platform migration checklist and questions

Affiliate platforms: questions to ask before you migrate (SaaS)

A practical checklist for migrating affiliate platforms in SaaS: what to export, how to compare ledgers, how to handle refunds and clawbacks, and the safest cutover plan.

Read article
Affiliate tracking for subscriptions: events and edge cases

Affiliate tracking for SaaS subscriptions: trials, upgrades, refunds, and recurring commissions

A founder-friendly guide to affiliate tracking for SaaS subscriptions: which event should earn commission, how to handle trials and plan changes, how recurring commissions work, and the tests that catch broken attribution.

Read article