Dashboard
On this page

Team revenue splits

Share a game's income with your team by agreed percentages, see what each member is owed, and get store sales paid out to everyone automatically.

A revenue split records how a team shares a game's income: who is in it, what percentage each person gets, and from then on what everyone is owed and has been paid. Splits are in Revenue splits in the sidebar, and a studio's are also in Studio HQ.

DevNet only moves money it actually receives. Asset store sales go through DevNet, so those can be paid to every member automatically. DevNet never receives Robux, Steam or Epic income: for that, the split is a shared record of what's owed and what's been paid, and the money is paid by the team itself.

This is the team's own bookkeeping. It isn't legal or tax advice, DevNet staff don't settle disagreements about it, and each member is responsible for their own taxes.

Setting one up

Select New split and fill in:

  • Whose income: your own account, or a studio you're an admin or manager of. That account's managers record income and mark payments.
  • A name, and optionally one of the account's LiveOps games, so the team knows which game it's for.
  • Split this account's asset store sales (optional): see Store sales. Only one split per account can do this.
  • Members: 2 to 20 people by username, each with a share in percent (up to two decimals) and an optional role, such as Scripter. The shares have to add up to exactly 100%. Studio accounts can't hold a share; add the people instead.

Select Send for acceptance. Every member is notified and accepts or declines on the split's page.

A split that takes a studio's store sales also needs the studio's own approval. Admins and managers can write it and change its shares, but it only starts once the studio account itself has selected Approve as owner on the split's page (sign in as the studio account). The same goes for every later change to its shares; until then the current shares, or none, apply. A split you set up for your own account needs no extra approval. You accept by proposing, if you're a member. Once everyone has accepted, the split is active. If anyone declines, nothing starts: the managers can propose new shares or withdraw it.

Changing the shares

A manager selects Change shares. Each change is a new version:

  • Members whose share or role changes, new members, and anyone removed are asked to accept. Members the change doesn't touch don't need to.
  • Until all of them accept, the current shares keep applying. If one declines, the change is dropped.
  • Income is always split by the shares in use when it was recorded, so a change never rewrites what people were already owed. Every version stays on the Versions tab.

Someone who leaves keeps whatever they were already owed.

Store sales

When a split covers an account's asset store, DevNet collects each sale of that account's assets instead of sending it to the account. DevNet keeps the usual 10% store fee, and the rest is split by the shares and sent to each member's Stripe account straight away. For example, a $20 sale leaves $18 after the 10% store fee; with shares of 60% and 40%, the members receive $10.80 and $7.20.

  • The account selling the assets doesn't receive these sales itself, so it doesn't need payouts set up for them.
  • A member who hasn't set up payouts keeps a balance. Their split page and the Payouts page say Set up payouts to receive the amount, and it's sent as soon as Stripe confirms their account.
  • If Stripe can't send a payment, DevNet tries again, up to 6 times. After that it shows as failed, and the member or a manager can select Try again.
  • A share that waits for payout setup is never given to anyone else. The member is reminded after 30 and 60 days; at the second reminder the split's managers and DevNet staff are told too.
  • If a buyer disputes a sale with their bank, the shares of that sale not yet sent are held until the bank decides. If the bank sides with DevNet they are sent; if it returns the money to the buyer, those shares are taken off what members are owed by a reversal entry. Shares already sent stay with their members.
  • Ending a split sends new sales back to the account. A checkout that was already started when the split ended is still split.

Income DevNet doesn't collect

For Roblox (DevEx or group payout), Steam, Epic Games and other income, a manager selects Record income and enters the currency (Robux or US dollars), the amount, where it came from, the period it's for, and optionally a note and a receipt link. Every member is notified.

Each member's part shows on the entry. Then the managers pay members themselves, outside DevNet, and mark it paid on the Payments tab: the amount, date, how it was paid and an optional reference. Robux are always paid by hand: Roblox has no way for DevNet to pay Robux to people.

The member then selects It arrived, or It didn't arrive to tell the managers. A manager can cancel a payment record that was wrong, and the amount is owed again.

When something looks wrong

Open the entry on the Income tab and Flag as wrong, saying what's wrong. Everyone in the split can comment underneath. A manager, or whoever flagged it, marks it as sorted.

Entries are never edited or deleted. A manager can Reverse an entry recorded by mistake: a new entry takes it back for every member. A reversal isn't possible while a member has already been paid more than they'd be owed afterwards; cancel that payment record first. Store sales can't be reversed by hand.

How amounts are rounded

Each entry is split so the parts always add up to exactly the entry: everyone gets their share rounded down, and the few cents or Robux left over go to the members with the biggest remainders. For example, $1.00 split three ways (33.34%, 33.33%, 33.33%) is $0.34, $0.33 and $0.33.

Who can see a split

Only its members (anyone named in any version) and the managers of the account it belongs to. For anyone else it doesn't exist.

Still stuck? Ask in the support channel on the DevNet Discord, or see how support works on your plan.