Related Party Transactions: Compliance, Disclosure, and Audit Trail in Indian Companies

Related party transactions compliance in India requires companies to identify connected counterparties, secure timely board or shareholder authorizations, verify arm's length pricing, and maintain tamper-proof audit trails. Governed by the Companies Act 2013, SEBI LODR Regulations, and accounting standards, compliance protects minority shareholders and prevents statutory penalties through systematic contract scrutiny and continuous disclosures.

For chief financial officers, company secretaries, and corporate controllers, managing intercompany dealings has shifted from an annual compliance formality to an active operational discipline. Scrutiny from the Ministry of Corporate Affairs (MCA), the Securities and Exchange Board of India (SEBI), and the National Financial Reporting Authority (NFRA) has never been more intense. Regulators and statutory auditors no longer inspect only year-end balance sheet disclosures. They examine the contemporaneous economic rationale, competitive bidding records, and complete transaction lifecycles behind every intercompany movement.

When transactions between connected entities occur without documented commercial justification, companies face severe statutory consequences. Non-compliance can trigger personal penalties for directors under Section 188(5) of the Companies Act, contract voidability under Section 188(3), adverse auditor qualifications under CARO 2020 Clause 3(xiii), and market enforcement actions under SEBI LODR Regulation 23. Building an audit-proof operating model is therefore indispensable for growing enterprises, multi-entity conglomerates, and listed groups alike.

The Multi-Layered Architecture of Related Party Transactions Compliance

Related party transactions compliance does not sit within a single statute. Instead, Indian enterprises navigate four overlapping frameworks, each with distinct definitions, approval thresholds, and disclosure obligations.

1. The Companies Act, 2013

The Companies Act establishes corporate governance guardrails across private, unlisted public, and listed entities:

• Section 2(76) Definitions: Identifies related parties, including directors, key managerial personnel (KMPs), their relatives under Section 2(77), private companies where a director or manager is a director or member, public companies where a director or manager holds more than 2 percent of paid-up share capital alongside relatives, and holding, subsidiary, associate, or fellow subsidiary companies.
• Section 177 Audit Committee Approvals: Mandates prior Audit Committee approval for all related party transactions and subsequent modifications. Crucially, Section 177 contains no carve-out for transactions in the ordinary course of business or conducted at arm's length. Every transaction with a related party must pass through the committee.
• Section 188(1) Board and Shareholder Approvals: Regulates seven specific transaction categories: sale, purchase, or supply of goods; selling or buying property; leasing property; availing or rendering services; appointing agents; appointment to an office or place of profit; and underwriting securities subscriptions.
• The Arm's Length Exemption: Under the fourth proviso to Section 188(1), transactions entered into in the ordinary course of business and on an arm's length basis are exempt from Board and shareholder approvals under Section 188. However, establishing both conditions requires verifiable proof, and the transaction remains subject to Audit Committee approval under Section 177.
• Section 184 and Section 189 Governance: Directors must disclose their business interests annually and upon any change using Form MBP-1. Companies must record all arrangements in the statutory Register of Contracts in Form MBP-4 within 30 days of contract finalization.

2. SEBI LODR Regulations, 2015

For listed companies, SEBI enforces Regulation 23 of the Listing Obligations and Disclosure Requirements. The capital market framework imposes far tighter requirements than company law:

• Expanded Definition: Under Regulation 2(1)(zb), any entity belonging to the promoter or promoter group, or holding 10 percent or more of equity shares (directly or beneficially), is classified as a related party.
• Cross-Entity Scope: Under Regulation 2(1)(zc), transactions between a listed company or any of its subsidiaries and a related party of the listed entity or its subsidiaries fall under the regime, regardless of whether a price is charged.
• Independent Director Approval: Within the Audit Committee, only independent directors are entitled to vote on related party transaction resolutions.
• Turnover-Linked Materiality Framework: Material related party transactions require prior approval by ordinary resolution of shareholders. Under Schedule XIII of the LODR Regulations, materiality is determined by a graded, turnover-linked scale based on annual consolidated turnover: up to INR 20,000 crore turnover carries a 10 percent threshold; turnover between INR 20,001 crore and INR 40,000 crore carries a threshold of INR 2,000 crore plus 5 percent of the excess over INR 20,000 crore; and turnover above INR 40,000 crore carries a threshold of INR 3,000 crore plus 2.5 percent of the excess, capped at an absolute ceiling of INR 5,000 crore. Royalty or brand payments exceeding 5 percent of consolidated turnover remain material.
• Voting Restrictions: No related party can vote to approve a material related party transaction, regardless of whether that entity is party to the specific arrangement.
• Regulation 23(9) Disclosures: Listed companies must file standardized XBRL disclosures of all related party transactions with stock exchanges every six months within 15 days of publishing standalone and consolidated financial results.

