SOP: Audit Procedures for Related Party Transactions (RPT)

Purpose and Scope

This Standard Operating Procedure (SOP) outlines the audit framework for identifying, verifying, and disclosing Related Party Transactions (RPTs) in accordance with international accounting standards (e.g., IAS 24). The objective is to ensure that all transactions between the entity and its related parties are identified, substantiated, approved at the appropriate governance level, and accurately disclosed to prevent conflicts of interest and financial misrepresentation.

---

Phase 1: Identification and Planning

• Update the Related Party Register: Obtain the master list of all key management personnel (KMP), subsidiaries, associates, joint ventures, and entities with significant influence or common control.
• Review Governance Minutes: Review minutes of Board of Directors and Audit Committee meetings to identify any disclosed interests or potential conflicts discussed during the period.
• Cross-Reference Ownership Data: Verify current shareholding structures and changes in legal entities to ensure new relationships are captured in the master registry.
• Inquiry of Management: Conduct formal interviews with legal counsel and senior management regarding any undisclosed side agreements or informal arrangements.

Phase 2: Transaction Testing and Substantiation

• Completeness Verification: Perform a "look-back" test by checking high-value payments or large vendor invoices against the Related Party Register to ensure all RPTs were flagged.
• Arm’s Length Analysis: For every material transaction, obtain evidence that the terms are equivalent to those that would prevail in an arm’s length transaction (e.g., benchmark against market price quotes or independent valuations).
• Approval Compliance: Verify that each transaction was authorized by the required governance body (e.g., Board of Directors or Audit Committee) as per the company’s Delegation of Authority (DoA) matrix.
• Contractual Documentation: Inspect signed contracts, Master Service Agreements (MSAs), or Purchase Orders to confirm that the business purpose of the transaction is clearly defined and commercially rational.

Phase 3: Financial Statement Presentation

• Disclosure Review: Confirm that the nature of the relationship, the volume of transactions, and outstanding balances are disclosed in the notes to the financial statements.
• Consistency Check: Ensure that the amounts disclosed in the audit working papers reconcile exactly to the general ledger and the notes provided in the financial statements.
• Assessment of Risk: Evaluate whether the volume or nature of the transactions indicates "round-tripping," unauthorized lending, or improper revenue recognition.

---

Pro Tips & Pitfalls

• Pro Tip (The 'Look-Outside' Technique): Do not rely solely on internal registries. Perform a web search on vendor/customer addresses and phone numbers. Often, "unrelated" vendors share the same office address or registered agent as the company’s executives.
• Pro Tip (Focus on Small Amounts): Fraudsters often hide significant irregularities in a series of small, frequent, "immaterial" transactions. Use data analytics to spot patterns in aggregate spend rather than just individual transactions.
• Pitfall (Assuming Disclosure): Management often forgets to disclose family members of KMP who hold positions in supplier firms. Ensure the audit process covers "indirect" related parties.
• Pitfall (Missing Non-Monetary Transactions): Auditors frequently focus on cash payments and miss barter agreements, guarantees, or the provision of free services, which are still considered RPTs.

---

Frequently Asked Questions (FAQ)

1. What is the biggest red flag for a related party transaction? Transactions that lack a clear commercial purpose or those that deviate from established market rates are the primary indicators of potential self-dealing or manipulation.

2. Does an informal "handshake" agreement need to be audited? Yes. Even if an agreement is not formal, the economic impact is real. Auditors must document the existence of the relationship and the value transferred, regardless of the lack of formal paperwork.

3. What if a management member denies the existence of a relationship? If management denies a relationship that evidence suggests exists, this must be treated as a potential management integrity issue and elevated to the Audit Committee or external legal counsel immediately.

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is the primary goal of an RPT audit procedure?", "acceptedAnswer": { "@type": "Answer", "text": "The primary goal is to ensure all transactions between an entity and its related parties are identified, substantiated, properly approved, and accurately disclosed to prevent conflicts of interest." } }, { "@type": "Question", "name": "How do you verify 'Arm's Length' terms in RPTs?", "acceptedAnswer": { "@type": "Answer", "text": "Arm's length verification is achieved by benchmarking transaction terms against market price quotes, obtaining independent valuations, or comparing them to similar transactions with unrelated parties." } }, { "@type": "Question", "name": "What documents are required for RPT compliance testing?", "acceptedAnswer": { "@type": "Answer", "text": "Key documents include the Related Party Register, board meeting minutes, signed contracts, Master Service Agreements (MSAs), and the company's Delegation of Authority (DoA) matrix." } } ] } </script> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "RPT Audit Procedure Software", "applicationCategory": "FinanceApplication", "operatingSystem": "Web", "description": "A comprehensive audit framework and SOP tool for managing Related Party Transactions (RPT) in compliance with IAS 24 standards.", "softwareHelp": { "@type": "CreativeWork", "name": "RPT Audit SOP Documentation" } } </script>