Related Party Transactions for Around 750 Listed Indian Companies Are Now on VIGIL, With the March Half-Yearly Filings In.
Published: August 16, 2026
Related party transactions for around 750 listed Indian companies are now on VIGIL, updated to 12 August 2026 and including the March half-yearly filings. Query it on the app or download the full database.
A related party transaction is business a company does with someone connected to it, a subsidiary, a promoter, a director, or a relative of one, and needs to be disclosed every six months.
The data has about 3,60,000 + rows covering roughly 44,000 counter parties across three half-year periods. You can browse and filter it in the app, query it through the open API without a key, or take the whole table as one file in CSV, Parquet or SQLite.. which range from 9-14 MBs.
How much a company files depends almost entirely on how many legal entities its group runs. The median company files under 200 rows for the whole period, and nine companies file more than 5,000 each, so the same disclosure rule produces very different volumes.
Live tool (for humans) at: tigzig.com/vigil ➜ Signals ➜ Related Party
Hit the docs and validations sections for more details on the data and pre-publish checks carried out.
And the 'Data & API' section to download manually yourself .. or have your AI do it via API ... see below
- API Docs (for agents): api.tigzig.com/vigil/v1/openapi.json
- API Docs (for humans): tigzig.com/apis/vigil
This is part of the Tigzig Agent Data Surface at tigzig.com/apis, which also carries mutual fund NAVs going back to 2006, macro and credit indicators, and market data. All of it open, no auth, no key and no signup.
How much each company files
Across 744 companies and the full period, the median company files 195 rows. A quarter file under 91, and the bottom 5% file under 27.
At the other end, 81 companies file more than 1,000 and nine file more than 5,000 each: Samvardhana Motherson at 6,653, Adani Ports 6,643, HCL Technologies 6,475, Wipro 6,393, Mahindra & Mahindra 5,893, Bharti Airtel 5,874, Reliance 5,662, Kotak Mahindra Bank 5,237 and Adani Green 5,215.
662 of the 744 file more than 50 rows.
A company that runs treasury, shared services, manufacturing and distribution through separate legal entities has to disclose every internal transaction between them, so a high count reflects how the group is organised rather than how much business is being done. About 69% of all rows are transactions with group companies.
Some data nuances
Transaction type has a catch-all. About 56% of rows are filed as "any other transaction".
Counter party is a name, not an identifier. There are roughly 44,000 distinct strings and the same entity can appear spelled several ways, so match on normalised names rather than exact ones.
Period end date is stored as text like
31-MAR-2026, soMAX()on it sorts alphabetically and gives you the wrong answer. Parse it first.Negative amounts are deliberate. A negative outstanding balance means payable rather than receivable, and there are around 12,000 of them spread evenly across every transaction type.
Amounts are in rupees and reasonably consistent, the median transaction is about 62 lakh. Still sanity-check the extreme top before you sum anything.
I publish what the exchange filed, including the values that are wrong. Anything found is listed on the Known Issues page and flagged on the row itself in the app.
I run multi-level validation, but I am not going to say that they catch everything. Filing data is messy in ways nobody anticipates, and something will slip through, so I keep looking and tightening the validations. If you find something odd, tell me and I will add it.