SEBI Compliance for Listed Entity Contracts: A Complete Guide

This guide covers every SEBI regulation that touches contracts for listed entities, the mandatory clauses your legal team must include, and how AI-powered contract intelligence platforms like LexiReview automate compliance checks so nothing slips through the cracks.

Why SEBI Compliance in Contracts Matters More Than Ever

SEBI has steadily tightened the screws on listed entity governance since 2020. The regulator issued over 1,200 enforcement orders in the 2023-24 financial year alone, and contractual non-compliance featured prominently in show-cause notices related to:

• Undisclosed related party transactions
• Late or missing material event disclosures under Regulation 30
• Insider trading violations traced to contractual arrangements with promoters and key managerial personnel
• Failure to obtain audit committee or shareholder approval for RPTs above threshold limits

For corporate legal teams, the challenge is not awareness — it is operationalising compliance across hundreds of contracts executed each quarter. A single vendor agreement that qualifies as a related party transaction but bypasses the approval workflow can trigger a SEBI investigation.

The LODR Framework: Regulations That Directly Impact Contracts

The SEBI (Listing Obligations and Disclosure Requirements) Regulations 2015 form the backbone of contractual compliance for listed entities. Here are the regulations your contracts must address.

Regulation 23: Related Party Transactions (RPT)

Regulation 23 is arguably the single most impactful provision for contract management in listed companies. It requires:

1. Prior audit committee approval for all RPTs, regardless of value
2. Prior shareholder approval for material RPTs exceeding the prescribed threshold (transactions exceeding ₹1,000 crore or 10% of annual consolidated turnover, whichever is lower)
3. Arm's length pricing certification — every RPT contract must demonstrate that terms are no less favourable than those available to unrelated parties
4. Half-yearly disclosure of RPTs in the prescribed format to stock exchanges

What this means for contracts: Every agreement with a related party — whether a subsidiary, associate, promoter group entity, or KMP-linked entity — must contain arm's length pricing justification, reference the audit committee approval date and resolution number, and include a clause permitting the listed entity to terminate or renegotiate if the arrangement ceases to satisfy arm's length norms.

Regulation 30: Disclosure of Material Events

Regulation 30 read with Schedule III mandates that listed entities disclose every "material" event or information to stock exchanges within 30 minutes of board approval (for board-level decisions) or within 24 hours of occurrence (for other events). Contracts trigger Regulation 30 obligations when they involve:

• Acquisition or disposal of assets exceeding the materiality threshold
• Joint venture or collaboration agreements with strategic significance
• Licensing or franchise agreements that impact revenue materially
• Loan agreements or borrowing arrangements above threshold limits
• Settlement agreements in litigation matters
• Any agreement that is not in the ordinary course of business

Mandatory contract clause: Listed entity contracts that could qualify as material events must include a disclosure acknowledgement clause — the counterparty acknowledges that the listed entity may be required to disclose the existence and material terms of the agreement to stock exchanges, and such disclosure does not constitute a breach of confidentiality obligations.

Regulation 17: Board and Committee Governance

Certain contracts require board-level or committee-level approval based on their nature and value:

• Contracts involving capital expenditure exceeding the threshold set by the board
• Investment decisions including acquisition of shares, assets, or businesses
• Contracts with KMP remuneration implications
• Agreements involving corporate guarantees or pledges

Every such contract must reference the relevant board or committee resolution, and the contract execution date must fall after the approval date — a compliance gap that AI review systems catch consistently.

Insider Trading Regulations and Contractual Safeguards

The SEBI (Prohibition of Insider Trading) Regulations 2015 impose obligations that must be embedded in multiple contract types.

Confidentiality and UPSI Clauses

Any contract that involves sharing Unpublished Price Sensitive Information (UPSI) — including M&A discussions, fundraising negotiations, material supply agreements, or technology licensing deals — must include:

• A clear definition of UPSI aligned with Regulation 2(1)(n) of the PIT Regulations
• Restricted trading obligations — the counterparty must agree not to trade in the listed entity's securities while in possession of UPSI
• Chinese wall provisions where the counterparty is an institutional investor or financial intermediary
• UPSI return or destruction clauses upon termination of the agreement or completion of the transaction

Structured Digital Database (SDD) Compliance

Regulation 3(5) requires listed entities to maintain a structured digital database of every person with whom UPSI is shared. Contracts involving UPSI sharing should include:

