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

# About Tabs

**Tabs** is an AI-native revenue platform for finance teams. It ingests contracts and customer data, turns legal terms into structured billing, generates and collects invoices, recognizes revenue, and syncs everything to your ERP — on one system instead of spreadsheets and bolt-on tools.

Tabs agents automate routine work like invoice preparation, collections replies, and reconciliation. Your team stays in control with approvals and exception handling when judgment is needed. See [Collections Agent](/collections-agent) for how it handles inbound email.

These docs cover two paths:

* **Getting Started** (this tab) — product concepts and workflows for finance and ops teams
* **API Guides** — implementation, integrations, and programmatic access for developers

## How revenue operations flow through Tabs

Every billing operation in Tabs follows the same contract-to-cash lifecycle:

1. **Customers and contracts enter Tabs** — via CRM sync, e-signature, email ingest, or API. CRM customers often arrive before their contracts; use [Confirm Customer](/customer-ingestion#confirm-customer) to link deals to the right account.
2. **Products and billing terms are configured** — reusable [Product Catalog](/product-catalog) entries define what you sell; billing terms on each contract define pricing, cadence, and schedule for that customer.
3. **Invoices are generated and sent** — billing terms create draft invoices on schedule; sent invoices sync to your CRM, ERP, and tax providers.
4. **Payments are collected and applied** — Stripe, Plaid, and manual recording settle invoice balances and sync cash to your ERP.
5. **Revenue is recognized and closed** — performance obligations and revenue schedules decouple recognition from billing; month-end close posts journal entries to your ERP.
6. **Reporting and integrations tie it together** — AR, forecasting, and commercial metrics draw from the same data; [Integrations](/integrations) connect CRM, ERP, payments, and tax.

![Contract-to-cash lifecycle](/_fern-img/95e1b34c41330cdba7fd18516135a881662f7cc92ae137a54e7be2402a9f241d.webp)

For entity definitions and a worked example, see [Tabs data model](/data-model).

## Explore Getting Started

#### [Customers](/customers)

Customer records, billing contacts, and how accounts enter Tabs from CRM and ERP.

#### [Contracts](/contracts)

How deals become structured billing data — ingestion, extraction, and amendments.

#### [Product Catalog](/product-catalog)

What you sell — pricing models, cadence, revenue dates, and invoice timing.

#### [Billing](/billing)

Billing terms, schedules, invoice generation, and ERP sync.

#### [Payments](/payments)

Recording payments, Stripe and Plaid, cash application, credits, and ERP sync.

#### [Collections](/collections)

Receivables workflows, dunning, the Collections Agent, and AP portal submission.

#### [Revenue](/revenue)

Revenue recognition, performance obligations, SSP allocation, and month-end close.

#### [Reporting](/reporting)

Aging, cash forecasting, renewals, ARR, and commercial visibility.

#### [Integrations](/integrations)

CRM, ERP, payments, and tax — architecture, setup, and troubleshooting.

## Key concepts

> **Note**
>
> **Billing and revenue are separate.** A customer can be invoiced on one schedule and recognize revenue on another — for example, usage billed monthly in arrears with revenue recognized ratably over the contract term. See [Billing](/billing) for invoice generation and [Revenue](/revenue) for recognition and close.

> **Note**
>
> **Tabs is the source of truth for invoices.** Sent invoices, payments, and revenue journal entries flow from Tabs to your ERP, and edits made to a Tabs-sent invoice in your ERP do not come back. Some activity does flow the other way: payments applied in your ERP sync back to Tabs, as does an ERP-side credit memo application, which arrives as a payment. See [Integrations](/integrations) for sync behavior and [ERP & Account Mapping](/erp-account-mapping) for setup.

> **Tip**
>
> **CRM customers arrive before contracts.** HubSpot and Salesforce syncs create customer records first; contract sync links closed-won deals to those accounts. If a contract lands on the wrong customer, use [Confirm Customer](/customer-ingestion#confirm-customer) before processing.

## Build with the API

#### [Tabs data model](/data-model)

Entity definitions, relationships, and a worked billing example.

#### [Invoice a customer](/invoice-customer-quickstart)

Define billing terms and send your first invoice via the API.

#### [Develop with the Tabs API](/develop-with-api)

Authentication, core endpoints, usage events, and the Tabs MCP Connector.

## Further reading

* [Tabs data model](/data-model) — entity definitions and relationships
* [Integration Overview](/integration-overview) — CRM, ERP, payments, and tax architecture
* [Develop with the Tabs API](/develop-with-api) — authentication, endpoints, and rate limits