Back to Insights
Governance Advisory25 June 2026

Related-Party Transaction Escalation Note in India

A practical governance note on when related-party transactions should move from business approval to board or committee escalation.

Business professionals signing documents for a related-party transaction review

Related-party transactions are not automatically improper. Many are commercially sensible and operationally necessary. The governance risk begins when the relationship is identified late, the pricing basis is thin, or the approval note reads as if it was drafted after everyone had already agreed. A related-party escalation note helps the board or audit committee see the relationship, the transaction, the commercial reason, and the safeguards before approval hardens.

The note should begin with the counterparty relationship. Is there common control, a promoter link, a director interest, a group entity, or a key managerial personnel connection? The next part should explain the transaction: value, tenure, goods or services, pricing method, alternatives considered, and whether the arrangement is ordinary course and arm's length. The note should not hide difficulty under labels. Labels are useful; evidence is better.

Business professionals reviewing transaction records in a meeting

The official Supreme Court judgment titled Vishal Tiwari v Union of India and Others dealt with securities-market allegations that included related-party disclosure concerns. Used only by analogy, it reinforces a governance lesson: oversight improves when expert review, transparency, and follow-through are taken seriously. A board note should therefore show the actual review undertaken, not simply declare that the transaction is acceptable.

Escalation is sensible where value is material, pricing is unusual, the relationship is sensitive, approval is urgent, or earlier transactions with the same party show a pattern. Directors with a conflict should disclose it and abstain where required. The minutes should record the disclosure, papers reviewed, decision, and conditions. A board should never need archaeology tools to discover why an interested transaction was approved.

For implementation, management should keep a compact control pack: the issue note, source documents, responsible owner, review date, approval route, next action, and evidence needed for closure.

The pack should identify what changed since the previous review and the threshold for escalation at the next meeting.

If the board or management decides not to escalate, the reason should be recorded in plain terms.

Where external advisers are involved, business instructions should be separated from privileged legal review.

The result should be short enough to read before a meeting and complete enough to explain the decision months later.

Governance fails quietly when action items become folklore.

A sensible pack also records dissent, abstention, unresolved information requests, and the date by which management will return with a closure note.

If the matter is repeated, the second note should not start from zero; it should show the history, earlier conditions, and whether those conditions were met.

This is where disciplined drafting protects both commercial speed and legal memory.

The board does not need a thesis.

It needs a fair record of the decision, the evidence available at the time, and the reason the chosen route was proportionate.

The note should also be tested for audience.

Finance may need numbers, legal may need authority, operations may need deadlines, and directors may need a clear risk choice.

A single page can serve all four if it is drafted with headings, owners, and exhibits rather than narrative clutter.

That discipline makes later review faster and avoids the familiar scramble for missing context later.

AGS Consulting assists companies with related-party transaction review notes, conflict registers, and board-ready escalation records. For support on a proposed transaction or approval process, contact AGS Consulting through the contact section.

FAQs

Does every related-party transaction need board escalation?

No. Escalation depends on statute, listing status, policy thresholds, materiality, conflict sensitivity, and whether audit committee approval is required.

What evidence supports arm's-length review?

Comparable pricing, procurement records, valuation notes, market quotes, or management justification can support the review, depending on the transaction.

Should conflicted directors participate?

Conflicted persons should disclose the interest and follow the statutory, policy, and board-process requirements on participation and abstention.

What should minutes record?

They should record the relationship, materials reviewed, disclosures, abstentions where applicable, decision, conditions, and follow-up owner.