• A clause requiring the counterparty to identify all individuals within their organisation who will access UPSI
• Notification obligations if additional individuals are granted access during the contract term
• The right of the listed entity to audit the counterparty's information barriers

Mandatory Contract Clauses for Listed Entities: A Checklist

Based on the regulatory framework above, here is a consolidated list of clauses that SEBI compliance contracts for listed entities must include where applicable:

Disclosure and transparency clauses:

• Stock exchange disclosure acknowledgement (Regulation 30)
• Material event notification trigger mechanism
• Pricing transparency and arm's length certification (Regulation 23)
• Annual and half-yearly disclosure consent

Governance and approval clauses:

• Audit committee approval reference (RPTs)
• Board or committee resolution reference
• Shareholder approval condition precedent (material RPTs)
• Compliance certificate from company secretary

Insider trading safeguards:

• UPSI definition and handling obligations
• Trading restriction acknowledgement
• SDD data provision requirements
• Chinese wall and information barrier commitments
• UPSI destruction or return on termination

Ongoing compliance clauses:

• Regulatory change adaptation clause (permits renegotiation if SEBI amends applicable regulations)
• Audit and inspection rights for compliance verification
• Compliance representation and warranty (both parties warrant ongoing SEBI compliance)
• Indemnification for regulatory penalties arising from counterparty breach

How AI Automates SEBI Compliance Checks in Contracts

Manual compliance review of contracts against SEBI regulations is time-consuming, error-prone, and does not scale. A single corporate legal team reviewing 50-100 contracts per month cannot realistically cross-reference every agreement against Regulation 23 thresholds, Regulation 30 materiality criteria, and insider trading safeguards.

This is where AI-powered contract intelligence changes the equation.

Automated RPT Detection and Flagging

LexiReview's AI engines cross-reference counterparty details against the listed entity's related party register. When a contract involves a party that matches — or potentially matches — the expanded RPT definition, the system flags the agreement for audit committee routing before execution. No manual lookup required.

Regulation 30 Materiality Triggers

The platform evaluates contract value, nature, and terms against the listed entity's board-approved materiality policy. Contracts that cross the threshold are flagged with a disclosure alert, including a draft materiality assessment that the company secretary can use for the stock exchange filing.

UPSI Clause Verification

LexiReview scans every contract for the presence (or absence) of UPSI-related clauses when the agreement type or counterparty profile suggests UPSI sharing is likely. Missing trading restriction clauses, absent SDD provisions, or inadequate UPSI definitions are flagged as compliance gaps with specific remediation suggestions.

Audit Trail for Regulatory Defence

Every review, flag, approval, and modification is recorded in a chain-hashed SHA-256 audit trail. If SEBI issues a show-cause notice, the listed entity can demonstrate a systematic, technology-enabled compliance process — which is increasingly relevant in enforcement proceedings where SEBI evaluates whether the entity took "reasonable steps" to comply.

Start Free SEBI Compliance Checks

Building a SEBI Compliance Workflow for Contract Management

Implementing SEBI compliance in your contract lifecycle requires more than clause libraries. Here is a practical workflow:

Step 1 — Triage and classification. Every incoming contract is classified by type (vendor, customer, investment, JV, licensing, etc.) and automatically checked against RPT registers and materiality thresholds.

Step 2 — AI-powered review. The contract is reviewed against SEBI-specific clause requirements. Missing or non-compliant clauses are flagged with regulatory references and suggested language.

Step 3 — Approval routing. Based on the AI assessment, the contract is routed to the appropriate approval authority — audit committee for RPTs, board for material transactions, compliance officer for UPSI-related agreements.

Step 4 — Execution with compliance metadata. The executed contract is tagged with approval references, disclosure obligations, and compliance deadlines. Integration with e-Office and board portals ensures seamless governance documentation.

Step 5 — Ongoing monitoring. LexiBrain monitors regulatory changes from SEBI circulars, LODR amendments, and enforcement trends. When a regulation changes, affected contracts in the vault are flagged for review and potential renegotiation.

Common SEBI Compliance Gaps in Contracts (And How to Fix Them)

After reviewing thousands of contracts for listed entities, these are the most frequent compliance gaps:

