> ## Documentation Index
> Fetch the complete documentation index at: https://docs.royaltyport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Curve Overview

> What is Curve, key conceptual differences, account types, and recommended workflow

## What is Curve?

[Curve](https://www.curveroyaltysystems.com/) is a royalty calculation software package used by labels and publishers to perform royalty calculations and pay out artists and writers. Royaltyport integrates with Curve so you can use your contract and catalog data from Royaltyport to drive what gets synced into Curve.

## Royaltyport and Curve Together

Think of **Royaltyport as the brain** and **Curve as the engine**. Royaltyport holds your agreements, parties, and catalog as extracted from signed contracts and statements. The integration maps that data into Curve’s model (payees, contracts, releases, tracks) and keeps it in sync. Curve remains the system where royalty calculations and payouts are configured and run.

## Key Conceptual Differences

| Aspect              | Royaltyport                                                                                                                                           | Curve                                                                                                                                                                                                                                        |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Parties**         | Stores all parties from agreements — multiple assignors, and every related party (including those who don’t receive royalties).                       | Only **payees**: parties you need to pay.                                                                                                                                                                                                    |
| **Agreements**      | **Incoming and outgoing** — we know which side your project entity (or its aliases) is on.                                                            | Only **outgoing** obligations to payees.                                                                                                                                                                                                     |
| **Configuration**   | Data comes from extracted contracts and statements.                                                                                                   | Users configure and map territories, channels, catalog groups, sales terms, etc. The integration picks the best option when syncing and checking; it works best when your Curve account is set up to support the types of contracts you use. |
| **Project mapping** | One Royaltyport **project** maps to one Curve **account**. If your company uses multiple Curve accounts, use a similar split in Royaltyport projects. |                                                                                                                                                                                                                                              |

## Account Types

Curve has separate account types for **labels** (recording) and **publishers** (publishing). Fields for sales terms, catalog items, and checks differ slightly between them. You configure and store credentials separately for Label and Publisher in the integration.

## Current Sync Scope

The integration currently supports a **full two-way sync** of:

* **Entities** — Royaltyport entities ↔ Curve payees
* **Catalog** — Releases and tracks (recordings/products) ↔ Curve releases and tracks
* **Contracts** — Including sales terms, participation rates, and cost rules per contract

<Note>
  Synchronisation of **periodic costs** and **sales/revenue statements** will follow in a later release.
</Note>

## Recommended Workflow

1. **Enter credentials** for your Label and/or Publisher Curve account.
2. **Test the connection** to confirm API access.
3. **Activate the connection** — an initial scan will attempt to match entities, catalog, and contracts.
4. **Complete linking** from right to left: first **entities/payees**, then **catalog**, then **contracts** (and fix any contract alerts where needed).
5. **Only then** start **runs** to sync new contracts and data to Curve.

```mermaid theme={null}
flowchart LR
  subgraph setup [Setup]
    Creds[Credentials]
    Test[Test]
    Activate[Activate]
  end
  subgraph link [Linking Order]
    Entities[Entities]
    Catalog[Catalog]
    Contracts[Contracts]
  end
  subgraph run [Sync]
    Runs[New Runs]
  end
  Creds --> Test --> Activate --> Entities --> Catalog --> Contracts --> Runs
```

## Next Steps

<Card title="Setup" icon="cog" href="/projects/settings/integrations/curve/setup">
  Enter credentials, test, and activate the Curve connection.
</Card>

<Card title="Linking Overview" icon="link" href="/projects/settings/integrations/curve/linking-overview">
  Why linking matters and the order to follow.
</Card>