A Related Party Transaction (RPT) is any transaction between a listed company and a person or entity with a pre-existing relationship to it - a subsidiary, holding company, promoter, director, Key Managerial Personnel (KMP), or their relatives. The Companies Act 2013 (Section 188) and SEBI LODR Regulation 23 require listed companies to disclose these transactions to protect minority shareholders. Most RPTs are routine - large companies constantly transact with subsidiaries and group entities (raw materials, IT services, intra-group lending, director remuneration); the disclosure exists so shareholders can verify they happen at arm's length rather than on terms that benefit insiders. VIGIL parses the RPT section from each company's half-yearly Standalone Financials XBRL filing.
Open the live VIGIL Related Party Transactions view to filter by company, relationship group and transaction type.
What companies must file
All listed companies disclose RPTs in their half-yearly results under SEBI LODR Regulation 23, covering every transaction with every related party during the period, with: counter-party name and relationship; nature/type of transaction (sale, purchase, loan, remuneration, investment); value approved by the Audit Committee; actual amount transacted; outstanding balance at period end; and loan details where applicable (interest rate, tenure, secured/unsecured). Large companies (Reliance, HDFC Bank, Bharti Airtel) can have 1,000-2,000+ transactions per filing across hundreds of entities; smaller companies typically have 3-50.
Coverage and frequency
Scope: Nifty Total Market, ~750 companies (Nifty 500 + Nifty Microcap 250). Data period: Sep 2025 and Mar 2025 half-yearly filings; as of March 2026 the database holds ~250,000 transactions across 728 companies. Update: frequent scans during filing season (Oct-Nov for H1, Apr-May for H2), weekly otherwise to catch late filers; most companies file within 45 days of period end. Method: official XBRL filings via NSE's Integrated Filing system, extracted from the Standalone Financials XBRL using the SEBI in-capmkt taxonomy (2022 and 2024 versions).
Missing companies (9 of 751, ~1.2%; 98.8% coverage maintained): ABBOTINDIA, ADANIENT, BAYERCROP, BDL, ENRIN, GRSE, MCX, NIVABUPA, UPL. ADANIENT and UPL have broken XBRL links on NSE; ABBOTINDIA, BAYERCROP, MCX are not in the Integrated Filing system; BDL, GRSE, NIVABUPA, ENRIN file RPT separately (not embedded in XBRL).
Transaction types
| Transaction Type | What it covers |
|---|---|
| Sale of goods or services | Company selling products or services to a related party |
| Purchase of goods or services | Company buying from a related party (raw materials, IT services, etc.) |
| Loan | Loans given to or received from related parties |
| Investment | Equity investments, share subscriptions in related entities |
| Remuneration | Salary, commission, sitting fees paid to directors / KMPs |
| Inter-corporate deposit | Short-term deposits placed with or received from group companies |
| Interest received / paid | Interest on loans or deposits between related parties |
| Dividend paid / received | Dividends flowing between the company and related entities |
| Any other transaction | Guarantees, brand fees, reimbursements, and other items |
Relationship groups
The relationship field in each filing is free text - companies describe it in their own words ("Wholly owned subsidiary", "Son of Managing Director", "Entity under common control"). VIGIL classifies these into 12 standardized groups using a text-parsing algorithm. Approximate share of total transactions (as of 6 March 2026):
| Relationship Group | % | What it includes |
|---|---|---|
| Group Companies | 68% | Subsidiaries, associates, joint ventures, fellow subsidiaries, holding companies |
| KMP | 10% | Managing Director, CEO, CFO, Company Secretary, Whole-time Directors |
| Relatives | 6% | Relatives of directors or KMPs (spouse, children, siblings, parents) |
| Other Related Party | 6% | Other disclosed related parties not fitting another category |
| Promoter Group | 4% | Promoters and promoter-group entities (families, trusts, holding vehicles) |
| Common Control/Influence | 2% | Entities under common control or significant influence (not direct subsidiaries) |
| KMP/Dir Controlled | 2% | Entities where a director or KMP has significant influence or control |
| Employee Benefits | under 1% | Post-employment benefit plans (gratuity, PF, ESOP trusts) |
| Trust | under 1% | Family trusts, charitable trusts, and foundations linked to promoters |
| Govt/PSU | under 1% | Government entities, PSUs, or government-controlled bodies |
| Investor | under 1% | Significant investors, VC or PE funds with board representation |
| Uncaptured | 1% | Relationships that do not match any classification pattern (under review) |
The dominant group is Group Companies (68%) - expected, since conglomerates transact between subsidiaries and associates. KMP (10%) is largely director/executive remuneration. These are standard operational disclosures.
How to use this data
Not every RPT is a red flag - the vast majority are routine business transactions companies must disclose. What to look for when reviewing:
- Unusual transaction types - loans to promoter-controlled entities, large investments in related parties, or guarantees given.
- Amounts vs approved values - the actual amount significantly exceeding the audit committee's approved value.
- Transactions with KMP/Dir-controlled entities - where directors have a personal financial interest.
- Large outstanding balances - money owed by related parties that has not been settled.
- Comparison across periods - a sudden increase in RPT volume or new counter-parties appearing.
Data quality and validation
RPT data is extracted from official XBRL filings using a parser that reads the SEBI in-capmkt taxonomy. A full extraction validation in March 2026 across all 1,440 filings (728 companies, ~250,000 transactions) independently counted the RPT contexts defined in each XBRL file and compared them to the parser's extracted count: 100% match across all 1,440 filings, zero discrepancies. Additional checks confirmed all transactions have the required fields (counter-party, relationship, type, at least one amount) with no duplicate transaction numbers within a filing.
Open the live VIGIL Related Party Transactions view on TIGZIG, or see all VIGIL data sources.