| Gap | Risk | Fix | |-----|------|-----| | Missing RPT classification | Regulation 23 violation, SEBI penalty | Automated counterparty screening against RPT register | | No stock exchange disclosure clause | Confidentiality disputes when filing Regulation 30 disclosures | Standard disclosure acknowledgement clause in all material contracts | | Inadequate UPSI definitions | PIT Regulation breach, insider trading liability | Use SEBI's statutory definition verbatim with contract-specific examples | | No materiality assessment | Late or missed Regulation 30 filings | AI-driven materiality scoring at contract intake | | Missing audit committee approval reference | RPT validity challenge | Workflow-enforced approval gate before execution | | No regulatory change clause | Contracts become non-compliant after SEBI amendments | Standard adaptation clause with 90-day renegotiation window |

Frequently Asked Questions

Which SEBI regulations directly affect contracts of listed entities?▾

The primary regulations are LODR Regulations 2015 (especially Regulations 23, 30, and 17), SEBI (Prohibition of Insider Trading) Regulations 2015, and SEBI (Substantial Acquisition of Shares and Takeovers) Regulations 2011. Depending on the transaction, SEBI's Issue of Capital and Disclosure Requirements (ICDR) Regulations may also apply. Each imposes specific contractual obligations around disclosure, approval, and compliance clauses.

What is Regulation 23 and how does it affect contracts with related parties?▾

Regulation 23 of LODR requires prior audit committee approval for all related party transactions and shareholder approval for material RPTs exceeding ₹1,000 crore or 10% of consolidated turnover (whichever is lower). Contracts must include arm's length pricing justification, approval references, and mechanisms for ongoing compliance monitoring. The definition of "related party" was expanded in 2024 to cover material pecuniary relationships.

When does a contract trigger a Regulation 30 disclosure obligation?▾

A contract triggers Regulation 30 when it constitutes a "material event" under Schedule III of LODR. This includes acquisitions, disposals, JV agreements, significant licensing deals, large borrowings, litigation settlements, and any agreement not in the ordinary course of business that crosses the listed entity's board-approved materiality threshold. Disclosure must be made within 30 minutes of board approval or 24 hours of occurrence.

What UPSI clauses must be included in contracts involving sensitive information?▾

Contracts involving UPSI must define UPSI per Regulation 2(1)(n) of PIT Regulations, impose trading restrictions on the counterparty, require identification of individuals accessing UPSI for the Structured Digital Database, include Chinese wall provisions where applicable, and mandate UPSI return or destruction upon termination. Omitting these clauses exposes the listed entity to insider trading enforcement.

Can AI tools reliably check SEBI compliance in contracts?▾

Yes. AI-powered platforms like LexiReview use multiple parallel engines trained on Indian regulatory frameworks to detect missing clauses, flag RPTs, assess materiality, and verify insider trading safeguards. With 98.5% accuracy and 45-second average review time, AI review significantly outperforms manual checks in both speed and consistency — particularly for high-volume contract portfolios.

What are the penalties for SEBI non-compliance in contracts?▾

Penalties vary by violation. Under Section 15H of the SEBI Act, non-disclosure of material information attracts penalties up to ₹25 crore or three times the profit made. RPT violations can result in disgorgement, debarment of officers, and directions to unwind transactions. Insider trading violations carry penalties up to ₹25 crore or three times the profit made, along with potential criminal prosecution.

How should listed entities handle confidentiality when SEBI requires contract disclosure?▾

Include a stock exchange disclosure acknowledgement clause in all contracts that could qualify as material events. This clause should state that the listed entity may be required to disclose the existence and material terms to stock exchanges, and such disclosure does not breach confidentiality obligations. This prevents disputes when Regulation 30 filings are required.

How does LexiReview help with SEBI compliance for listed entity contracts?▾

LexiReview automates counterparty screening against RPT registers, flags contracts crossing materiality thresholds, verifies the presence of mandatory SEBI clauses (UPSI, disclosure, approval references), maintains chain-hashed SHA-256 audit trails for regulatory defence, and monitors SEBI circulars through LexiBrain for ongoing compliance. Quick Triage provides instant preliminary assessment in under 2 seconds at zero cost.

---

SEBI compliance in contracts is not optional for listed entities — it is a continuous obligation that spans the entire contract lifecycle. The combination of expanding regulatory definitions, shorter disclosure timelines, and stricter enforcement makes automated compliance checks a necessity, not a luxury.

Automate SEBI Compliance in Your Contracts