A director signs off a lease between the trading company and the family trust. The rent feels commercially sensible. Months later, the auditor asks a simple question: “What evidence shows the terms were arm's length and properly approved?” That's where many related party transactions stop being routine and start becoming expensive.
By Panbo Ye, CFP® | FCPA | SSA® | Founder, Everglow
Who this article is for: Business owners, directors, trustees, not-for-profits, SMSF stakeholders, and inbound Chinese enterprises in Australia that deal across connected people or entities.
What Exactly Is a Related Party Transaction in Australia?
A related party transaction is a dealing between a business and someone close enough to influence it, or be influenced by it. In practice, that often means directors, key management personnel, family members, trusts, associated companies, and entities within the same group.
The cleanest starting point is the accounting rule. In Australia, AASB 124 is the foundational disclosure standard. It requires an entity to disclose the nature of the related-party relationship and details of transactions, even if no price is charged, and it specifically includes key management personnel compensation, as set out by the Australian Accounting Standards Board AASB 124 standard.

Who counts as a related party
Imagine a family dinner table. If one person can influence who gets served first, how much they get, or whether the meal happens at all, independence is already reduced. Business structures work the same way.
Common examples include:
- Directors and executives: Their personal entities, family interests, and arrangements involving services or loans may fall into scope.
- Controlled entities: Subsidiaries, parent entities, and connected trusts often sit inside the same influence chain.
- Close family relationships: A transaction with a spouse's company or a sibling's trust may still need careful analysis.
For many Australian groups, this reaches further than expected. Closely held companies, discretionary trusts, and not-for-profits often use shared resources informally. If you want a plain-English refresher on trust structures, this guide on how a trust works in Australia is a useful companion.
Practical rule: If a transaction would look different with an unrelated party, treat it as a related party transaction first and test it properly second.
What counts as a transaction
A transaction isn't limited to a sale. The accounting standard is broader than that.
It may include:
- Use of assets: Leasing premises, using vehicles, or occupying trust-owned property.
- Funding arrangements: Director loans, shareholder advances, guarantees, and repayments.
- Services and obligations: Management fees, bookkeeping support, staff sharing, and assumption of liabilities.
A common mistake is assuming that “no money changed hands” means “nothing to disclose”. Under AASB 124, that assumption may fail because the standard captures transfers of resources, services, or obligations whether or not a price is charged.
The core point is simple. Related party transactions aren't always wrong. They become a governance problem when the relationship changes the terms, the approval process, or the quality of disclosure.
Why These Transactions Attract Scrutiny from the ATO and ASIC
Regulators care because connected-party dealings can change outcomes without looking unusual in the general ledger. A rent payment can shift profits. A loan can mask liquidity stress. A service fee can sit comfortably in the accounts while still lacking commercial support.
The Australian Taxation Office (ATO) is concerned with tax integrity. The Australian Securities and Investments Commission (ASIC) is concerned with governance, duties, and market confidence. Different mandates, same pressure point. Connected dealings can distort what outsiders think is really happening.
Why common transactions get attention
Research cited in the literature found that the mean number of related party transactions per company was 3.92, the median was 2, across a sample of 112 companies, and several transaction types appeared in about 20% of companies sampled. Real estate was the most common type, accounting for 14.4% of all related party transactions, according to the Rutgers research paper on related party transactions.
That pattern makes sense in Australian practice. Property, loans, and service arrangements are exactly where private groups and family structures tend to operate. They're ordinary transactions commercially, but they're also the easiest place for terms to drift away from market benchmarks.
What regulators are really testing
The first question usually isn't “did this exist?” It's “was it fair, authorised, and visible?”
That means scrutiny often falls on:
- Tax effect: Whether pricing, deductibility, or allocation of income reflects a genuine commercial arrangement.
- Conflict management: Whether directors identified their interest and stepped out of decision-making where appropriate.
- Financial reporting reliability: Whether balances, commitments, and terms are recorded in a way that a reader can understand.
A related party transaction rarely causes trouble because it exists. Trouble starts when the file can't show who approved it, why the pricing made sense, and where it appears in the accounts.
If your organisation is preparing for deeper review, internal governance and testing matter as much as year-end disclosure. This broader overview of audits and compliance for Australian entities gives context on how these issues surface in practice.
The commercial trade-off is straightforward. Informal arrangements feel efficient inside a family or founder-led group, but that convenience may create a much heavier burden later when the ATO, ASIC, or an auditor asks for evidence.
Specific Rules for Different Australian Entities
The rule set changes with the entity type, but the practical issue is constant. You need enough evidence to show the transaction was commercially grounded, properly approved, and accurately recorded. Poorly documented defensibility is often the weakness, not the transaction itself.
Private companies and family groups
Private groups usually run into related party transactions through rent, service charges, staff sharing, and loans between entities. These arrangements may be sensible, especially where a trust owns property and a company conducts the business, but they need structure.
For family groups, the minimum file usually includes a written agreement, approval minutes, and support for pricing. If your structure relies heavily on trust arrangements, this external guide on navigating family trusts in Australia 2026 gives a broader structural lens.
Not-for-profits and charities
Not-for-profits face a different reputational test. Even where a transaction is lawful and beneficial, stakeholders may ask whether a connected person received preferential treatment.
Boards of charities and community organisations should be especially disciplined about:
- Conflict disclosure: Interested board members should disclose their connection early and clearly.
- Independent comparison: Obtain a market quote, benchmark, or alternative supplier evidence where possible.
- Minute quality: Minutes should record the rationale, abstentions, and approval basis.
SMSFs
Self-Managed Super Funds (SMSFs) carry a stricter practical environment because related party dealings can intersect with superannuation rules, sole purpose concerns, and asset use restrictions. Even a transaction that feels harmless in a family context may raise a very different issue inside an SMSF.
For SMSF trustees, paperwork is only part of the answer. The transaction itself must fit the governing rules, not just look tidy.
Inbound groups and cross-border structures
Chinese inbound businesses and other cross-border groups often use multiple entities for funding, procurement, and management support. The challenge isn't only translation. It's that an arrangement accepted informally in one jurisdiction may need much sharper documentary support in Australia.
Where pricing crosses borders, intercompany files need to align with accounting, tax, and governance records. As a result, proper transfer pricing documentation for Australian groups often becomes part of the wider related party file.
The table below shows a practical baseline for documentation.
Minimum documentation by transaction type helps directors and trustees avoid the common “we all understood it” problem.
| Transaction Type | Minimum Documentation | Key Consideration |
|---|---|---|
| Property lease | Signed lease, market appraisal, board or trustee approval | Whether rent and terms align with comparable premises |
| Director or shareholder loan | Loan agreement, repayment terms, interest basis, approvals | Whether the balance is really funding, not a trade balance |
| Management or service fee | Service agreement, work scope, invoice support, pricing rationale | Whether there was a real service and a defensible basis for the charge |
| Asset sale or transfer | Contract, valuation support, approval minutes | Whether value was independently supported at the transaction date |
Different entities face different overlays, but the working standard is the same. If you can't reconstruct the commercial logic from the file, the arrangement may be difficult to defend.
Worked Example: The Nguyen Family's Property Lease
The Nguyen family in Parramatta runs Nguyen Enterprises Pty Ltd, a trading company. The shop operates from a commercial property owned by the family trust. That rent is a related party transaction because the tenant and landlord sit within the same family-controlled structure.

