It started with a transaction that looked completely ordinary.
A growing company needed professional services. A sister concern within the same business group had the required team and experience. The engagement was approved internally, the work was completed, an invoice was raised, and the payment was made through the banking channel.
Nothing looked unusual.
There was no cash payment. No hidden agreement. No obvious attempt to move money out of the business.
So when the statutory auditor asked a simple question — “Why has this transaction not been reported as a related-party transaction?” — the finance team was caught off guard.
The transaction had never been flagged.
Not by accounts.
Not by management.
Not during the monthly closing process.
It was the auditor who noticed the connection.
And that one question opened a much bigger discussion about related-party transactions, corporate governance, disclosure requirements, transfer pricing, and internal controls.
The Problem Wasn't the Transaction. It Was the Process.
The company had always viewed related-party Compliance as something that happened at year-end.
The accounts team would prepare financial statements, the auditor would review them, and any required disclosures would be added before filing.
But the business had changed significantly over the years.
New companies had been incorporated. Directors had taken positions in other entities. Family members had become shareholders. Group companies had started providing services to each other.
The organisation had grown.
Its related-party tracking process had not.
That difference eventually became the problem.
The transaction identified by the auditor was legitimate from a commercial perspective. The services had actually been provided, the invoice was supported, and the payment had been made.
But the company had failed to properly identify and evaluate the transaction from a related-party compliance perspective.
And that distinction matters.
A transaction can be genuine and still require appropriate disclosure, approval, documentation or reporting.
What Exactly Is a Related-Party Transaction?
In simple terms, a related-party transaction is a transaction between a company and a party connected to it through relationships such as ownership, management, control or other specified connections.
Depending on the applicable law and the nature of the entity, related parties can include:
- Directors and their relatives
- Key managerial personnel
- Companies under common control
- Holding and subsidiary companies
- Associate companies
- Entities in which directors or their relatives have significant interests
- Other parties covered by applicable accounting and corporate regulations
Transactions can take many forms.
They may involve:
- Sale or purchase of goods
- Rendering or receiving services
- Loans and advances
- Leasing arrangements
- Guarantees
- Investments
- Transfer of assets
- Management fees
- Royalty or licensing arrangements
- Other financial or commercial dealings
The important point is that the relationship itself can trigger compliance considerations.
You do not necessarily have to wait until a transaction becomes suspicious.
Why the Auditor Flagged It
When the Auditor reviewed the company's vendor and expense records, one name immediately stood out.
The vendor was not an unrelated third party.
Its ownership and management structure connected it to individuals associated with the company.
The auditor therefore asked the finance team to establish:
- Whether the counterparty qualified as a related party.
- Whether the transaction was covered by applicable related-party provisions.
- Whether the required approvals had been obtained.
- Whether the transaction was conducted on appropriate commercial terms.
- Whether the transaction required disclosure in the financial statements.
- Whether any other regulatory or tax implications needed to be considered.
Suddenly, what had appeared to be a normal vendor payment became a related-party compliance review.
The company had not intentionally hidden the transaction.
It had simply failed to connect two pieces of information:
Who the vendor was — and who was connected to that vendor.
That is one of the most common weaknesses in related-party transaction monitoring.
Why Related-Party Transactions Receive So Much Attention
Related-party transactions are not automatically illegal or improper.
Businesses regularly transact with group companies, subsidiaries, directors, promoters and other connected parties for perfectly legitimate commercial reasons.
The concern is different.
When two parties are connected, there may be a greater possibility that the terms of a transaction could differ from those available between independent parties.
For example, imagine a company purchasing services from an entity controlled by one of its directors.
The transaction may be genuine.
But stakeholders may reasonably ask:
Was the price commercially reasonable?
Was the service actually required?
Was an independent vendor considered?
Who approved the transaction?
Was the relationship properly disclosed?
These questions are at the heart of corporate governance and related-party compliance.
The Bigger Risk: When One Missed Transaction Becomes a Pattern
The auditor's question did not stop with one invoice.
Once the relationship was identified, the finance team had to look backwards.
Were there other transactions with the same entity?
Were there payments to other group companies?
Were directors or their relatives connected with additional vendors?
Had loans or advances been provided?
Were any assets transferred between group entities?
Had management fees or shared expenses been charged?
The company discovered that the issue wasn't necessarily one transaction.
It was the absence of a systematic related-party transaction monitoring mechanism.
That is where the real risk lies.
A company may correctly record every transaction in its accounting software while still failing to identify related-party relationships.
Accounting records tell you what happened.
A compliance framework must also establish who was involved and whether the relationship changes the regulatory treatment.
Related-Party Compliance Is More Than a Disclosure Exercise
One of the biggest misconceptions is that related-party compliance simply means adding a note to the financial statements.
In reality, depending on the entity and transaction, the compliance process can involve several stages.
1. Identify the relationship
The company needs an updated understanding of its directors, promoters, key managerial personnel, shareholders and connected entities.
2. Identify the transaction
The organisation should determine whether dealings with those parties fall within applicable related-party transaction provisions.
3. Check approvals
Certain transactions may require specific approvals depending on the applicable legal framework and circumstances.
4. Evaluate the terms
The commercial basis of the transaction should be properly documented.
5. Maintain supporting records
Agreements, invoices, work orders, board approvals, valuation documents and other relevant records can become important during an audit or regulatory review.
6. Make appropriate disclosures
Where required, related-party transactions must be appropriately reflected in financial statements and other applicable filings.
The exact requirements depend on the company's legal structure, applicable regulations and nature of the transaction.
What the Company Changed After the Audit
The company eventually realised that the solution wasn't simply correcting one disclosure.
It needed a better system.
Management created an updated related-party register and introduced a process requiring finance to check new vendors and counterparties against the group's ownership and management information.
The company also started reviewing related-party transactions periodically instead of waiting for the annual audit.
Contracts involving group entities were documented more carefully.
Approval responsibilities were clarified.
And before the financial statements were finalised, the finance and compliance teams conducted a separate related-party review.
The objective was simple:
Don't wait for the auditor to discover the relationship. Identify it before the transaction becomes a compliance issue.
Shunyatax's View:
The Best Compliance Control Is an Early Warning System
At Shunyatax Global, we believe related-party compliance should not begin when the auditor asks a question.
It should begin when the relationship or transaction is created.
For companies with promoters, multiple group entities, family-owned businesses, subsidiaries, associates or complex ownership structures, maintaining a clear related-party transaction framework is essential.
A proper review can help businesses understand:
- Who qualifies as a related party
- Which transactions require closer scrutiny
- Whether appropriate approvals are in place
- Whether documentation supports the commercial rationale
- What disclosures may be required
- Whether tax or transfer-pricing considerations arise
- Whether existing internal controls are actually working
If your company has multiple group entities, promoter interests or transactions with directors and connected businesses, Shunyatax Global can help you review and structure your related-party compliance process before an auditor, regulator or stakeholder raises the question.
Because the expensive part of a related-party issue is often not the transaction itself.
It's discovering the compliance gap after the transaction is already on the books.
As businesses grow, relationships become more complicated.
Your compliance process needs to grow with them.
Don't wait for the auditor to ask, “Why wasn't this flagged?”
Review your related-party transactions before they become an audit finding.
Talk to Shunyatax Global for Corporate Compliance, Tax & Advisory Support.
📞 +91 9461514198 |
📩 office@shunyatax.in
Book a Confidential Advisory Call → https://shunyatax.in/appointments