Payout Schedules
AffiliateBase supports operator-driven payout scheduling through payout runs. Most teams use a recurring internal cadence (weekly, bi-weekly, or monthly).
How Timing Works
Timeline:
- Sale/conversion creates commission.
- Commission moves from
pendingtodueafter hold period. - You create and execute payout runs on your cadence.
- Payouts reconcile to
paid.
Building a Cadence
Common cadences:
- Weekly: faster affiliate payouts, higher ops frequency
- Bi-weekly: balanced operations
- Monthly: lowest ops overhead
Choose based on:
- Cash-flow preference
- Affiliate expectations
- Internal finance bandwidth
Recommended Operating Procedure
For each payout cycle:
- Open Payouts.
- Create a new payout run.
- Review eligible affiliates and totals.
- Execute the run.
- Reconcile exports and payment references.
- Confirm payouts are in
paidstate.
Referral Window and Commission Due Date
Campaign timing has two separate settings:
days_before_referrals_expire: how long a referral can receive credit after a click.days_until_commissions_are_due: how long after a sale before the commission becomes payable.
Practical guidance:
- Keep the commission due delay aligned to refund/dispute risk.
- Keep the referral window aligned to the normal customer decision cycle.
- Set clear affiliate expectations on when commissions become payable.
Schedule Policy Template
Use this template in your program terms:
- Payout cadence:
Monthly on the 5th - Hold period:
30 days - Reconciliation SLA:
within 2 business days of payout run - Exception handling:
manual review for fraud/refund flags
Troubleshooting
No payouts available on run day
Check:
- Commissions are
due(not stillpending). - Affiliates have required payout details.
- Affiliates are active.
Runs created but not fully settled
Check:
- Export execution completion in PayPal or Wise.
- Missing PayPal or Wise recipient details.
- Remediation hints in payout run reconciliation.
Best Practices
- Keep cadence predictable and publish it to affiliates.
- Assign a run owner for each cycle.
- Store payout references for every completed run.
- Reconcile exceptions immediately rather than batching unresolved failures.
Next steps
- Review setting up payouts
- Review payment methods