Let's make it concrete. The company pays $4,800 per month to occupy the Parramatta premises. The family trust receives the rent and services the property outgoings. On its face, that's a normal operating arrangement. The compliance question is whether the family can prove the amount, terms, and approvals were commercially defensible.
What the Nguyen family did right
They started with market support. Before signing anything, they obtained an independent rental appraisal for comparable local commercial space. That doesn't guarantee the exact number is perfect, but it gives the board and trustee a proper basis for the decision.
They then documented the arrangement like a third-party deal:
- Formal lease: The lease set out rent, term, review mechanism, outgoings, and payment timing.
- Company approval: The company recorded a board minute approving entry into the lease and noting the related party connection.
- Trust records: The trustee kept matching records showing why the lease was in the trust's interests.
If a lease between related parties is real, it should read like a lease you'd be willing to show a bank, an auditor, and the ATO on the same day.
Where families often slip
The usual failure isn't the rent amount. It's the gap between intention and records.
The Nguyen family avoided these common errors:
- Backdating paperwork: They signed documents before occupancy, not after questions were raised.
- Blurring private and business costs: Rent went through the books consistently, with no casual offsets.
- Ignoring state taxes: Property structures can trigger wider issues. If the arrangement changes legal ownership or beneficial interests, separate duty questions may arise. This guide on stamp duty on property in Australia is worth reviewing where restructures are involved.
At year end, the accounting file could link the lease to the rent ledger, bank payments, approval minute, and supporting valuation material. That is what a defensible related party transaction looks like in practice.
A well-run related party lease should look boring. If the paperwork makes it look ordinary, commercial, and traceable, you've usually done the hard part properly.
How to Build a Defensible Compliance Framework
A defensible framework does one thing well. It allows an outsider to understand who the related parties are, what happened, why the terms were commercially supportable, and who approved the arrangement.
That's also where audit pressure tends to land. Auditing standards require auditors to test whether a transaction had a genuine business purpose and was properly authorised, and to assess management's ability to identify and approve related parties. Weak controls in those areas increase the risk of misstatement or incomplete disclosure, as reflected in PCAOB Auditing Standard AS 2410 on related parties.

