Skip to content
Document
Contracts
Typical fields
parties · effective_date · term · contract_value
Output
JSON · Excel · CSV
Plans
$0 · $9.90 · $100 · Custom

Contracts in.
Terms and clauses out.

Contract data extraction at intake: parties, dates, amounts and the clauses you name are read when a contract arrives and returned as fields for your CLM, CRM or tracking sheet.

30 minutes · no commitment

SampleRESULT · services-agreement.pdfJSON
{  "extracted_data": [    {      "parties": ["Acme Supplies Inc.", "Orion Ltd."],      "subject_matter": "Warehouse services",      "effective_date": "2026-03-01",      "term": "36 months",      "auto_renewal": true,      "contract_value": 184200.00,      "payment_terms": "Net 30",      "penalty_termination": "60 days notice",      "escalation_index": "CPI, yearly",      "jurisdiction": "England and Wales",      "signatures": 2,      "annexes": ["Schedule A", "Schedule B"]    }  ]}

Fictional contract; values are illustrative. Only the extracted_data of a result is shown.

What changes at contract intake.

01
Process
How the work changes

Done by hand

  • A person reads each contract and fills in a tracking sheet.
  • Renewal terms and escalation clauses are found by opening the contract.
  • A question across the portfolio means opening contracts one by one.

With Parser

  • Parties, dates, amounts and the clauses you name in the template are read from each contract.
  • Long documents are read as a whole, not in chunks, so a clause near the start can be checked against a table near the end.
  • The fields go to your CLM, CRM or tracking sheet by webhook or API, or as Excel or CSV. Dates arrive as fields, so your own system can set its alerts.
02
Fields
Typical fields and a sample

Fields come from your extraction template.

These are the fields contracts usually carry. Name a clause in the template and it becomes a field.

  • parties
  • subject_matter
  • effective_date
  • term
  • auto_renewal
  • contract_value
  • payment_terms
  • penalty_termination
  • escalation_index
  • jurisdiction
  • signatures
  • annexes

Field names are set in the template and come back as the keys of the result. Define your own fields in the API guide.

03
Solutions
Where to look next

Related solutions.

  • 3.1

    Invoice processing

    Vendor, tax ID, line items, taxes and due date from invoices and bills.

    Fields vendor tax_id line_items total

    Invoice processing, see use case
  • 3.2

    Receipts & expenses

    Merchant, tax ID, total, taxes and expense category from receipts and proofs of payment.

    Fields merchant tax_id total taxes

    Receipts & expenses, see use case
  • 3.3

    Bank statements

    Account, period, opening and closing balances and one row per transaction from bank statements.

    Fields account_holder account_number period_end closing_balance

    Bank statements, see use case
  • 3.4

    Logistics & freight

    Bills of lading, freight invoices, rate confirmations and delivery receipts, read into shipment fields.

    Fields bol_number shipper consignee gross_weight_lb

    Logistics & freight, see industry
  • 3.5

    Insurance

    Claim forms, policy schedules, certificates of insurance and repair estimates, read into claim and coverage fields.

    Fields claim_number policy_number loss_date claimed_amount

    Insurance, see industry

Your documents are different? Book a demo.

Bring a real contract.

In the demo we process your documents live — no slides, no fluff.

30 minutes · no commitment

  • Self-serve

    Free, Starter ($9.90/month) and Pro ($100/month) start when you sign up. No card required for Free.

  • Enterprise

    By contract · your own model key · an engineer for your team · setup done for you if you want it · POC on your documents.