# Ingesting your Rights

### Ingesting Client Accounts and Royalty Splits

To generate statements and manage royalty reporting for your rights holders, add them as Payees via **Contracts** in Revelator.

### 3.1 Adding Payees

* You can add Payees manually in the Revelator dashboard or in bulk by filling out our **Contracts Worksheet**.

### 3.2 Understanding Contracts

Contracts define how DSP revenue is split between your company and your Payees. A Contract contains:

1. **Terms**
   * Defines the payout rate(s) for DSPs, territories, channels, and formats.
   * You can have multiple terms (e.g., different rates for YouTube ContentID vs. other services).
2. **Payees**
   * Once the Payout Revenue is determined by the Terms, distribute the shares among Payees.
   * Specify each Payee’s email, PayPal email (optional), share percentage, and initial balance (positive or negative).
   * Depending on your account setup (Parent-Child vs. Standalone), Payees might be able to create releases (Distribution Payees) or only view data (Payee Portals).
   * **Commission Payees**: A commission payee’s share is deducted from the distribution fee (your cut), not from the licensor’s royalties.
3. **Assets**
   * Define which assets the Contract Terms and Splits apply to.
   * This can be at the Account, Label, Artist, Release, or Track level.

### **3.2.1 For Parent-Child Accounts**

* An **Account-Level Contract** for each Child Account covers all catalog under that Child Account by default.
* By default, non-Enterprise plans have 100% payout to the Child Account. Adjust case by case if needed.
* **Label/Artist/Release/Track-Level Contracts** override the default Account-Level Contract for the specified assets (see the Sample Data in the Contracts Worksheet).

### **3.2.2 For Standalone Accounts**

* Only you (the Account Owner) and Team Members can create and distribute releases.
* Payees are invited to **Payee Portals** to view assets, statements, analytics, and distribution status but cannot edit or distribute unless otherwise specified.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.revelator.com/pro/getting-started/onboarding-to-revelator/ingesting-your-rights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.