Read This Before You Sign: The Six Clauses That Decide If You Get Paid

Negative carryover means that if your revshare balance goes negative in a period, usually because a referred player won big or bonus costs exceeded gaming revenue, the deficit rolls into the next period. You start the new month owing revenue before your first click lands. Without a reset clause, one bad variance month can shadow your earnings for a quarter or longer.

The clause bites hardest on small and mid-sized player books, where a single large winner can outweigh everything else. It converts revshare from a share of long-run margin into a position where you absorb short-run player variance, which is the operator's business risk, not yours. You do not share in the operator's balance sheet upside, so absorbing its downside is a one-way trade.

The market standard worth pushing for is no negative carryover, meaning negative balances reset to zero at period close. Where an operator will not concede that, a cap or a time limit on carryover is the fallback. What you should never accept silently is uncapped, indefinite carryover combined with cross-brand pooling, which lets one brand's variance consume commissions earned everywhere else.

• Ask: does a negative balance reset to zero at the end of the period, and if not, is carryover capped in amount or duration?
• Ask: is carryover calculated per brand or pooled across all brands in the program?
• Ask: do bonus costs and progressive jackpot contributions count toward the negative balance?
• Model it: take your expected player volume and ask what one large winner does to your next three months

Your revshare percentage is applied to net gaming revenue, and NGR is a defined term, not a fact of nature. The standard construction is GGR minus bonuses, payment processing costs, gaming taxes and chargebacks. The red flag is what gets added on top: administration fees, platform fees, license contributions, or a catch-all for "other costs", often expressed as a flat percentage skimmed before your share is calculated.

The arithmetic is unforgiving. A 40 percent revshare on NGR with a 25 percent admin fee is a 30 percent revshare wearing a costume. Because deductions compound quietly inside a definition, two programs advertising identical headline rates can pay out very differently, and the difference never appears on a landing page, only in the definitions section of the agreement.

The test is enumerability. Every deduction should be a named, closed list with stated percentages or actual-cost language, and you should be able to recompute your commission from the raw figures. An NGR definition you cannot recompute is not a formula, it is a discretion.

• Ask: list every deduction between GGR and my commission base, with the percentage or basis for each
• Ask: is there any admin, platform or marketing fee, and is it capped?
• Ask: are deductions itemized on my monthly statements so I can recompute NGR myself?
• Compare programs on effective rate after deductions, never on headline revshare

Brand bundling is the practice of pooling your performance across every brand in an operator's program into a single calculation. Your earnings on the brand where you send quality traffic get netted against negative balances, fees or underperformance on brands you barely promote, or promoted once and stopped.

Combined with negative carryover, bundling is the most expensive interaction in affiliate contracts. A losing month on a minor brand you tested in January can silently drain commissions from your flagship brand in June. It also destroys your analytics: when everything nets into one number, you cannot see which brand actually earns and which one leaks, so you cannot allocate traffic rationally.

The position to negotiate is per-brand accounting: each brand's revshare calculated independently, with no cross-brand netting of negative balances. If the operator insists on pooling, price that into the deal, because you are effectively underwriting their weakest brand with your strongest traffic.

• Ask: is commission calculated per brand or pooled across the program?
• Ask: can a negative balance on one brand offset earnings on another?
• Ask: do reports break out clicks, FTDs and NGR per brand, per month?
• If pooling is non-negotiable, demand a higher rate or restrict yourself to the brands you actually intend to push

On CPA and hybrid deals you are paid per first-time depositor, but the contract decides what counts as one. Minimum deposit amounts, minimum wagering activity, KYC completion, geo restrictions, payment-method exclusions and duplicate-account rules all sit between a real deposit and a paid FTD. Vague criteria are a red flag because they make your conversion rate a negotiable quantity after the fact.

The damage shows up as a gap between the FTDs you track and the FTDs you are paid for, explained after the fact by "failed validation" with no itemized reasons. A related clause to hunt for is retroactive disqualification, where players can be reclassified as fraudulent or duplicate weeks later and clawed back from balances already earned. Some fraud protection is legitimate, unbounded clawback windows are not.

The defense is specificity plus verifiability. Validation criteria should be exhaustively listed, and rejections should come with per-player reasons you can audit against your own S2S tracking. If you cannot reconcile their count against your postbacks, you are not measuring your business, you are taking their word for it.

• Ask: define a qualified FTD exactly, minimum deposit, wagering threshold, KYC status, allowed countries and payment methods
• Ask: what is the clawback window for reclassifying players, and is it capped?
• Ask: do rejection reports itemize the reason per player?
• Verify: run your own postback-based count and reconcile it against every statement, the delta is your negotiation evidence

