Related party transactions: Documentation and scrutiny
Related party transactions are common, but regulators scrutinize them heavily. Know what to document, which red flags trigger audits, and how to prepare defensively.
This article is general information, not professional advice. Related party transaction rules and documentation requirements change — confirm current requirements with a tax adviser before executing large transactions.
Related party transactions are not inherently suspicious. Parents lend to subsidiaries. Companies buy services from affiliates. Holding companies own operating companies. This is ordinary corporate structure.
But regulators are skeptical. Related party transactions create opportunity for profit shifting—funneling revenue out of Indonesia to minimize local tax. So every related party transaction, no matter how routine, draws regulatory attention.
If you have related parties, expect scrutiny. Preparing defensively now saves you from reconstruction later.
What makes a transaction “related party”
Indonesian tax law defines related parties broadly:
- Ownership or control — directly or indirectly owning 20% or more of voting shares
- Common ownership — multiple entities owned by the same person or group
- Family relationships — spouses, parents, children, siblings (to certain degrees)
- Management control — when one entity has significant influence over another’s decisions
- Contractual arrangements — even if not related by ownership, arrangements that effectively link entities
The threshold is not high. A 20% stake triggers related party status. A family loan is a related party transaction. Management fees between affiliated companies are related party transactions.
What regulators scrutinize
The transaction price. Is it arm’s length? (We covered transfer pricing separately, but the principle applies to all related party transactions, not just cross-border ones.)
Business purpose. Why did the transaction occur? What business rationale supports it? “It seemed efficient” is not sufficient. Regulators look for legitimate business reasons—rent paid for premises actually used, interest charged on loans actually received, services rendered actually provided.
Timing and frequency. Related party transactions in odd patterns trigger flags. A payment right before year-end. A service fee that spikes in a loss year. Lumpy transactions that don’t align with business cycles.
Amounts relative to parties’ size. A small service fee from a large subsidiary to a parent rarely draws scrutiny. A $10 million management fee from a small operating company to a related entity will.
Documentation quality. Can you produce written evidence of the transaction? Invoices? Contracts? Payment evidence? The thinner the paper trail, the higher the audit risk.
Common red flags
Loans without interest or below-market rates. A shareholder loan to the company at 0% interest looks like disguised equity. Regulators recharacterize it and disallow the deduction. Interest should reflect market rates [verify: current market rates for comparable loans].
Management fees with no scope. “Management fee” is standard, but what exactly is being managed? By whom? For how many hours? A vague management fee with no deliverables is vulnerable.
Services described but not evidenced. The contract says “consulting services rendered,” but there is no output: no reports, no meetings, no tangible work product. Regulators disallow the deduction because the service is not substantiated.
Rent paid for unused premises. A company pays rent to a related owner for office space that is not occupied or is underutilized. Regulators disallow the deduction because the rent is not tied to actual business use.
Purchases from related suppliers at inflated prices. Inventory purchased from a related supplier at prices consistently above market. Regulators reduce the cost of goods sold and increase profit.
Year-end lumpiness. A transaction (especially a large one) that occurs only in December, only in loss years, or only when the company needs a deduction—this raises suspicion.
Building a defensible position
For every material related party transaction, document:
-
The business purpose — in writing. Why does the company need this service, loan, or supply? What business problem does it solve?
-
The price justification — for goods or services, show comparable prices from independent suppliers. For management fees or interest, show market rates. Include any benchmarking studies.
-
The contract — a written agreement specifying the parties, price, terms, deliverables (if services), and payment schedule. Even informal relationships should be documented. The absence of a contract signals low credibility.
-
The performance evidence — invoices, time records, delivery receipts, service reports, or other tangible evidence that the transaction occurred and was performed.
-
The business cycle rationale — why does this transaction occur in this timeframe? Tie it to business cycles or operational need, not tax strategy.
-
The approval trail — who approved the transaction internally? At what level? Documented approval shows the transaction was considered and approved through normal channels, not ad hoc.
If you are audited
Auditors will ask for all of the above. If you can produce it, the audit moves forward. If you cannot, the auditor has latitude to reconstruct pricing, disallow deductions, or impose penalties.
The defensive posture is: treat related party transactions the same way you would if the other party were independent. Compete on price. Negotiate terms. Document thoroughly. This is not just defensive—it also means you are managing related party transactions as efficiently as you would at arm’s length.
Related party transactions are a permanent audit focus. Building the documentation at transaction time—when you can think clearly about business purpose—is far more efficient than reconstructing it defensively. If you need help documenting related party transactions or want to review a planned related party arrangement, our tax practice can work with you.