Structure & Extraction

When Tabs processes a contract, it reads the document and converts legal language into structured billing data linked to the customer record.

Supported document types

Tabs reads and processes entire agreements — not just a single document type. Every document is automatically classified against the types below:

What Tabs extracts

Once ingested, Tabs extracts structured data such as:

What’s on a contract record

Each contract in Tabs has:

Within each contract, Tabs organizes billing into billing term groups — the unit that ties billing and revenue recognition together. Each group contains one or more billing terms (what gets billed) and one or more performance obligations (how revenue is recognized).

You can view the billing and revenue impact of each product on a contract through the Billing Schedule and Revenue Schedule charts in the app.

Writing contracts for accurate extraction

Tabs uses AI to parse your agreements. Clear contract structure leads to faster processing and fewer review cycles.

Customer and billing contact

• Include the email address that will receive invoices
• Provide a full physical billing address

Term definitions

• Service term — clear subscription start and end dates for accurate revenue recognition
• Usage term (in arrears) — clearly define the period for which usage data will be processed and billed

Billing frequency and dates

• Specify whether billing is annual, semi-annual, quarterly, monthly, daily, or one-time
• Define critical dates:
  • Invoice date — when the invoice will be issued
  • Signature date — when the contract becomes legally binding
  • Effective date — when the service term starts

Payment terms

• State net terms explicitly (e.g. Net 30)
• Include late charges or credit card fees if applicable
• Define cancellation conditions and any waived fees or promotions
• Label tax lines explicitly (e.g. “VAT” vs. “GST”) so they map to the correct field

Pricing structure

• Flat fees — clearly define quantity and rate
• Usage and tiered fees — provide detailed tier breakpoints and per-unit costs
• Milestones — for milestone-based billing, specify the exact amount and the triggering event or date for each milestone; vague milestone language is a common source of inaccurate billing schedules
• Overages — if usage beyond a commitment is billed at a different rate, state the per-unit overage rate explicitly, rather than leaving it to be configured manually
• Name line items exactly as they should appear on invoices
• Include escalators with percentage increases for multi-year contracts

File quality

• Keep contract PDFs under 40MB
• Use text-selectable PDFs rather than scanned images where possible — they process faster and more accurately, and heavily redacted or scanned documents can bloat file size