> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/ecommerce/chargebee/data-overview.md).

# Data Overview

Chargebee exposes a wide range of subscription billing data through Coupler.io. You can export everything from customer profiles and subscription lifecycles to individual transactions, pricing catalogs, and audit events.

## Available entities

| Entity                        | Best used for                                     |
| ----------------------------- | ------------------------------------------------- |
| Subscriptions                 | MRR tracking, churn analysis, lifecycle reporting |
| Customers                     | Segmentation, cohort analysis                     |
| Invoices                      | Revenue recognition, accounts receivable          |
| Transactions                  | Payment success/failure rates, cash flow          |
| Credit notes                  | Refund tracking, adjustments                      |
| Unbilled charges              | Pending revenue, billing cycle forecasting        |
| Plans & Items                 | Pricing catalog analysis                          |
| Coupons & Promotional credits | Discount usage and impact                         |
| Events                        | Audit trail, integration debugging                |
| Quotes                        | Sales pipeline, pre-billing activity              |

## Key fields by entity

#### Subscriptions

| Field                                     | Description                                     |
| ----------------------------------------- | ----------------------------------------------- |
| `id`                                      | Unique subscription ID                          |
| `customer_id`                             | Linked customer                                 |
| `plan_id`                                 | Associated plan                                 |
| `status`                                  | active, cancelled, paused, etc.                 |
| `current_term_start` / `current_term_end` | Current billing period                          |
| `mrr`                                     | Monthly recurring revenue for this subscription |
| `created_at`                              | Subscription creation timestamp                 |
| `cancelled_at`                            | Cancellation timestamp (if applicable)          |
| `currency_code`                           | Billing currency                                |

#### Customers

| Field             | Description                |
| ----------------- | -------------------------- |
| `id`              | Unique customer ID         |
| `email`           | Customer email             |
| `company`         | Company name               |
| `billing_address` | Full billing address       |
| `taxability`      | Tax status                 |
| `created_at`      | Account creation timestamp |

#### Invoices

| Field             | Description                        |
| ----------------- | ---------------------------------- |
| `id`              | Invoice ID                         |
| `customer_id`     | Linked customer                    |
| `subscription_id` | Linked subscription                |
| `status`          | paid, posted, payment\_due, voided |
| `amount_due`      | Outstanding balance                |
| `amount_paid`     | Amount collected                   |
| `total`           | Invoice total                      |
| `date`            | Invoice date                       |
| `currency_code`   | Billing currency                   |

#### Transactions

| Field             | Description              |
| ----------------- | ------------------------ |
| `id`              | Transaction ID           |
| `customer_id`     | Linked customer          |
| `subscription_id` | Linked subscription      |
| `amount`          | Transaction amount       |
| `status`          | success, failure, voided |
| `payment_method`  | Payment method type      |
| `date`            | Transaction date         |

#### Plans & Item prices

| Field                    | Description                     |
| ------------------------ | ------------------------------- |
| `id`                     | Plan or item price ID           |
| `name`                   | Display name                    |
| `price`                  | Price in smallest currency unit |
| `period` / `period_unit` | Billing frequency               |
| `status`                 | active, archived                |
| `currency_code`          | Currency                        |

## Common metric combinations

* **MRR by plan**: Join **Subscriptions** + **Plans** on `plan_id` to break down recurring revenue by product tier
* **Revenue vs. refunds**: Join **Invoices** + **Credit notes** on `customer_id` to compare billed vs. returned amounts
* **Payment failure rate**: Use **Transactions** filtered by `status = failure` against total transaction count
* **Churn cohorts**: Use **Subscriptions** with `cancelled_at` and `created_at` to build monthly cohort churn tables
* **Discount impact**: Join **Invoices** + **Coupons** to measure revenue lost to discounts

## Use cases by role

{% tabs %}
{% tab title="Finance" %}

* Pull **Invoices** and **Transactions** into Google Sheets or BigQuery to automate revenue recognition
* Use **Unbilled charges** to forecast upcoming billing cycle totals
* Combine **Credit notes** with **Invoices** to reconcile net revenue
* Send invoice summaries to ChatGPT or Claude for automated narrative reporting
  {% endtab %}

{% tab title="Growth & Marketing" %}

* Analyze **Coupons** and **Promotional credits** to measure discount campaign ROI
* Segment **Customers** by plan or acquisition date to build targeted outreach lists
* Track **Subscription** upgrades and downgrades to identify expansion revenue trends
  {% endtab %}

{% tab title="Product & Operations" %}

* Monitor **Events** for unusual activity or integration issues
* Use **Subscriptions with scheduled changes** to anticipate upcoming plan transitions
* Pull **Hosted pages** data to analyze checkout conversion patterns
* Join **Items** + **Item prices** to audit your pricing catalog across currencies
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Chargebee uses cents (or the smallest currency unit) for monetary fields — divide by 100 to get standard decimal values in your destination
* The `status` field on Subscriptions uses Chargebee's native values: `active`, `in_trial`, `cancelled`, `paused`, `future`, `non_renewing`
* The **Events** entity is useful for debugging webhook failures but can be high-volume — set a specific start date to avoid pulling unnecessary history
* If you use Chargebee's Product Catalog v2, use **Items**, **Item prices**, and **Item families** instead of the legacy **Plans** and **Addons** entities
* Timestamps in Chargebee are returned as Unix epoch integers — most BI tools will need a conversion step


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/ecommerce/chargebee/data-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.