AffiliateFactoryWP

← All articles

GuidesDec 2, 2025 · 3 min read · by the Affiliate Factory WP team

Affiliate Payout Schedules: Net-30, Minimums, and the Rhythm Partners Can Plan Around

When to pay, how much must accrue first, and why a boring fixed date beats paying fast. The standard schedule explained, with the edge cases — minimums, dormancy, currency — decided.

Ask partners what makes a program trustworthy and the answers cluster around one thing: money arrives when the program said it would. Not fast — predictably. A payout schedule is a small set of decisions (when, how much minimum, what happens to stragglers), and getting them right costs nothing but deciding on purpose.

The three-part standard

The schedule most programs converge on, because it balances everyone's risk:

Maturity first. A commission becomes payable only after the order outlives your refund window — the maturity period that keeps you from paying money that later un-earns itself. With a 30-day refund policy, commissions mature at day 30–35.

A fixed monthly date. All matured commissions pay out on the same date each month — the 1st, the 15th, whatever you'll never miss. "Net-30, paid monthly" in program shorthand. A fixed date beats rolling per-commission payouts for reasons beyond your own sanity: partners can plan around it, payment fees batch instead of multiplying, and a missed rolling payout is invisible while a missed monthly date is accountable.

A minimum threshold. Balances below a floor — $25 and $50 are the common choices — roll to the next month instead of paying out. This isn't stinginess; per-payout fees on tiny amounts can eat a meaningful slice of the payment, and a $4 payout costs you processing plus everyone's attention. Set it low enough that a modest partner reaches it within two or three months.

Publish all three numbers on your program page and in your terms. Together they answer the applicant's real question — "if I send a sale today, when do I see money?" — and the answer ("it matures in 30 days, pays on the next 1st") being specific matters more than it being fast.

The edge cases worth deciding now

  • Dormant balances. A partner leaves $18 below threshold and goes quiet forever. Decide: balances pay out regardless of minimum once a year (tidy, generous), or on request, or expire after a defined period if your terms say so and local law allows — earned commissions are the partner's money, so err warm here.
  • Departures. When a partner exits the program, matured balance pays on the next cycle regardless of minimum; pending commissions ride out maturity first. Write it down before anyone leaves angry.
  • Negative offsets. Reversals deduct from the balance before anything pays — the negative-balance policy plugs in here.
  • Method and currency. Who eats the PayPal fee (usually the program), what happens for partners in countries your method doesn't serve, whether you'll ever pay in store credit (only if the partner chooses it — a rate premium for credit is a nice optional carrot, an imposed one is a red flag).

The dashboard does half the work

Payout trust is mostly visibility trust. A partner who can see, any day, their pending amount, their payable amount, the date each pending sum matures, and a history of past payouts with dates and references, never emails you "where's my money" — the dashboard already answered. This is worth demanding from your software: in Affiliate Factory WP each payout is a ledger entry linked to the commissions it covered, the partner's view separates pending from payable, and every state change lands in the audit log. The demo shows both sides — the admin's payout run and the partner's history.

Then keep the only promise that matters. Pick a date you can hit every month for years, automate what your payment method allows, and be an hour early rather than a day late. Partners forgive modest rates, strict rules, even clawbacks — they don't forgive the 1st arriving without money and without an email.

Keep reading