Target keyword: related party transaction policy
Intent: Informational / Template
Last updated: 2026-09-14
Why related-party rules sit next to loyalty
A related-party transaction (RPT) is any deal between the organization and a person or entity that can influence — or appear to influence — a director’s, officer’s, or key person’s judgment. RPTs are where the duty of loyalty becomes concrete: disclosure, independent review, fairness, and documentation.
Public companies face SEC Regulation S-K Item 404 disclosure, stock-exchange approval rules, and audit-committee scrutiny. Private companies face investor agreements, lender covenants, and Delaware entire-fairness risk when conflicts are not cleansed. Nonprofits face Form 990 Schedule L reporting, intermediate sanctions (excess benefit), and state AG attention.
This guide gives boards a workable policy: definitions, thresholds, independent review paths, disclosure, minutes language, and operating rhythm — to be tailored by counsel for your jurisdiction and entity type.
Definitions that prevent argument later
Related party (illustrative): directors; executive officers; beneficial owners above a threshold (often 5% for public-company analogs); immediate family; entities controlled by any of the above; significant donors or members where nonprofit law so provides.
Related-party transaction: sale, lease, loan, guarantee, employment/consulting, equity issuance, grant, joint venture, settlement, or other transfer of value — direct or indirect — involving a related party.
Materiality / threshold: dollar amounts or qualitative significance that trigger enhanced process. Below-threshold items may still require disclosure if they create appearance issues.
Interested person: anyone with a conflicting interest in the specific transaction.
Disinterested / independent review body: independent directors, audit committee, or special committee without the conflict.
Appearance matters. Policies should capture actual, potential, and apparent relatedness.
Policy goals (state them explicitly)
- Protect organizational assets and mission.
- Preserve director liability protections through good process (business judgment / safe harbors where available).
- Meet disclosure and regulatory expectations.
- Enable beneficial RPTs that are genuinely fair (e.g., below-market office lease from a founder) without normalizing self-dealing.
- Create a searchable approval record.
Thresholds: design a ladder, not a cliff
Example corporate ladder (customize)
| Aggregate annual value | Process |
|---|---|
| Under $10,000 (or de minimis hospitality) | Disclose on annual questionnaire; management log |
| $10,000–$100,000 | Written disclosure; CEO + GC review; report to Audit/Governance |
| Over $100,000 or qualitative material | Independent committee approval before binding |
| Any loan to directors/executives | Generally prohibited or board-level approval with counsel (public cos: SOX loan ban for issuers) |
| Equity / unique assets / IP | Always independent review regardless of dollars |
Nonprofit ladder notes
- Excess benefit / intermediate sanctions analysis for disqualified persons
- Comparability data for compensation-like RPTs
- Schedule L reporting thresholds on Form 990
- State nonprofit corporation act safe harbors for conflicted transactions
Thresholds should be revisited when inflation, company scale, or regulator expectations change. Publish them in the policy appendix so managers know when to stop and escalate.
Independent review: the heart of the process
Who reviews
- Audit committee for financial RPTs and auditor independence adjacency
- Governance / nominating for board-composition-related conflicts
- Compensation committee for pay and perqs
- Special committee when a majority of the board is interested or in M&A freeze-outs
Independence must be real: no material relationships with the counterparty; no sharing in the economics of the deal.
What reviewers evaluate
- Nature of the relationship and conflict
- Business purpose for the organization
- Terms vs. market alternatives (quotes, comps, fairness opinion if warranted)
- Whether a non-related alternative is reasonably available
- Impact on controls, reputation, and stakeholder optics
- Ongoing monitoring (renewals, amendments, volume caps)
Approval standards
Approve only if the transaction is fair, reasonable, and in the best interests of the organization (nonprofit phrasing often tracks state statutes; corporate phrasing may track DGCL safe harbors or common-law fairness). Document the finding expressly.
Disclosure duties
Annual
Related-party questionnaire overlapping the COI questionnaire — or a combined instrument. Capture entities, family employment, vendor ties, loans, and anticipated transactions.
Transaction-specific
Before negotiation advances past preliminary discussion, the interested person discloses in writing to the Corporate Secretary / GC / committee chair. Late disclosure is a policy violation even if the deal is fair.
Ongoing
Material amendments, renewals, and volume increases re-trigger review.
Public / regulatory
Coordinate with securities counsel (Item 404), nonprofit Form 990 preparers, and lender reporting. Internal approval ≠ external disclosure completeness.
Recusal and meeting mechanics
Script:
- Interested director discloses.
- Leaves the room for deliberation (may answer factual questions first).
- Does not vote; confirm quorum without counting the interested director if required by statute/bylaws.
- Minutes record disclosure, absence, discussion summary at an appropriate level, alternatives considered, and approval/denial with fairness finding.
- Interested director returns only after the item is closed.
Hallway lobbying after recusal undermines the record. Chairs should say so.
Loans, guarantees, and “soft” RPTs
High-risk categories:
- Loans or guarantees to directors/officers
- Related-party leasing of facilities or IP
- Purchasing from director-owned vendors without bids
- Preferential equity terms for insiders
- Nonprofit grants to director-affiliated charities
- Hiring immediate family into senior roles
Some are banned for certain issuers; others demand heightened process. When in doubt, independent review plus market evidence.
Documentation and retention
Retain for the same horizon as board minutes (often permanent for corporate minute books; multi-year for nonprofits):
- Disclosure forms
- Committee packages and comps
- Approvals and denials
- Related contracts
- Monitoring reports
Apply legal holds in disputes. Restrict access — RPT files contain sensitive personal financial data.
Intersection with COI policy
COI policy = disclosure + recusal culture.
RPT policy = transactional approval engine for deals with related parties.
They should cross-reference, share definitions, and avoid contradictory thresholds. Many organizations maintain one combined Loyalty Policy with COI and RPT chapters.
Startup / venture-backed specifics
Common RPTs: founder secondary sales, related-party SaaS tools, family contractors, investor affiliate commercial deals, inside-led bridge notes.
Investor consents in stockholders’ agreements often layer on top of board policy. Map both. Independent directors should expect to own approval of founder-related commercial arrangements.
Nonprofit Schedule L readiness
Maintain a running log of transactions that may appear on Schedule L. Finance and Governance should reconcile before Form 990 drafting — not during filing week. Board review of the 990 is easier when RPT files are complete.
Monitoring after approval
Approval is not forever:
- Annual affirmation that terms remain in force
- Volume caps and invoice sampling
- Re-bid at renewal
- Immediate reopening if conflict deepens
Audit internal audit’s RPT testing into the audit plan where scale warrants.
Red flags for chairs and secretaries
- “We’ve always used my brother’s firm.”
- Verbal side deals not in the board package
- Related vendor sole-sourced in a rush before quarter-end
- Interested director drafting the fairness memo
- Threshold gaming (splitting invoices)
- Undisclosed special-purpose entities
Sample policy section headers
- Purpose and loyalty framing
- Definitions
- Covered persons
- Pre-clearance and disclosure
- Thresholds and approval authority matrix
- Independent review standards
- Recusal
- Loans and prohibited transactions
- Reporting to the full board
- Regulatory disclosure coordination
- Recordkeeping
- Violations
- Annual review
Metrics for governance / audit committees
- Number of RPTs approved / denied / pending
- Aggregate dollars with related parties
- Questionnaire completion rate
- Late disclosures
- Audit findings related to vendor master / related parties
Fairness evidence: how much is enough?
Not every RPT needs a banker’s fairness opinion. Calibrate evidence to risk:
| Situation | Typical evidence |
|---|---|
| Routine vendor under threshold | Two comparable quotes; COI disclosure |
| Material services contract | Competitive RFP or 3 comps; independent committee memo |
| Real estate / unique asset | Independent appraisal |
| Control / freeze-out / controller deal | Special committee + counsel + financial advisor (see special committees guide) |
| Nonprofit compensation-like benefit | Comparability data; rebuttable presumption process where applicable |
The record should show the committee considered alternatives, not that it rubber-stamped a management narrative. If the only memo was drafted by the interested party’s counsel, restart.
Controller and private-equity contexts
When a controlling stockholder or sponsor sits on both sides:
- Ordinary RPT policy may be insufficient
- Consider dual protections (independent committee + majority-of-minority) where counsel advises for cleansing
- Separately track portfolio-company commercial deals with affiliate funds
- Observers from co-investors may need information barriers on sensitive RPT deliberations
PE operating partners who also sell services to portcos create recurring RPT patterns — standardize the approval memo format across the fund’s portfolio for diligence efficiency.
Vendor master and accounts-payable controls
Governance policy fails if AP cannot detect relatedness:
- Flag related-party vendors in the ERP
- Dual approval for invoices above threshold
- Periodic match of director questionnaires to vendor master
- Prohibit new vendor setup without COI check for board-related names
Internal Audit should test this annually for mid-market and larger organizations.
Sample approval motion language
“RESOLVED, that the Audit Committee, having reviewed the disclosure of [Director X]’s interest in [Counterparty], the materials comparing terms to market alternatives, and management’s business rationale, hereby determines that the proposed [transaction] is fair, reasonable, and in the best interests of the Corporation, and approves the transaction substantially on the terms presented, with [Director X] recused from deliberation and vote.”
Keep the packet index number in the minutes for the archive.
90-day implementation plan
Days 1–30: Inventory known RPTs; draft threshold ladder with Finance; align definitions with COI policy.
Days 31–60: Board approval; questionnaire update; train managers who own vendor selection; build committee checklist.
Days 61–90: Clear backlog of undocumented historical RPTs; set monitoring calendar; reconcile with Form 990/Item 404 workpapers.
Director quick card
Before you promote a vendor or structure a side deal: disclose early. Bring comps. Leave the room. Expect the independent committee to say no sometimes — that is the system working. Never split invoices to dodge thresholds. When unsure, ask the GC before the term sheet circulates.
Worked example: director-affiliated SaaS vendor
A director owns 30% of a cybersecurity startup. Management wants a $180,000 annual contract. Process:
- Director discloses at first serious conversation; Corporate Secretary opens an RPT file.
- Management runs a mini-RFP with two alternatives; documents feature gaps.
- Audit committee meets; director answers technical questions then leaves.
- Committee finds the price within 8% of the best alternative and the product uniquely meets a control requirement; approves with annual re-bid and volume cap.
- Minutes recite fairness finding; ERP vendor master flagged; Form 990/Item 404 workpaper updated.
- One year later, committee re-opens on renewal with fresh comps.
That is what “good” looks like — not a hallway nod.
Product POV
Prepared Board’s view: related-party tags should sit beside the decision object — disclosure, recusal, and approval findings linked to the resolution — so loyalty process is visible under time pressure, not buried in a shared-drive folder named “Legal Misc.”
Internal links
- Conflict of Interest Policy for Boards
- Fiduciary Duties of Board Directors
- How Boards Make Decisions
- Special Committees in M&A
- Form 990 Board Governance Questions
- Board Committee Charters
Conclusion
Related-party policy is loyalty with a calculator and a minute book. Set thresholds, insist on independent review, disclose early, recuse cleanly, and keep records that explain why the deal was fair. Beneficial RPTs can survive sunlight; self-dealing cannot.
Sources
- SEC Regulation S-K Item 404 (related person transactions) — public company baseline
- DGCL conflict-transaction safe harbor themes and entire fairness case law (secondary summary; counsel for application)
- IRS Form 990 Schedule L and intermediate sanctions concepts
- Stock exchange related-person transaction approval rules (NYSE/Nasdaq themes)
- NACD guidance themes on conflict oversight