Skip to content
SoundSyncAudio software platform

Collaborator Revenue Sharing

Collaborator Revenue Sharing

Allocate product revenue to contributors without sharing your owner login or granting customer-record access.

Updated 2026-11-13

Give contributors their own eligible balance

Each accepted collaborator allocation is tracked separately from the developer remainder. Eligible previous-period earnings and older unpaid balances enter the 1st and 15th payout schedule after the assigned sales period’s approximately two-week wait.

The same destination, account, refund and dispute checks apply. Allocated earnings, an eligible payout and a completed payment are different states; sharing a product does not require sharing the owner login.

Collaborator revenue sharing is supported

SoundSync supports collaborators with product-specific revenue-sharing agreements and separately tracked earnings. Agree each contributor's share without sharing your owner login; dashboard access belongs to the separate Team Accounts system.

Agree how a product's revenue is shared

Collaborator agreements record who participates in a product and the share proposed for each eligible product. Use them for product contributions without sharing the developer owner account or giving every contributor access to customer records.

Confirm who participates in each product

Both the developer owner and collaborator accept the current agreement version and payout policy before future eligible one-time sales accrue a share. Product assignments, effective dates and the accepted rates define the contribution agreement.

This allocation path does not cover subscriptions or rent-to-own. A collaborator agreement also does not grant a workspace role or access to customer records.

SoundSync

Collaboration is not workspace access

RelationshipWhat it grants
Collaborator agreementAccepted product-specific revenue-sharing terms and separately authorized live participation
Team accountA separately assigned role and product scope for dashboard work
Reseller relationshipApproved external sales and fulfillment arrangements
Affiliate agreementReferral terms, supported attribution, and eligible sale allocations

Keep terms and capacity explicit

Review product assignments, rates, effective dates and the accepted version. Multiple collaborators share the post-affiliate remainder. Paused collaborator agreements retain their allocation capacity so resuming cannot exceed a complete product allocation. Ending an agreement preserves its history rather than deleting accepted terms.

Keep contribution shares separate through adjustments

Collaborator shares use the remainder after the 3% SoundSync fee and any accepted affiliate share. Actual checkout processing fees are billed separately to the developer; external sellers pay their own providers.

Changing an agreement does not rewrite a completed sale. Refunds reverse the original affected shares, already-paid amounts are recovered from future earnings, and unresolved adjustments can hold the balance. Outside payments remain separate, unfunded estimates in SoundSync settlement reporting.

SoundSync

An after-fee split example

StepAmount
Discounted pre-tax product revenue$100.00
SoundSync fee (3%)$3.00
Remaining revenue$97.00
Illustrative affiliate share: 20% of $97.00$19.40
Illustrative collaborator share: 25% of $77.60$19.40
Developer remainder before actual processing/payout fees and other account charges$58.20
Actual provider feesBilled separately to the developer; excluded from partner shares and SoundSync minimum

SoundSync

Collaborate without sharing credentials

Collaborator guide

Product scope, proposals, acceptance and status.

Team roles

Separate access permissions.

Program payout model

After-fee shares, funding and adjustments.

Program API

Versions, live consent, and scoped recipient balances.

SoundSync

Give each collaborator a clear product share

Agree the effective date, default share, and product-specific rates without sharing your developer login.

Collaborators - Private account details and business metrics are blurred.