What works in practice
A good framework isn't a thick policy no one reads. It's a short operating system that directors, trustees, and finance staff use.
The strongest setups usually include:
- A related party register: Maintain a live list of directors, executives, close family connections, trusts, and associated entities.
- Approval rules: Set clear internal thresholds for who approves leases, loans, service agreements, and unusual balances.
- Transaction files: Keep the agreement, pricing support, board minutes, invoices, and ledger mapping together.
A visual guide to compliance risk management can help boards think about how these controls fit into broader governance.
What usually fails under review
Weak files tend to have the same pattern. People know the arrangement is genuine, but they've never converted that knowledge into evidence.
Typical failure points include:
- Oral approvals: “We all agreed to it” isn't a control.
- Missing pricing rationale: “It felt fair” doesn't help much if no benchmark exists in the file.
- Ledger confusion: Loans, advances, and trade balances get mixed together, which can distort disclosure and liquidity analysis.
For organisations formalising their governance, this page on governance and compliance advisory outlines the broader operating discipline these files should sit within.
The best evidence is created at the time of the decision, not reconstructed at year end.
If you want related party transactions to survive scrutiny, build the file when the deal is agreed. Retrospective tidy-up may help presentation, but it rarely fixes weak governance.
Frequently Asked Questions About Related Party Transactions
Does an interest-free loan from me to my company count?
It may. A related party transaction is defined broadly under AASB 124, and the issue isn't only whether interest was charged. Key questions are whether the relationship is captured, whether the terms were documented, and whether the balance is recorded and disclosed appropriately for your reporting context.
If I employ my spouse in the business, is that a related party transaction?
It could be, depending on the structure, role, and reporting framework. Employment arrangements involving close family members deserve extra care because the market basis may be questioned. Keep a position description, approval record, payroll support, and evidence that remuneration aligns with the work performed.
What if the terms aren't perfectly arm's length but the deal is still commercially sensible?
That's where defensibility matters most. A transaction doesn't become acceptable merely because the parties say it helped the business. You need a clear rationale, approval process, and evidence showing why the terms were chosen and why they were still appropriate in the entity's circumstances.
We found an older transaction that wasn't disclosed properly. What should we do?
Don't ignore it. Review the accounting impact, the governance record, and whether prior-period disclosure or amendment may be needed. The right response depends on materiality, the entity type, and whether tax, audit, or legal consequences flow from the omission. Early review usually gives you more options than late discovery.
Are small recurring charges less risky than a single large transaction?
Not necessarily. Repeated management fees, rent adjustments, reimbursements, or inter-entity funding can accumulate over time and become material through frequency rather than size. Small items also tend to be processed informally, which means they often have the weakest evidence trail when reviewed later.
What's the simplest test for whether our documentation is good enough?
Ask whether an independent reviewer could understand the transaction without calling the founder, trustee, or finance manager. If the answer is no, the file probably needs work. Good documentation explains the relationship, the commercial purpose, the pricing basis, the approval path, and how the transaction appears in the accounts.
If you would like clarity on how these principles may apply to your own circumstances, contact Everglow Prosperity on 1300 913 929 or email contact@everglow.au. To book directly: Book a meeting with Panbo.
Want help applying this to your situation?
Every situation is different. Book a time with our team to talk it through, or call us on 1300 913 929.
Book a meetingOur audit and assurance services →See our fees →
