Skip to content
Back to skills

Audit Related Party Transactions Jeffreytse

ASecurity

Use when a company is entering, or reviewing whether it has properly reviewed, a transaction involving a director, officer, significant shareholder, or their close associates — requiring independent-committee review and approval before the transaction proceeds, rather than allowing an interested party to approve or influence approval of a transaction that benefits them.

  • 85 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 8, 2026
ai-agentsgogitdocumentation

Security analysis

A100/100

Scanned October 8, 2026

npx -y skills add ThomasMoreAI/legal-skills-open --skill audit-related-party-transactions-jeffreytse --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Audit Related Party Transactions Jeffreytse?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Audit Related Party Transactions Jeffreytse
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-audit-related-party-transactions-jeffreytse/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-audit-related-party-transactions-jeffreytse)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: audit-related-party-transactions-jeffreytse
title: Audit Related-Party Transactions
description: Use when a company is entering, or reviewing whether it has properly reviewed, a transaction involving a director, officer, significant shareholder, or their close associates — requiring independent-committee review and approval before the transaction proceeds, rather than allowing an interested party to approve or influence approval of a transaction that benefits them.
author: jeffreytse
author_url: https://github.com/jeffreytse/grimoire-core/tree/main/skills/law/corporate/skills/audit-related-party-transactions
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: us
practice: corporate
language: en
tags: [law, related-party-transactions, conflict-of-interest, corporate-governance, board-oversight]
---

# Audit Related-Party Transactions

Require independent-committee review and approval of any transaction involving a director, officer, significant shareholder, or their close associates before the transaction proceeds — rather than allowing an interested party to approve, or influence the approval of, a transaction that benefits them.

## Why This Is Best Practice

**Adopted by:** The NYSE Listed Company Manual (Section 314.00) requires listed companies to conduct appropriate review and oversight of related-party transactions, SEC Regulation S-K Item 404 mandates disclosure of related-party transactions above a specified threshold, and independent audit or nominating/governance committee review of these transactions is standard corporate governance practice across NYSE- and Nasdaq-listed companies.
**Impact:** Undisclosed or improperly approved related-party transactions have been a recurring element in major corporate governance failures (Enron's related-party special purpose entities among the most cited examples), where transactions benefiting insiders were approved without genuine independent scrutiny — the specific structural failure that mandatory independent review is designed to prevent.
**Why best:** A transaction reviewed and approved by the same person who benefits from it, or by directors with personal loyalty to that person, provides no genuine check against a deal favoring the insider over the company and its other shareholders — independent-committee review, with the interested party recused from the approval decision, is what actually separates legitimate related-party dealing from self-dealing.

Sources: NYSE Listed Company Manual, Section 314.00 (Related Party Transactions); SEC Regulation S-K, Item 404 (Transactions with Related Persons); Sarbanes-Oxley Act corporate governance provisions

## Steps

### Step 1: Define what qualifies as a related party and a reportable transaction

Establish clear definitions of who qualifies as a related party (directors, executive officers, significant shareholders above a defined ownership threshold, and their immediate family members) and what transaction size or type triggers the review requirement, using SEC Regulation S-K Item 404's disclosure threshold as a reference point if no more conservative internal threshold is set.

### Step 2: Require disclosure of the proposed transaction before it proceeds

Require any director, officer, or significant shareholder proposing or benefiting from a related-party transaction to disclose it to the designated review committee before the transaction is finalized — after-the-fact disclosure defeats the purpose of independent review, since it can't prevent an unfavorable transaction from proceeding.

### Step 3: Recuse the interested party from the approval decision

Recuse the interested director or officer from the committee's discussion and vote on the transaction, ensuring the approval decision is made entirely by directors with no personal stake in the outcome.

### Step 4: Evaluate the transaction against arm's-length terms

Evaluate the proposed transaction against what arm's-length, unrelated-party terms would look like — comparable market pricing, standard commercial terms — rather than accepting the interested party's proposed terms without independent benchmarking.

### Step 5: Document the review and disclose per applicable requirements

Document the committee's review, the terms considered, and the basis for approval or rejection, and disclose the transaction in proxy statements or other filings as required by SEC Regulation S-K Item 404 and applicable listing standards.

## Rules

- Require disclosure of a proposed related-party transaction before it's finalized, not after the fact.
- Always recuse the interested party from the committee's discussion and approval vote.
- Benchmark the proposed transaction against arm's-length terms rather than accepting the interested party's proposed terms without independent evaluation.
- Document the review and disclose per applicable SEC and listing-standard requirements.

## Examples

**Independent review catching an unfavorable term:** A company's audit committee reviews a proposed real estate lease between the company and an entity controlled by a board member's spouse. Benchmarking against comparable market lease terms reveals the proposed rent is above market rate — the committee requires renegotiation to market terms before approving, a check the interested director's own approval would not have provided.

**Proper recusal and documentation:** A significant shareholder proposes a consulting arrangement with the company. The shareholder discloses the proposal, recuses from the committee's discussion and vote, and the committee documents its review of the proposed terms against comparable consulting arrangements before approving — creating a clear, defensible record.

## Common Mistakes

- **Allowing the interested party to participate in or influence the approval decision** — this defeats the entire purpose of independent review; recusal must be complete.
- **Reviewing the transaction only after it has already been finalized or executed** — disclosure and review must occur before the transaction proceeds to actually prevent an unfavorable deal.
- **Accepting the interested party's proposed terms without independent arm's-length benchmarking** — the review's value depends on genuinely evaluating whether the terms are fair, not rubber-stamping proposed terms.
- **Failing to document the review or disclose per applicable requirements** — an undocumented or undisclosed review doesn't satisfy SEC and listing-standard obligations and isn't defensible if later challenged.

## When NOT to Use

- For a transaction below the company's defined materiality threshold for related-party review — apply proportionate scrutiny rather than requiring full committee review for genuinely immaterial transactions.
- For a private company with no applicable exchange listing standards — related-party transaction review is still good governance practice, but the specific NYSE/Nasdaq/SEC triggers won't apply in the same way.
- As a substitute for the company's general conflict-of-interest policy — related-party transaction review addresses a specific category of transaction; broader conflict-of-interest disclosure and management is a distinct, complementary practice (see `design-conflict-of-interest-policy`).

> **Legal disclaimer:** This skill encodes professional best practices for educational purposes. It is not legal advice. Related-party transaction review carries specific securities-law disclosure obligations that vary by company size, exchange listing, and jurisdiction — consult licensed securities counsel before finalizing a related-party transaction review process.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.