3. Accounting Standards: Ind AS 24 and AS 18

The Institute of Chartered Accountants of India (ICAI) governs financial statement reporting. Ind AS 24 prioritizes economic substance over legal form, defining related party relationships through control, joint control, or significant influence. Companies must disclose transaction volumes, outstanding ledger balances, commitments, bad debt provisions, and key management personnel compensation divided across short-term, post-employment, and share-based benefits.

4. Direct Tax and Transfer Pricing Regulations

The Income Tax Department evaluates intercompany dealings under Section 40A(2)(b) of the Income Tax Act, 1961, disallowing domestic payments deemed excessive relative to fair market value. For cross-border transactions and Specified Domestic Transactions (SDTs) exceeding INR 20 crore under Section 92BA, enterprises must maintain contemporaneous transfer pricing documentation and submit Form 3CEB certified by a chartered accountant.

The following flowchart illustrates the statutory evaluation and authorization path for transactions under the Companies Act and listing regulations.

flowchart TD
    A["Identify Counterparty"] --> B{"Is Counterparty a Related Party?"}
    B -- "No" --> C["Standard Commercial Process"]
    B -- "Yes" --> D["Assess Scope under Relevant Law"]
    D --> E{"Audit Committee Applicable?"}
    E -- "Yes" --> F["Audit Committee Review"]
    F --> G{"Eligible for Omnibus Approval?"}
    G -- "Yes" --> H["Apply Omnibus Approval Framework"]
    G -- "No" --> I["Specific Prior Committee Approval"]
    E -- "No" --> J{"Ordinary Course and Arm's Length?"}
    H --> J
    I --> J
    J -- "Yes" --> K["Execute Transaction and Record Log"]
    J -- "No" --> L["Board Approval under Section 188"]
    L --> M{"Exceeds Shareholder Thresholds?"}
    M -- "Yes" --> N["Obtain Shareholder Approval"]
    M -- "No" --> K
    N --> K
    K --> O["Statutory Disclosures and Reporting"]

Statutory Approval Matrix: Companies Act vs SEBI LODR vs Income Tax

Navigating related party transactions compliance requires establishing exact authorization matrices before binding purchase orders or sales contracts are executed. Because legal thresholds and voting rights differ significantly across statutes, companies must evaluate transactions against all three frameworks concurrently.

The Audit Trail Mandate and Auditor Scrutiny Under CARO 2020

Statutory reporting in India has evolved past historical sampling. Under Rule 3(1) of the Companies (Accounts) Rules, 2014, every company utilizing accounting software must retain an audit trail feature that records an edit log for every transaction change, preserves timestamps, and prevents log modification throughout the financial year. Statutory auditors must report on software audit trail controls under Section 143(3)(j) of the Companies Act.

