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

# Billing & Subscriptions

> Sync billing data from Stripe or Chargebee into Introw and use it to calculate partner commissions on real, recognized revenue.

> Commissions should be paid on real revenue, not estimates. The billing integration brings your Stripe or Chargebee data into Introw so commission plans calculate against actual customers, subscriptions, and invoices.

## What it does

The billing integration connects Stripe or Chargebee to Introw and imports billing objects, customers,
subscriptions, invoices, products, and prices, so they are available as a data source for commissions.
You map billing properties to link records to the right partner, and the imported data becomes a
commission plan source, letting you pay partners on actual recognized revenue.

You connect in live or test mode, define which billing objects and properties to bring in, and link
billing records to partners. Imports run on a schedule, and you can trigger a sync manually. This is
an import into Introw, billing data flows in to power commissions, while Stripe remains the system
that actually charges customers.

## The problem it solves

Commissions calculated outside billing data drift from reality:

* **Commissions use estimates** → Plans calculate on real Stripe revenue.
* **Billing lives in another system** → Billing objects import into Introw.
* **Records are not tied to partners** → Property mapping links revenue to partners.
* **Reconciliation is manual** → Scheduled sync keeps billing data current.

## From problem to solution

The Stripe integration grounds commissions in actual revenue. Import billing data, link it to
partners, and use it as a commission source, so payouts reflect what customers really paid.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  import["Import billing data"] --> link["Link to partners"]
  link --> source["Commission source"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Pay on real revenue" icon="circle-check">
    Use Stripe data for commissions.
  </Card>

  <Card title="Import billing objects" icon="circle-check">
    Bring in invoices and subscriptions.
  </Card>

  <Card title="Attribute revenue" icon="circle-check">
    Link billing records to partners.
  </Card>

  <Card title="Keep data current" icon="circle-check">
    Sync on a schedule or on demand.
  </Card>
</CardGroup>

## Impact

* **CRM-native** - Billing data complements your CRM as a commission source.
* **Trust & accuracy** - Commissions calculate on real, reconciled revenue.

## Who it's for

<CardGroup cols={2}>
  <Card title="RevOps" icon="user">
    Connects Stripe and maps billing data.
  </Card>

  <Card title="Finance" icon="user">
    Ensures commissions reflect real revenue.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Commission Plans" icon="hand-holding-dollar" href="/features/commissions/commission-plans">
    Commissions calculate on billing revenue.
  </Card>

  <Card title="Payouts" icon="hand-holding-dollar" href="/features/commissions/payouts">
    Reconcile payouts to invoices.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>