AASB 124 contains numerous technical traps and judgement points that commonly cause errors or inconsistent disclosures if not managed deliberately. The Standard and its guidance highlight areas where preparers should be particularly cautious.
Misidentifying related parties by focusing on legal form
- The Standard directs attention to the substance of relationships not merely legal form (para 10). Preparers who mechanically apply organisational charts without assessing substance may misclassify relationships. Examples in the Implementation Guidance illustrate ministerial and government scenarios where apparent legal form does not automatically translate into KMP or related party status (IG3-IG6).
Ministers and public officeholders may or may not be KMP
- The Implementation Guidance emphasises that a Minister is not automatically KMP of every entity in the Minister’s portfolio; KMP status depends on the authority and responsibility to plan, direct and control the entity (IG3-IG6; examples 1-6). The guidance provides layered examples where Ministers are and are not KMP; failure to apply the guidance can either over‑report or under‑report KMP relationships.
Government-related entity exemption does not cover persons
- The partial exemption in paragraph 25 exempts transactions with the government and other entities tied by the same government. It does not exempt disclosures about transactions with persons who are related parties, such as Ministers, councillors or KMP (paras 25-27; BC14-BC17; IG10). A common mistake is to assume that government control means no related party disclosures are required concerning persons connected with the government; the Standard requires separate consideration.
Arm’s length assertions must be substantiated
- Paragraph 23 permits assertions that transactions were on terms equivalent to arm’s length only if such terms can be substantiated. The implication is an evidentiary burden; preparers should keep contemporaneous documentation proving pricing, comparable transactions or independent valuations.
Aggregation can conceal individually significant items
- The Standard allows aggregation of similar items (para 24) but requires separate disclosure where necessary for understanding. Practitioners must identify individually significant transactions that would be obscured by aggregation and disclose them separately. The government-related entity exemption’s alternative disclosure regime singles out individually significant transactions (para 26(b)(i)).
Management entity carve-out and disclosure timing
- Where KMP services are provided by a separate management entity, paragraphs 17A and 18A create a limited relief and require disclosure of amounts incurred for such services. Misunderstanding the carve-out may lead to double counting or omission of KMP compensation in the reporting entity’s financial statements. The IG clarifies reimbursement obligations and when disclosure is required (IG7-IG8).
Consolidation elimination exceptions
- The Standard instructs that intragroup related party transactions and outstanding balances are eliminated in consolidated financial statements except for transactions between an investment entity and its subsidiaries measured at fair value through profit or loss (para 4). Failure to apply that exception correctly can result in inconsistent consolidated disclosures.
Tier 2 and simplified disclosures
- Appendix B and AusB1 exclude entities applying AASB 1060 from full Standard requirements. Entities moving between tiers must be careful to apply the correct disclosure set and ensure that transitional disclosures and comparatives are treated consistently (AusB1; compilation table).
Materiality judgement and cost-benefit
- Implementation Guidance stresses materiality and the cost‑benefit trade-off in gathering and disclosing related party data, especially in the public sector where many interactions with related parties may occur on general public terms (IG11; BC17). Preparers must document materiality judgements and the rationale for not disclosing immaterial related party transactions.
Parent and ultimate controlling party naming nuances
- Paragraph 13 requires naming of parent and ultimate controlling party; Aus13.1 requires identification of overseas-incorporated parents and naming of an ultimate controlling entity incorporated in Australia, if any. This can be operationally tricky for complex international group structures and requires legal entity analysis and consistent public‑use consolidation verification.
Evidence for guarantees, terms and commitments
- Paragraph 18 requires disclosure of the terms and conditions of outstanding balances, including whether secured, and details of guarantees given or received. Practitioners must capture contractual terms, security arrangements and contingent obligations related to related party balances and ensure that such ancillary documents are available for disclosure and audit.
Overlap with other statutory reporting
- The Standard references reporting to other regulatory authorities and other disclosure regimes; preparers must ensure that AASB 124 disclosures are consistent with statutory registers and other public disclosures and that they do not inadvertently omit material overlaps or create contradictions (para 27; IG11).
Transition and versioning pitfalls
- The compilation and amendment history show different effective dates and transitional rules for amendments. Entities must identify which amending Standards apply to their reporting period (Compilation details; Aus28.1; Aus28.2; table of standards). Failure to apply the right version leads to non-compliance.
Document and retention requirements
- Although the Standard does not prescribe retention periods, the substantiation requirements and audit scrutiny mean entities should retain evidence demonstrating how related parties were identified, how materiality was assessed and how arm’s length assertions were supported.
Addressing these “gotchas” requires cross‑functional coordination across legal, treasury, procurement, payroll and finance teams; clear policies; and disciplined record-keeping.