For related party transactions, audit trail integrity represents the primary defense during financial audits. Statutory auditors verify compliance under Clause 3(xiii) of the Companies (Auditor's Report) Order, 2020 (CARO 2020). Auditors must explicitly state:

• Whether all transactions with related parties comply with Section 177 (Audit Committee approval) and Section 188 (Board and shareholder approval) of the Companies Act, 2013.
• Whether details have been accurately disclosed in the financial statements as required by applicable accounting standards (AS 18 or Ind AS 24).

When conducting CARO 2020 reviews, audit teams compare general ledger entries directly against board approvals, omnibus limits, and the statutory register in Form MBP-4. They examine whether journal entries reflect retrospective rate adjustments or unapproved credit notes issued to sister concerns. Connecting operational assets to physical ledgers is equally critical. Our fixed asset and inventory audit services assist enterprises in reconciling physical plant, equipment, and inventories with corporate records, ensuring comprehensive CARO 2020 readiness.

The following diagram outlines the complete audit trail architecture required to track related party activity from initial disclosure to statutory filings.

flowchart LR
    A["Director Disclosures MBP-1"] --> B["Centralized Related Party Master"]
    B --> C["ERP Master Tagging of Counterparties"]
    C --> D["Pre-Transaction Gatekeeping Controls"]
    D --> E["Pricing Study and Arm's Length Check"]
    E --> F["Audit Committee and Board Approvals"]
    F --> G["Transaction Execution with Edit Logs"]
    G --> H["Statutory Disclosures and CARO Reporting"]

Operational Challenges in Related Party Data Governance

While the regulatory expectations are transparent, enterprise execution often breaks down in daily finance operations. Finance leaders frequently encounter four structural hurdles:

Siloed Master Data Systems

In mid-market and large organizations, company secretarial teams maintain director interest filings in physical forms or standalone governance portals. Concurrently, procurement and sales teams manage thousands of counterparties in separate enterprise resource planning (ERP) systems. Without automated data synchronization, a newly incorporated supplier owned by a director's relative can be onboarded in procurement without triggering related party flags in finance.

Cross-Subsidiary Visibility Gaps

Under SEBI LODR amendments, listed parent companies must track transactions where their unlisted subsidiaries transact with related parties, even when the parent company is not a counterparty. Gathering timely transaction data across decentralized subsidiaries running disparate accounting software creates major reporting delays and reconciliation errors.

Substantiating Arm's Length Pricing

The fourth proviso to Section 188(1) requires transactions to be both in the ordinary course of business and on an arm's length basis to bypass shareholder voting. Proving arm's length terms demands contemporaneous market quotes, commercial bids, or transfer pricing economic studies. When companies rely on subjective assertions rather than documented market testing, statutory auditors and tax authorities routinely reject the exemption.

Uncontrolled Spending Against Omnibus Caps

Audit Committees grant omnibus approvals with explicit annual financial ceilings. Without automated procurement controls, cumulative invoices can exceed approved limits mid-year. Managing high-volume transactions in accounts payable requires automated tracking to halt processing before statutory thresholds are breached. Linking procurement workflows with disciplined vendor compliance guarantees that supplier contracts remain synchronized with approved governance parameters.

Step-by-Step Implementation Framework for Related Party Transactions Compliance

Establishing an audit-ready compliance framework requires a systematic, six-step operating procedure spanning legal, procurement, and accounting departments.

Step 1: Upstream Identification and Centralized Master Creation

Begin each financial year by collecting Form MBP-1 declarations from all directors and KMPs. Extract full lists of directorships, partnerships, shareholding interests, and identified relatives under Section 2(77). Consolidate these records into a single Related Party Master maintained jointly by corporate secretarial and accounting teams. Require quarterly affirmations from key leaders to capture interim directorship changes or corporate restructurings promptly.

Step 2: ERP Master Tagging and Pre-Transaction Gatekeeping

Translate the legal Related Party Master into ERP controls. Tag counterparties at the vendor and customer master level. Configure purchase order workflows in modern AP automation software to recognize related party flags instantly. When a requisition involves a tagged counterparty, the software must verify whether an active Audit Committee approval code exists and confirm that the purchase value remains within the remaining omnibus limit before generating a purchase order.

Step 3: Economic Justification and Pricing Benchmarking

Build a standardized commercial evaluation pack for every related party contract. Document at least two independent third-party market quotes, publish open tenders where feasible, or establish documented cost-plus pricing formulas supported by transfer pricing documentation. For real estate leases or capital asset transfers, obtain formal valuation reports from registered valuers under Section 247 of the Companies Act to create undeniable arm's length records.

Step 4: Formal Governance Approvals

Present structured requests to the Audit Committee prior to entering contracts. For recurring commercial arrangements, seek omnibus approval under Rule 6A of the Companies (Meetings of Board and its Powers) Rules, 2014, ensuring the resolution details counterparty names, transaction nature, tenure, pricing formulas, and maximum financial limits. If a proposed transaction falls outside the ordinary course of business or exceeds Rule 15 thresholds, schedule board meetings and draft explanatory statements for shareholder resolutions.

Step 5: Continuous Consumption Tracking and Dynamic Controls

Track cumulative transaction values against approved omnibus ceilings on a monthly basis. Establish automated alerts when aggregate billing reaches 80 percent of an approved limit, providing sufficient lead time to seek fresh committee authorization. Integrating these checks into standard record to report outsourcing workflows ensures intercompany balances, debit notes, and cross-charges reconcile smoothly each month.

Step 6: Multi-Registry Statutory Disclosures and Reconciliations

Close the compliance loop by executing mandatory statutory filings across all registries:

• Record all contracts in the statutory Register of Contracts in Form MBP-4 within 30 days of execution, presenting it for signatures at the next board meeting.
• Disclose contracts not at arm's length or material contracts in Form AOC-2 within the annual Board's Report under Section 134(3)(h).
• Submit semi-annual related party disclosures in XBRL format under Regulation 23(9) of SEBI LODR to stock exchanges.
• Publish comprehensive accounting disclosures under Ind AS 24 or AS 18 in audited financial statements, cross-verifying figures against Form 3CEB tax filings.

Core Internal Controls and Key Performance Indicators to Track

Corporate controllers and compliance heads should monitor specific operational indicators to evaluate internal control maturity:

• Prior Approval Coverage Rate: Target 100 percent. Every related party transaction must link to an active Audit Committee, Board, or shareholder approval reference ID before contract execution.
• Unflagged Related Party Detection Rate: Target zero. Measures the volume of related party transactions identified post-facto during internal or statutory audits rather than through upstream ERP controls.
• Omnibus Threshold Consumption Margin: Variance tracking to confirm that cumulative spend never exceeds 100 percent of approved omnibus limits without supplementary authorization.
• Edit Log Integrity Metric: Target zero audit trail exceptions. Continuous monitoring to verify that system audit logs remain active and free from unauthorized administrative alterations.

Embedding these metrics within unified compliance management services ensures corporate legal, tax, and secretarial deadlines remain harmonized across multi-entity corporate structures.

Five Critical Mistakes Companies Make in Related Party Compliance

Even well-resourced finance organizations encounter compliance failures through subtle procedural misunderstandings:

1. Confusing Section 188 Exemptions with Section 177 Mandates

Many finance professionals assume that because a transaction is in the ordinary course of business and conducted at arm's length, it is entirely exempt from governance approvals. While this dual condition exempts the transaction from Board and shareholder approvals under Section 188, it does not exempt it from prior Audit Committee approval under Section 177. Bypassing the Audit Committee violates corporate law.

2. Overlooking Multi-Tier Subsidiary Transactions

Under SEBI LODR Regulation 23, listed parent entities must review transactions where their subsidiaries transact with related parties, even if the parent entity is completely uninvolved. Failing to establish reporting mechanisms at the subsidiary level leaves listed parent boards vulnerable to regulatory enforcement actions.

3. Utilizing Generic or Open-Ended Omnibus Approvals

Rule 6A strictly prohibits open-ended omnibus authorizations. Approvals that fail to specify counterparty names, transaction nature, pricing formulas, or specific monetary caps are invalid under MCA scrutiny. Furthermore, omnibus approvals expire after one financial year and cannot be rolled forward automatically.

4. Delayed Entry in the Section 189 Statutory Register

Section 189 requires entering contracts in Form MBP-4 within 30 days. During CARO reviews, statutory auditors examine board minutes alongside register entry dates. Recording contracts months later or right before annual audits creates clear audit findings of procedural default.

5. Relying on Post-Facto Arm's Length Rationalizations

When questioned by tax authorities under Section 40A(2)(b) or statutory auditors under CARO 2020, companies often attempt to justify transaction prices using retrospective market estimates. Arm's length pricing must be supported by contemporaneous documentation gathered when the contract was signed.

Strengthening Corporate Governance with Integrated Finance and Compliance Operations

Managing related party transactions compliance across complex operating environments requires combining legal expertise with robust financial process execution. As corporate groups expand, manual spreadsheets and fragmented departmental checks are insufficient to guarantee compliance.

At MYND Integrated Solutions, we help enterprises establish audit-ready financial governance by unifying technology platforms and back-office management. Through our comprehensive finance and accounts outsourcing, AP automation, and statutory compliance frameworks, we integrate master data validation directly into day-to-day transaction processing. Our automated workflows eliminate unapproved spend, enforce omnibus approval ceilings, and maintain unbroken audit trails aligned with MCA and SEBI standards.

With over two decades of industry leadership, MYND manages more than 20 million transactions annually and over 20 billion dollars in financial throughput across our platforms. Our clients achieve an average 35 to 40 percent cost reduction, 80 percent touchless accounts payable processing, and 99 percent compliance achievement. By pairing robust ERP controls with expert operational delivery, we ensure your related party governance remains transparent, defensible, and audit-proof.

Building Resilience Through Continuous Related Party Governance

Sustaining effective related party transactions compliance requires institutional discipline across legal, finance, and operational teams. Related party governance cannot function as a periodic reporting checklist completed weeks before annual board meetings. It must operate as an embedded control mechanism integrated into vendor onboarding, purchase order authorization, and ledger accounting.

By unifying director disclosures, establishing rigid pre-transaction gatekeeping, preserving contemporaneous arm's length proof, and securing unbroken audit trails, corporate leaders can engage with regulators and auditors with complete assurance. Modernizing your related party operating model today protects board members, safeguards enterprise value, and reinforces stakeholder trust.

Frequently Asked Questions

Does an arm's length transaction in the ordinary course of business require Audit Committee approval?

Yes. Under Section 177(4)(iv) of the Companies Act 2013 and SEBI LODR Regulation 23, all related party transactions require prior Audit Committee approval. The ordinary course of business and arm's length exemption in the fourth proviso to Section 188(1) applies only to Board and shareholder approvals under Section 188, not to Audit Committee oversight.

What is the current materiality threshold for related party transactions under SEBI LODR?

Under SEBI LODR Regulation 23 and Schedule XIII, materiality is determined by a graded, turnover-linked scale based on annual consolidated turnover: up to INR 20,000 crore turnover carries a 10 percent threshold; turnover between INR 20,001 crore and INR 40,000 crore carries a threshold of INR 2,000 crore plus 5 percent of the excess over INR 20,000 crore; and turnover above INR 40,000 crore carries a threshold of INR 3,000 crore plus 2.5 percent of the excess, capped at an absolute ceiling of INR 5,000 crore. Payments concerning brand usage or royalty exceeding 5 percent of annual consolidated turnover remain material.

How does the MCA audit trail rule impact related party transaction records?

Under Rule 3(1) of the Companies (Accounts) Rules, 2014, accounting software must retain an unbroken, date-stamped edit log for every entry, ensuring modifications cannot be hidden or disabled. For related party dealings, this audit trail provides verifiable evidence of transaction timing, approvals, and post-facto adjustments, which statutory auditors review under Section 143(3)(j) and CARO 2020 Clause 3(xiii).

Can a related party vote on a shareholder resolution approving their own transaction?

Under Section 188 of the Companies Act 2013, an interested related party member cannot vote on an ordinary resolution approving their contract, unless 90 percent or more members are relatives of promoters or related parties. Under SEBI LODR Regulation 23(4), no entity falling within the definition of a related party can vote to approve a material related party transaction, regardless of whether it is a party to that specific contract.

What is the difference between Form MBP-1, Form MBP-4, and Form AOC-2?

Form MBP-1 is the initial notice of disclosure of interest submitted by directors under Section 184 at the start of each financial year or upon interest changes. Form MBP-4 is the statutory Register of Contracts in which directors are interested, maintained by the company under Section 189 within 30 days of contract entry. Form AOC-2 is the statutory disclosure included in the Board's Report under Section 134(3)(h), reporting details of contracts not at arm's length or material contracts entered into during the reporting year.