DISTROBOLT ARTIST GUIDES

Can one release repay costs from another? Questions to agree

Using income from one release to recover another release’s costs is a question of agreement scope and accounting authority. Do not treat it as a default consequence of sharing an artist, label or distribution account.

Name the proposed recovery scope

List the releases, recordings, recipients, cost types, income categories and periods involved. Identify the actual agreement clause being relied on. Songtrust describes cross-collateralisation as a contractual concept; that does not establish that any particular DistroBolt account or collaborator has agreed to it.

Ask the boundary questions

Which costs are approved and evidenced? Which income can be used? Is the recovery capped or time-limited? Who bears a loss and who approves changes? Does the arrangement affect only one owner’s income or another collaborator’s share too? Keep unanswered questions unresolved rather than filling them with a convenient platform setting.

Preserve separate ledgers

Example: Release A has an unrecovered cost balance while Release B earns income. Record both independently until the actual agreement and authorised treatment are confirmed. Do not erase B’s accepted split or merge balances merely because both releases appear in one dashboard. Publishing, recording and other income may have separate contractual treatment.

Review before implementation

Obtain appropriate legal and accounting advice for the actual documents and jurisdiction where scope is unclear or disputed. Confirm what DistroBolt can support operationally; a software capability would not itself create permission. Keep written approval, allocation calculations and effective periods, then verify any authorised result against statements. This guide neither grants cross-release recovery rights nor activates a recoupment engine.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.