A related‑party transaction (RPT) is any transfer of resources, services, or obligations between an entity and parties that have a preexisting relationship or common interest with the entity. Related parties include affiliates, parent/subsidiary entities, major shareholders, key management personnel (KMP), directors, and close family members or entities controlled by these persons. RPTs are legal, but because they create potential conflicts of interest, they require heightened scrutiny, governance and disclosure.
Key Takeaways
– RPTs are common and can be routine (e.g., intercompany loans) or high‑risk (e.g., off‑balance‑sheet arrangements).
– They are not inherently illegal, but they present conflicts of interest and fraud risk if not approved, documented and disclosed at arm’s length.
– Regulators and standard setters require disclosure (and in many cases board or independent committee approval) so investors can assess the effect on corporate performance and governance.
– Auditors face special challenges auditing RPTs because management controls identification and disclosure; auditors must perform additional procedures to detect undisclosed related parties or transactions.
Common Types of Related‑Party Transactions
– Intercompany sales and transfers (goods, inventory, IP, services) between parent, subsidiaries or affiliates.
– Loans, guarantees or credit arrangements among related entities or to officers/directors.
– Management, consulting or development fees paid to entities controlled by major shareholders or executives.
– Lease agreements between the company and a related party.
– Sales/purchases of property or fixed assets among related persons.
– Compensation, deferred compensation, or benefit arrangements with key management personnel or their family members.
– Special purpose entities and off‑balance‑sheet arrangements (historically used to move risk/obligations).
Regulatory and Accounting Framework
– U.S. Securities and Exchange Commission (SEC): Public companies must disclose related‑party transactions in their periodic reports (10‑K, 10‑Q) and proxy statements; Item 404 of Regulation S‑K governs information about related‑party transactions, director independence and certain relationships. (SEC)
– U.S. GAAP (FASB): Related‑party disclosure guidance is in ASC Topic 850, Related Party Disclosures (ASC 850). Historical standards such as SFAS No. 57 addressed related‑party disclosures as well. (FASB)
– International Financial Reporting Standards (IFRS): IAS 24, Related Party Disclosures, requires entities to disclose related‑party relationships, transactions and outstanding balances so readers can evaluate their effect on the financial statements. (IAS 24)
– Auditing standards: Auditors must identify and evaluate RPTs as part of assessing fraud and error risk (AICPA AU‑C Section 550, “Related Parties,” and equivalent PCAOB guidance).
– Tax authorities: Many tax codes (in the U.S., Internal Revenue Code Section 267 and other provisions) scrutinize RPTs and may disallow tax benefits arising from transactions that are not at arm’s length. (IRC §267)
– Corporate governance and law: Sarbanes‑Oxley Act (2002) and subsequent regulatory actions tightened board, audit committee and auditor obligations after high‑profile abuses.
Real‑World Example: The Enron Scandal
Enron used related parties (special purpose entities) to hide debt, inflate earnings and conceal losses. Those related‑party transactions misled auditors, the audit committee and investors, contributing to Enron’s collapse in 2001 and the conviction of several executives. The scandal prompted major regulatory and governance changes, including the Sarbanes‑Oxley Act of 2002 and stricter rules on disclosures, auditors and board responsibilities.
Are Related‑Party Transactions Audited?
Yes—but auditing them is challenging:
– Auditors must plan and perform procedures specifically targeted at identifying related parties and RPTs, including management inquiries, review of board and committee minutes, contract inspection and corroborative external confirmations.
– Auditing standards require auditors to evaluate whether transactions were authorized, whether terms are at arm’s length, whether amounts were properly measured and disclosed, and whether there is increased fraud risk.
– Detection depends largely on management’s truthful disclosure; undisclosed related parties or transactions can be difficult to detect because they may be disguised among ordinary transactions. (AICPA AU‑C 550; PCAOB guidance)
Which IFRS Regulation Covers Related Parties?
IAS 24, Related Party Disclosures, sets out the definition of related parties and the disclosure requirements for related‑party relationships, transactions and outstanding balances. Its objective is to ensure financial statement readers are made aware of the possibility that an entity’s position and results may have been affected by related parties.
Does the IRS Need to Know About Related‑Party Transactions?
Yes. The Internal Revenue Service (and tax authorities generally) scrutinize RPTs to ensure transactions are priced and reported at arm’s length and that tax benefits claimed are valid. Under U.S. Internal Revenue Code section 267 and other provisions, certain losses, deductions or tax attributes may be disallowed if transactions among related parties are not at arm’s length or are designed primarily to avoid tax. Documentation and transfer pricing support are critical.
Risks and Red Flags
– Transactions not approved by independent directors or an audit committee.
– Terms materially different from comparable third‑party agreements (e.g., below market price, unusual payment terms).
– Repeated back‑to‑back intercompany transactions that obscure cash flows.
– Significant balances with related parties in receivables, payables or loans.
– Rapid or unexplained changes in related‑party activity or new related‑party entities formed close to reporting dates.
– Lack of transparent disclosure in notes to the financial statements.
Practical Steps — For Boards and Management (Checklist)
1. Adopt a formal Related‑Party Transaction Policy
• Define related parties, types of transactions requiring review, approval thresholds and documentation requirements.
2. Maintain a Related‑Party Register
• Track all relationships, affiliations, beneficial owners, family ties and entities controlled by insiders. Update regularly.
3. Require Pre‑Approval by Independent Committee
• Use the audit committee or a designated independent committee for approvals above defined thresholds; disallow self‑approval by interested parties.
4. Obtain Independent Valuation or Competitive Bids
• For material transactions, obtain third‑party valuations or multiple bids to evidence arm’s‑length pricing.
5. Document Terms and Rationale
• Keep formal contracts, board minutes, conflict‑of‑interest disclosures and rationale demonstrating benefit to the company.
6. Strengthen Internal Controls and Segregation of Duties
• Ensure approvals, payments and reconciliations involve independent reviewers.
7. Disclose Fully in Financial Statements and SEC Filings
• Follow ASC 850 / IAS 24 and SEC Item 404 rules to disclose nature, amounts, terms and outstanding balances.
8. Periodic Internal Review and External Audit Coordination
• Conduct periodic audits of the related‑party register and ensure auditors have full access.
Practical Steps — For Auditors (Checklist)
1. Update Risk Assessment
• Consider RPTs as a fraud and material misstatement risk factor.
2. Inquire of Management and Governance
• Ask management and the audit committee about identification, approval and disclosure processes; review minutes and policies.
3. Perform Substantive Procedures
• Inspect contracts, confirm balances, perform analytical procedures and test transactions for arm’s‑length terms.
4. Seek External Corroboration
• Where possible, obtain third‑party confirmations or market evidence (e.g., price lists, valuations).
5. Evaluate Disclosures
• Ensure disclosures meet the requirements of applicable accounting standards and SEC rules.
6. Consider Implications for the Audit Opinion
• If RPTs are materially misstated or undisclosed and management is uncooperative, consider a modified opinion or reporting to those charged with governance.
Practical Steps — For Investors and Analysts (Checklist)
1. Read the 10‑K / 10‑Q and Proxy Statements Carefully
• Check Item 404 (Regulation S‑K) disclosures, notes to the financials and related‑party schedules.
2. Look for Patterns and Materiality
• Assess amounts, terms, frequency and whether related parties receive preferential treatment.
3. Check Governance and Approvals
• Determine whether independent directors/audit committee approved transactions and whether independent valuations were obtained.
4. Watch Cash Flows and Off‑Balance‑Sheet Items
• Related‑party movements can mask true cash flow and leverage positions.
5. Raise Questions and Demand Explanations
• If disclosures are sparse or transactions are significant, ask management or the board for clarification.
Tax and Compliance Practicalities
– Maintain contemporaneous transfer‑pricing documentation and arm’s‑length support for cross‑border related‑party transactions.
– For U.S. taxpayers, confirm that transactions comply with IRC §267 and other relevant provisions; consult tax counsel where disallowance or constructive ownership rules could apply.
– Preserve documentation for audits — contracts, invoices, valuations and approvals.
Essential Insights on Related‑Party Transactions
– Transparency is the core control: clear policies, independent approvals, market‑based terms and full disclosure reduce risks.
– RPTs can be necessary and beneficial (e.g., centralized services, group financing), but they must be handled to protect minority shareholders and financial statement users.
– Auditors and regulators rely heavily on management and governance to identify and disclose RPTs—so strong governance and an empowered independent audit committee are critical.
– High‑profile failures (such as Enron) show the potential consequences when RPTs are abused: financial collapse, criminal charges and long‑lasting regulatory change.
Further Reading and Sources
– Investopedia — Related‑Party Transaction (Jessica Olah)
– U.S. Securities and Exchange Commission — Exchange Act Reporting and Item 404 (Regulation S‑K) guidance
– Financial Accounting Standards Board — ASC 850, Related Party Disclosures (and historical SFAS No. 57 references)
– International Accounting Standards Board / IFRS Foundation — IAS 24 Related Party Disclosures
– Internal Revenue Service — Internal Revenue Code §267 (related‑party provisions)
– AICPA — AU‑C Section 550, Related Parties (auditing guidance)
– Deloitte — Guidance on Related‑Party Transactions and Disclosures
– U.S. Congress / Library of Congress — Sarbanes‑Oxley Act of 2002
Conclusion
Related‑party transactions are a normal part of doing business in groups and among people with overlapping interests. Their acceptability depends on transparency, governance and fair economic terms. Boards, management, auditors and regulators each have roles to play in identifying, approving, documenting and disclosing RPTs so investors and other stakeholders can understand their financial impact and associated risks.
Editor’s note: The following topics are reserved for upcoming updates and will be expanded with detailed examples and datasets.