About Tabs

View as Markdown

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 & Receivables for how the Collections Agent 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 to link deals to the right account.
  2. Products and billing terms are configured — reusable 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 connect CRM, ERP, payments, and tax.

Contract-to-cash lifecycle

For entity definitions and a worked example, see Tabs data model.

Explore Getting Started

Customers

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

Contracts

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

Product Catalog

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

Billing

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

Collections & Payments

Receivables workflows, payment collection, cash application, and credits.

Revenue

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

Reporting

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

Integrations

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

Key concepts

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 for invoice generation and Revenue for recognition and close.

Tabs is the source of truth for invoices. Sent invoices, payments, and revenue journal entries flow from Tabs to your ERP. Changes made directly in your ERP to Tabs-sent invoices do not sync back. See Integrations for sync behavior and ERP & Account Mapping for setup.

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 before processing.

Build with the API

Tabs data model

Entity definitions, relationships, and a worked billing example.

Invoice a customer

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

Develop with the Tabs API

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

Further reading