> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.tabs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.tabs.com/_mcp/server.

# Contracts

A **Contract** in Tabs is the binding agreement with a customer — the deal, order form, or amendment that defines what you're billing and when. Every contract belongs to exactly one customer and serves as the container for the billing terms, revenue schedules, and invoices that flow from it.

## Role in Tabs

Contracts are where Tabs turns legal language into structured billing data. When Tabs ingests a contract, it reads the document, extracts financial terms, and links them to the correct customer record. From there, Tabs generates billing term groups, invoices, and revenue schedules automatically.

The billing lifecycle in Tabs starts at the contract level:

1. A contract is processed on the customer
2. It creates **billing term groups** that tie together **billing terms** and **performance obligations**
3. **Billing terms** generate **invoices**
4. **Performance obligations** generate **revenue schedules**

For the full entity hierarchy, see [Tabs data model](/data-model).

## Explore contracts

#### [Contract Ingestion & Integrations](/contract-ingestion)

How contracts enter Tabs — CRM sync, email ingest, API upload, and processing timelines.

#### [Structure & extraction](/contract-structure)

What Tabs extracts from a contract, what's on the record, and how to write agreements for accurate parsing.

#### [Amendments & lifecycle](/contract-amendments)

Handling contract changes, terminations, and deletions after invoicing has started.