Who Is a Related Party under Ind AS 24?

The practical reporting issue

Finance teams frequently encounter this issue only during the close, when contracts have already been signed and data has been captured for operational rather than accounting purposes. For Who Is a Related Party under Ind AS 24?, the decisive work often happens before any number is calculated. The team must apply control, joint control, significant influence, key-management and close-family definitions symmetrically across persons and entities. Contract wording, operational practice and reporting-date evidence may point in different directions unless the accounting question is framed precisely. Ind AS 24 is designed to alert users that financial position and performance may have been affected by related-party relationships, transactions and outstanding balances. The analysis must connect the business fact, the applicable principle, the measurement method and the financial-statement message.

Drawing the right boundary

The correct answer begins with boundaries. Ind AS 24 applies to relationships involving control, joint control, significant influence, key management personnel, close family members and specified entities connected to those persons or the reporting entity. The standard is disclosure-focused: the entity identifies relationships first, then captures transactions, balances, commitments, terms and key-management compensation by required categories. In practice, who is a related party can be distorted when teams mix a rule from a connected standard, use a later event as hindsight, or let an operational system define the accounting unit. A short scope conclusion and a dated fact pattern prevent those errors and give reviewers a stable basis for challenging the estimate or classification.

From contract or data to accounting outcome

A practical sequence keeps the analysis ordered and prevents a late disclosure review from uncovering a recognition error:

1. Frame the question. obtain audit-committee and board confirmation of completeness before authorisation. Link it explicitly to who is a related party.
2. Build the evidence base. maintain a relationship universe using legal ownership, governance roles, close-family declarations and significant-influence assessments. Trace it to the reported outcome for who is a related party.
3. Apply the accounting test. map counterparties from procurement, sales, treasury, payroll and legal systems to that universe. Record its effect on recognition, measurement or disclosure for who is a related party.
4. Quantify and reconcile. capture transactions, outstanding balances, provisions, guarantees and commitments throughout the period. Give the conclusion on who is a related party a date and an accountable owner.

Worked application

Consider this fact pattern at a March year end: A director's spouse controls a supplier and the director also sits on the customer's board. The matter involves a carrying amount, transaction value or exposure of approximately ₹109 crore. Management initially focuses on the apparent commercial outcome. Ind AS analysis instead requires the team to maintain a relationship universe using legal ownership, governance roles, close-family declarations and significant-influence assessments and map counterparties from procurement, sales, treasury, payroll and legal systems to that universe. Only after those steps should it calculate the amount and post the entry. The resulting paper should demonstrate that the entity can apply control, joint control, significant influence, key-management and close-family definitions symmetrically across persons and entities.

For who is a related party, the most likely challenge is describing terms as arm's length without substantiation. Evidence such as director and key-management declarations refreshed at least annually converts management’s view into a supportable conclusion. The final paper should reconcile the opening balance, current-period movements and closing balance, and identify any judgement that a user needs to understand. Even when the numerical answer is unchanged, better classification or disclosure can materially improve the financial statements.

Common shortcuts and why they fail

The following failure modes commonly create audit adjustments or weak disclosures:

• Describing terms as arm's length without substantiation. The risk increases when different teams own the contract, model, journal and note disclosure. For who is a related party, the working paper should show why the entity’s facts do or do not create this risk.
• Assuming transactions at market price need not be disclosed. This usually happens when the ledger label is accepted without tracing the underlying terms and timing. For who is a related party, the working paper should show why the entity’s facts do or do not create this risk.

Presentation, disclosure and related standards

A defensible file would normally contain:

• A disclosure reconciliation to ledgers, board minutes and statutory registers, specifically cross-referenced to the conclusion on who is a related party and the affected financial-statement line items.
• Director and key-management declarations refreshed at least annually, specifically cross-referenced to the conclusion on who is a related party and the affected financial-statement line items.
• Group structure, shareholder and beneficial-ownership records, specifically cross-referenced to the conclusion on who is a related party and the affected financial-statement line items.

The presentation and disclosure review should be performed at the same time as the accounting analysis. Ind AS 24 often interacts with Ind AS 19, Ind AS 27 and Ind AS 28. The memorandum should allocate each issue to the correct standard, reconcile note amounts to the ledger and explain material judgement in entity-specific language. For who is a related party, the paper should show where each material assumption is used.

Closing insight

This is an area where a short technical memo, supported by reconciled data, can prevent a long audit debate. Who Is a Related Party is best handled as a governed decision rather than a year-end adjustment. The entity should know who owns the conclusion, which data refreshes it and what evidence would trigger reassessment. That approach improves both compliance and the usefulness of the reported information. It also prepares learners to evaluate more complex Ind AS 24 cases in which several principles interact.