Short Definition
International Financial Reporting Standards framework that establishes consistent global requirements for identifying and disclosing related-party transactions in financial statements.
Comprehensive Definition
The related-party framework under IFRS is centered on a single standard, IAS 24, which addresses a basic problem: financial statements are normally prepared on the assumption that transactions occur between independent parties at arm's length. When parties are connected through ownership, control, influence, or family ties, that assumption may fail. Users of the statements need enough information to understand how those relationships may have affected the entity's financial position and results.
What the Framework Encompasses
The framework has three broad components: identifying who counts as a related party, determining what must be disclosed, and applying those requirements consistently across reporting entities.
Who Is a Related Party
Related parties generally include persons and entities connected to the reporting entity through control, joint control, or significant influence. Common categories are:
- Parent companies and ultimate controlling parties
- Subsidiaries and fellow subsidiaries
- Associates and joint ventures
- Key management personnel of the entity or its parent
- Close family members of individuals who control, jointly control, or significantly influence the entity, or who are key management personnel
- Post-employment benefit plans for the benefit of employees
- Entities controlled or significantly influenced by any of the above individuals
What Must Be Disclosed
Disclosure typically covers the relationship itself, the nature of transactions, outstanding balances (including commitments and any guarantees), and the terms and conditions attached. Entities also disclose compensation of key management personnel, generally broken down by category such as short-term benefits and post-employment benefits. Where a parent–subsidiary relationship exists, the entity discloses the relationship even if no transactions occurred, because the existence of control is itself relevant information.
Why It Matters to Business Professionals
For HR, compliance, and operations teams, related-party reporting is rarely just an accounting exercise. The information needed originates outside the finance department. HR holds data on executive compensation and family relationships. Procurement and contracts staff know which suppliers or customers have connections to directors. Legal and compliance teams track board interests and conflicts. If those groups do not feed accurate information into the process, the financial statements can be incomplete or misleading, and the organization may face audit findings, governance concerns, or loss of stakeholder confidence.
How It Applies in Practice
Consider a manufacturer that leases its warehouse from a company owned by a close relative of its chief executive. Even if the rent matches market rates, the arrangement is a related-party transaction requiring disclosure of the relationship, the amounts paid, any balances outstanding, and the lease terms. Or consider a subsidiary that receives management services from its parent and a loan from a sister company. Both flows are disclosable, along with the balances at period end.
A practical process often looks like this:
- Build and maintain a register of related parties, including individuals and their affiliated entities.
- Collect periodic declarations from directors and key managers about interests, roles, and family connections.
- Configure accounting systems to flag transactions with registered related parties.
- Review flagged transactions for terms, pricing basis, and approval.
- Aggregate balances and compile the disclosures, with review by finance leadership and legal.
Related Concepts and Variations
Several adjacent ideas often come up alongside related-party reporting:
- Key management personnel: those with authority and responsibility for planning, directing, and controlling the entity's activities, which can include non-executive directors.
- Government-related entities: the standard provides a partial exemption from some disclosures for entities connected through the same government, though certain information is still required.
- Control, joint control, and significant influence: concepts defined in other standards that determine whether a relationship exists.
- Conflict-of-interest policies and governance codes: internal or jurisdictional requirements that operate separately from accounting disclosure but rely on much of the same information.
Common Misconceptions and Pitfalls
- "Arm's-length pricing eliminates the need to disclose." Disclosure is driven by the relationship, not by whether terms were fair. An entity may state that terms were arm's length only if it can substantiate that claim.
- Overlooking individuals. Teams often focus on corporate affiliates and miss close family members or entities those individuals control.
- Ignoring transactions without payment. Transfers of resources, services, or obligations count even if no cash changes hands, such as guarantees or free use of assets.
- Treating the register as static. Relationships change when directors join or leave, ownership shifts, or families change circumstances. An outdated register leads to omissions.
- Aggregating too aggressively. Items of a similar nature may be combined, but doing so should not obscure the understanding of the effects on the entity.
- Assuming it is purely an accounting matter. Because the underlying data sits across several functions, weak coordination is the most common cause of disclosure gaps.
Key Takeaway
Strong related-party reporting depends on clear definitions, reliable data collection, and cross-functional accountability. Organizations that treat it as a shared governance process, rather than a year-end accounting task, are better positioned to produce complete, defensible disclosures.