Extract data from joint venture agreements

A joint venture agreement is what two or more companies sign when they want to pursue one project together without merging their businesses. It sets up a shared undertaking with a defined purpose, splits the ownership, and spells out who puts in what, who runs it, and how the profits and any jointly created intellectual property are shared. A joint venture is narrower than a partnership, which is an ongoing firm, and different from a master services agreement, which governs a supplier relationship: here the parties are co-owners of a single venture, and the document reads like a constitution for that venture. In-house counsel, corporate development teams, and the finance staff who consolidate the venture all pull the same terms from it. The terms that decide control are the equity split, the capital contributions, and the governance, and they have to line up. Each party's equity percentage should track its capital contribution, so if one side funds 60 percent it usually holds 60 percent and takes 60 percent of the profit, and the contributions have to foot to the total committed capital. Board composition and reserved matters decide who can block a decision, the profit-sharing ratio decides who takes the return, and the joint-IP clause decides who owns what the venture invents. Because a joint venture is built to end, the term, the exit and change-of-control provisions, the non-compete, and the dispute-resolution forum all shape how the parties unwind it. These clauses follow the CUAD contract taxonomy, so they resolve to named categories rather than loose prose. Talonic reads the joint venture agreement and returns the parties and their roles, the equity split, the capital contributions, the profit-sharing ratio, the governance structure, and the joint-IP and change-of-control clauses as typed fields, keeping the parties, the contributions, the profit distribution, and the management roles as tables. An agreement between Aurora Renewables Inc. (60 percent, operator) and Meridian Infrastructure Partners LLC (40 percent, investor) forming Aurora Meridian Solar JV LLC to develop a 120 MW solar project in Andalusia, effective 2026-07-01 for a 10-year term, where the agreement states capital contributions of 30,000,000 EUR from Aurora and 20,000,000 EUR from Meridian toward a total committed capital of 50,000,000 EUR, loads into a contract system instead of a marked-up draft. Talonic structures the terms as written and does not judge whether a provision is enforceable.

What gets extracted from joint venture agreements

How extraction works for joint venture agreements

Joint venture agreements are drafted from firm precedents and negotiated across redlines, so the equity, funding, and governance terms sit in different sections from one deal to the next. Talonic reads the agreement and resolves each clause to the CUAD-based contract field set the Field Registry maintains, so the parties and roles, the venture purpose and location, the profit-sharing ratio, the management structure, and the exit clauses each land in their own field. Equity percentages and per-party contribution amounts are typed as numbers in their currency, so the 60-40 equity split and the profit-sharing ratio read as grounded fields and each party's contribution stays tied to its own amount and currency. The parties, the capital contributions, the profit distribution, and the management roles each return as a table, the effective and expiration dates parse to ISO 8601, and the non-compete, change-of-control, audit-rights, and joint-IP clauses are captured under their named categories. Every value carries a confidence score and a source-region pointer under DIN SPEC 91491, so counsel can verify a contribution amount or a governance term against the signed agreement. Talonic returns the terms as written and does not decide whether a clause is binding or how the venture should be run.

Sample extraction

A two-party joint venture agreement for a solar project

{
  "document_number": "JV-2026-0417",
  "document_date": "2026-06-18",
  "effective_date": "2026-07-01",
  "expiration_date": "2036-06-30",
  "venture_name": "Aurora Meridian Solar JV LLC",
  "venture_purpose": "Develop, build, and operate a 120 MW solar photovoltaic project in Andalusia, Spain",
  "venture_location": "Andalusia, Spain",
  "profit_sharing_ratio": "60:40",
  "governing_law": "Spain",
  "dispute_resolution": "ICC arbitration seated in Madrid",
  "management_structure": "Board of five directors: three appointed by Aurora Renewables, two by Meridian Infrastructure",
  "joint_ip_ownership": "Jointly owned by the venture, licensed back royalty-free to each party for its own use",
  "change_of_control": "Consent of the non-transferring party required for any change of control of a member",
  "non_compete": "Neither party to develop a competing solar project within 50 km for the term",
  "audit_rights": "Either party may audit the venture books on 20 business days notice",
  "parties": [
    {
      "party_name": "Aurora Renewables Inc.",
      "party_role": "operator",
      "equity_percentage": 60
    },
    {
      "party_name": "Meridian Infrastructure Partners LLC",
      "party_role": "investor",
      "equity_percentage": 40
    }
  ],
  "capital_contributions": [
    {
      "party_name": "Aurora Renewables Inc.",
      "contribution_amount": 30000000,
      "currency": "EUR"
    },
    {
      "party_name": "Meridian Infrastructure Partners LLC",
      "contribution_amount": 20000000,
      "currency": "EUR"
    }
  ],
  "profit_distribution": [
    {
      "party_name": "Aurora Renewables Inc.",
      "distribution_ratio": "60%"
    },
    {
      "party_name": "Meridian Infrastructure Partners LLC",
      "distribution_ratio": "40%"
    }
  ]
}

Frequently asked