Most affiliate agreements let the operator amend terms by updating a webpage, sometimes with notice, sometimes with none, and continued participation counts as acceptance. Under a clause like that, your revshare rate, the NGR definition and the validation criteria are all provisional. The contract is less a fixed agreement than a standing offer the operator can reprice.

The most damaging variant is retroactive application, changes that reach players you already referred. Revshare economics are built on the lifetime of a player book: you spend to acquire a player expecting years of shared revenue, and a clause that lets the operator cut the rate on your existing book after acquisition breaks the model at its foundation. Prospective changes to future players are an inconvenience, retroactive changes to your book are a repricing of work already done.

You will rarely get amendment rights removed from a standard agreement, but you can get guardrails: written notice with a defined period, no retroactive application to already-referred players, and an exit ramp under which you can terminate and be paid out at the pre-change terms if you reject an amendment.

• Ask: how are term changes notified, and how long is the notice period?
• Ask: do rate or definition changes apply to players I have already referred?
• Ask: if I reject a change, can I terminate and receive earned commission at the old terms?
• Archive: keep dated copies of the terms at signature and at every amendment, disputes turn on what applied when

Every program has a minimum payout threshold and a payment schedule. The red flags are thresholds set high enough to trap small balances indefinitely, unpaid balances that expire or are forfeited on account closure, and payment terms that stretch to net 60 or beyond, sometimes with a clause allowing suspension of payment during any "review" of unlimited duration.

The cost is more than annoyance. Long payment cycles are an interest-free loan from you to the operator, and they compound your own cash-flow risk: you pay for content, tools and media now against commission that arrives months later, if the balance clears the threshold at all. An open-ended payment review clause is the operator holding your money while deciding whether to keep it, with the burden of proof on you.

Pin down the full path from period close to money received: statement date, dispute window, payment date, payment method and who bears the fees. Then track it. An operator that slips from net 30 to net 45 to net 60 across a year is telling you something about its balance sheet, and affiliates who reconcile a payment ledger see the drift months before affiliates who check a dashboard occasionally.

• Ask: what is the payout threshold, and does an unpaid balance roll over indefinitely without expiry?
• Ask: what are the exact payment terms, net 15, 30 or 60, and by which methods, with fees borne by whom?
• Ask: under what conditions can payment be suspended, and is any review window time-limited?
• Ask: what happens to accrued balances if either side terminates?
• Track actual payment dates against contractual dates, drift is an early-warning signal

None of these clauses is exotic. They appear in standard agreements from reputable programs, and each is individually survivable. What kills affiliate economics is the combination: uncapped negative carryover, pooled across bundled brands, on an NGR definition padded with admin fees, with FTD criteria the operator interprets and terms the operator can rewrite. Read the agreement as a system, not a list.

Before signing, get written answers to the questions below. A serious affiliate manager can answer all of them in one email. Evasive or missing answers are themselves the finding: a program that will not define its own payout mechanics before you send traffic will not become more transparent after it holds your balance.

• Negative carryover: reset, cap or uncapped? Per brand or pooled?
• NGR: closed list of deductions, itemized on statements, recomputable from raw figures?
• Bundling: per-brand accounting, or your best brand subsidizing the rest?
• FTD validation: exhaustive criteria, itemized rejections, capped clawback window?
• Amendments: notice period, no retroactive application, exit at pre-change terms?
• Payments: threshold, rollover, net terms, fees, suspension conditions, termination treatment?

Every protection in this guide assumes one capability: that you can measure your side of the relationship independently. An affiliate who relies on the operator's dashboard for clicks, FTDs and NGR has no way to detect quiet validation drift, deduction creep or a mispriced statement, and no evidence to negotiate with when something looks wrong.

The minimum viable setup is S2S postback tracking with click IDs, so registrations and deposits are recorded on your infrastructure at the moment they happen, plus a commission ledger that records what each program owes, what it paid and when. Reconcile the two against operator statements every period. Most discrepancies are honest errors, and honest errors get corrected fast when you arrive with line-level data instead of a feeling.

This is the discipline Adfilius productizes with tracking and a payouts ledger, but the principle is tool-agnostic and older than the industry: the party with independent records sets the terms of the dispute. Read the contract before you sign, and measure it forever after.

• Run S2S postbacks with click IDs so conversions land in your own data first
• Keep a per-program ledger of earned, invoiced and received amounts
• Reconcile every statement against your own conversion counts
• Raise deltas immediately and in writing, aged discrepancies become unrecoverable