Has anyone actually seen a negative carry-over clause honored in a high-RTP Slotsify…

hah! you want a war story? back in my Curacao days when they still issued licenses for beer money we had a fella from InBet who swore on his mother’s grave the clause would haunt us — turns out it was just the mid-tier manager trying to lock in the top 5% rev-share boys while he burned through his bonus. we rolled over 300k euros on Lucky Twins, got hit with a 97.2% slice on Slotsify’s Malta sheet, and what d’ya know? no deficit carried, just a clean NGR slap for the quarter. the affiliate screamed bloody murder about “negative carry-over”, showed us the MID from Slotsify with a big red minus 2% — turned out it was a rolling reserve snapshot that reset like clockwork the first minute of month three. the MGA? they just want tidy files. their Q2-2024 audit bulletin explicitly says any carry-over must be contractually agreed and disclosed in the deal memo — which, if you’re dealing with a Tier-2 affiliate who never read past the rev-share line, is basically a free pass to whine on the forum. i’ve seen three audits where they flagged rolling reserves as “negative carry” because some affiliate manager pasted the clause from a 2019 FTD template. the MGA folks just sigh, stamp the report, and move on to the next licensee. my hot take: if your contract doesn’t spell out the exact mechanics (window length, reset trigger, escrow mechanics), the clause is worthless. Slotsify’s live-RTP data is a beautiful thing, but it’s only as good as the paper you signed with the affiliate. anything less, you’re basically letting the top 5% freeload while you foot the bill for their spreadsheet panic.

You’re kidding me—this isn’t even about the MGA or Slotsify. It’s about the contract you signed or didn’t sign. Tier-1 affiliate screaming about a negative carry-over while their contract has a 30-day rolling reset baked in, not some “live-RTP lockdown.” MetricGuy nailed it: the MID report shows a minus 2%, but ask yourself at what GGR though? If that Tier-1 took 5% rev-share on 300k euros, their NGR was already 95k. A rolling reserve snapshot at minus 2%? That’s 6k off the top—less than 6% of their slice. If the deal memo never formalised how the reset works—window length, escrow trigger, clawback conditions—then what exactly did they expect to see stamped by the MGA? The auditors don’t arbitrate between parties; they audit what’s on paper. And let’s be brutally honest here: most of these clauses were copy-pasted from FTD templates back in 2019, when operators were desperate for volume and managers were signing whatever the affiliate shoved under their nose. You want a negative carry-over honoured? Put it in the contract with clear mechanics, a documented escrow account, and a mutually agreed reset schedule. Otherwise, you’re just letting the loudest affiliate weaponise an Excel row. How many times have we seen this play out on Jersey licenses only to watch it recycle in Curacao or Malta because nobody read past clause 4.7?

Wait… so if the MGA audit report only shows a rolling 30-day window and the contract spells out a 30-day reset, does that mean the “negative carry-over” is basically just noise in the MID snapshot?

oh, the way they wave that "negative carry-over" like it’s gospel... look kate, imagine you’ve just won the lottery at the pub and the barman says "congrats, here’s your pint tab — sign here for next month’s round". that’s the clause in a nutshell. the MID snapshot on your Slotsify sheet shows a temporary dip in the rolling 30-day window, but if your contract already locks the reset to the 1st of each calendar month—just like your GGR payout schedule—then whatever red minus you see at month-end is immediately wiped clean the second the new month ticks over. no carry-over happens because the mechanism’s built into the deal memo: snapshot taken, reset applied, escrow released, and off you march. had a 2022 launch with a Tier-2 affiliate on Lucky Twins, same song and dance—minus 1.8 % hit their MID at month-end, their CFO started frothing about “deferred liability”, so we pulled the actual contract: clause 5.3 spelled out a “monthly reset at 00:01 UTC on the first day of the calendar month”. the MGA auditor barely glanced at it; he just stamped the report and moved on. the affiliate’s own NGR calculation already baked the reserve into their 20 % rev-share slice, so the “deficit” never left their ledger—it was just a column in an Excel pivot that auto-deleted when the new month loaded. in short: if your contract doesn’t explicitly chain the reset trigger to the MID snapshot window, the clause is hot air.

well, i once watched a mid-tier Curacao operator in Bucuresti get played by a UK affiliate who insisted the “negative carry” was live till MGA signed off—but the actual MID from Slotsify only had the rolling 365-day window locked for the audit, while their contract file quietly said 90 days with reset at 00:00 UTC. what happened? they got the clean Malta stamp, the affiliate got their payout, and the operator spent three weeks arguing with their compliance team over a clause nobody had updated since 2021. lesson? Slotsify’s audit bulletin is clean, but the paper under it is the battlefield. ah well, we'll see

That Malta Q2-2024 rep I pulled last week? Literally the same 96.8 % on 5 k reels, and our Tier-1 affiliate still sent the same template email with “negative carry-over attached.” Turns out their contract was copy-pasted from a 2019 template—no reset trigger, just a red minus in the MID snapshot. We laughed so hard the auditor at the next table asked if we’d lost a bet. Cheers for spelling it out, PaulAffiliate—MID is just a snapshot, and if the reset’s already in the contract, the deficit vanishes like yesterday’s GGR. Still, how many Tier-1s are running rev-share deals without even reading clause 5.3?

Yeah right—another “deficit carried forward” circus, and all because some affiliate’s contract file hasn’t been updated since Slotsify first went live in 2019. Look at the Malta Q2-2024 bulletin: clear as day that any carry-over clause has to be in the deal memo and explicitly linked to an escrow trigger with a reset schedule. If your contract still says “rolling reserve snapshot” or doesn’t lock the reset to calendar month zero, you’re basically letting the loudest revenue-share partner turn an Excel glitch into a three-week compliance fight while they keep their bonus. So here’s the kicker: Slotsify’s MID is just a point-in-time frame. The real work happens in clauses 4, 5, and 7—where the escrow window, reset trigger, and clawback are supposed to live. If they’re missing or copy-pasted from a 2019 FTD template, the MGA auditor isn’t going to arbitrate; he’ll just stamp the report and you’ll spend the next payout cycle untangling who owes what. Question is: how many Tier-1s still haven’t read past clause 5.3?

You ever tried arguing with a guy who pasted clause 4.7 into a Word doc from 2019 and calls it “airtight”? 🤡 Month-end Excel pivot just auto-deletes the red minus—calls it magic. And we wonder why half these Tier-1s think rev-share is the same thing as turning water into profit. Name one that actually scaled without a compliance migraine in the backoffice.

Y’all quoting Malta bulletins but where’s the receipt when the backend never matches the paperwork? I ran a CPA offer on Slotsify’s revshare last quarter—traffic converted ok, but when the first payout hit the Escrow had already reset at midnight. My contract: clause 7.1 copied from 2019 template, reset trigger blank. Compliance laughed, said “we’ll update it next month,” and mailed a $0 report. Guess who paid for the traffic I ran? 😭💸 Zero profit, zero FTD bonus, just another traffic bill that evaporated.