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

# Overview

Custom contract terms (a special usage allowance, a delayed discount, a one-off renewal clause) often exist only in the signed document, not in any system. Engineering approximates them in the entitlements system; finance approximates them again in a coupon or line item. The two can drift, especially after an amendment.

Contract Management removes the second copy: a contract in Stigg is a single object that provisions a customer's entitlements and drives their invoices, so what you enforce and what you bill can never fall out of sync.

## How it works

A contract represents a signed order form: the sales agreement, whether a PDF or a Salesforce opportunity, that defines what the customer bought. Creating a contract in Stigg attaches that order form and brings together two things that are normally managed separately:

* **Entitlement provisioning**: achieved by creating [subscriptions](../subscriptions/provisioning-subscriptions) to [custom plans](../../modeling-your-pricing-in-stigg/plans/custom-plans), so what a customer signs is what Stigg enforces.
* **Invoice generation**: achieved by setting up a **billing contract**, which defines the payment terms, billing schedule, and line items used to generate invoices.

A contract can include entitlement provisioning, invoice generation, or both, depending on what a given customer needs.

When a contract includes a [metered feature](../../modeling-your-pricing-in-stigg/features/creating-features/metered-features) (like API calls or seats), usage flows directly from the subscription into the billing contract, so it's reflected in invoices automatically:

<img src="https://mintcdn.com/stigg/EUqSVNUnZWIVqrn0/images/docs/contract-management-overview.png?fit=max&auto=format&n=EUqSVNUnZWIVqrn0&q=85&s=7bdce75978f6fd4cbd5fbc154d45e16d" alt="A contract splits into entitlement provisioning (via subscriptions to custom plans) and invoice creation (via billing contract), with usage data flowing from entitlement provisioning into invoice creation" width="1499" height="1049" data-path="images/docs/contract-management-overview.png" />

See [Setting up a contract](./setup-flow) to get started, or [Usage-based billing](./usage-based-billing) for more on how usage data flows into invoices.

## Benefits

Contract Management gives enterprise invoicing the same flexibility teams otherwise get from spreadsheets and custom scripts, without leaving Stigg or reconciling data by hand.

* **Maximum flexibility for enterprise invoicing** supports:
  * Any line item
  * Any pricing model
  * Any billing period
  * Any billing cadence (in advance or in arrears)
  * Any payment terms
  * Consolidate line items into one invoice, or bill any of them on a separate invoice, per your choice
  * Invoice anchors (set which date a separate invoice's billing cycle starts from)
* **Native integration with Stigg's product catalog**: contract line items can be mapped directly to the plans, add-ons, and features already modeled in your product catalog.
* **Native integration with Stigg's metering infrastructure**: bill usage-based enterprise contracts instantly, using the same usage that's reported to Stigg.
* **Works alongside your existing billing stack**: Contract Management orchestrates entitlement provisioning and invoicing on top of tools like Stripe Billing and NetSuite. It doesn't replace them, and your existing product-led motions are unaffected.
* **End-to-end AI monetization**: Stigg is the only solution that provides a single experience for both enterprise entitlement provisioning *and* invoicing, so the two never drift apart.

## Availability

<Note>
  Contract Management is currently in **beta**.
</Note>


## Related topics

- [Overview](/documentation/modeling-your-pricing-in-stigg/products/overview.md)