Related Party Transaction Procedures: AI + Manual Verification [2026]

Q: Q3: What if RP pricing is non-arm's-length?

1. AI pattern detection identifies RPs that manual review would miss. Circular payments, round-trip transactions, shell companies → flagged automatically.

Q: Ready to strengthen your RP testing?

1. Start Free Trial: Sign up here

Published: March 24, 2026 | Category: Audit Automation | Read Time: 13 minutes | Author: CORAA Team

Introduction

Related-party transactions remain a consistent NFRA finding: incomplete disclosure, inadequate arm's-length verification, missing party identification.

The challenge: Identifying related parties is difficult. Traditional approach relies on management's list. But management may miss parties (intentionally or unintentionally). Manual analysis of transaction patterns to identify suspected RPs is time-prohibitive.

AI changes this. By analyzing transaction patterns—vendor payment frequency, circular payments, round-trip cash flows—AI identifies likely related parties. Auditors then verify (manual step remains).

Result: Better RP identification → more comprehensive testing → better defensibility.

This guide covers:

RPT complexity in Indian audits
AI-assisted RP identification procedures
Manual verification procedures (AI identifies, auditor verifies)
Common NFRA findings and how to avoid them
Real audit results

RPT Complexity
Manual RPT Procedures (Limitations)
AI-Assisted RP Identification
Arm's-Length Verification
Testing Procedures
Real Results
Common Questions
Conclusion

RPT Complexity

Why RPT Auditing is Challenging

The breadth: Related parties include:

Shareholders (direct + indirect)
Board members & their families
Key management personnel
Entities controlled/significantly influenced by above
Joint ventures, associates
Non-controlling interest entities

The depth: Identifying all related parties requires:

Understanding ownership structures (shareholders, subsidiaries, joint ventures)
Tracing director relationships (family connections, shared board seats)
Recognizing influence (informal control, de facto control)
Identifying disguised parties (shell companies, straw entities)

The subjectivity: "What makes someone 'related'?" is judgment-heavy, especially for influence-based relationships.

Common RPs Missed in Indian Audits

Type 1: Shell company entities (minimal presence; used for cash flows)

Type 2: Circular cash flows (payment out → payment in, same period, round-trip)

Type 3: Indirect relationships (shareholder → company → director's relative, multi-hop relationships)

Type 4: Influence-based parties (no formal control, but de facto influence exists)

Manual RPT Procedures (Limitations)

Traditional Approach

Step 1: Obtain management's RP list

Management identifies all related parties they know of
Assume list is complete

Step 2: Verify transactions

For each RP transaction: Review contract, verify pricing, test authorization

Step 3: Disclose

Include all identified RPs in Schedule 7 (RP transactions)

Limitations

Limitation 1: Management's list may be incomplete (intentionally or unintentionally)

Limitation 2: Manual pattern analysis impractical (6,000+ GL entries; manual relationship analysis = 100+ hours)

Limitation 3: Disguised parties not detected (shell companies, straw entities not identified without specific investigation)

AI-Assisted RP Identification

Detection Rule 1: Transaction Pattern Analysis

Rule: Identify vendors/customers with unusual patterns:

High-frequency payments to same vendor (monthly, like internal transfers)
Round-trip payments (payment out → payment back, same amounts)
Circular payment chains (A → B → C → A roundtrip)

Why it identifies RPs: Genuine vendors typically have varied payment patterns. RPs often show regular, round-trip patterns.

Example detection:

Month 1: Payment to Vendor X = ₹50L
Month 2: Payment from Vendor X = ₹50L
Pattern: Likely RP (round-trip, round amount)

Detection Rule 2: Shell Company Detection

Rule: Identify vendors with minimal online presence, unusual entity characteristics:

Vendor has no website, minimal business history
Vendor incorporated recently (< 2 years)
Vendor address is residential (not business location)
Vendor has minimal other transactions (appears one-time only)

Why it matters: Shell companies often used for RP transactions (disguise transfers to related parties)

Detection Rule 3: Related Entity Matching

Rule: Cross-match company's vendor list against known related parties:

If vendor name matches shareholder name (partial or full match), flag
If vendor shares address with known shareholder, flag
If vendor director matches company director, flag

Why it works: Hidden RP entities often use director names or family entity names

Detection Rule 4: Pricing Anomaly Analysis

Rule: For top vendors, analyze pricing vs. industry benchmarks:

If prices 10%+ below market (unusually low), flag (possible subsidy to related party)
If prices 10%+ above market (unusually high), flag (possible overcharge by related party)

Why it matters: RPTs often at non-arm's-length pricing

AI-Assisted Procedure: Full Workflow

Step 1: Data Extraction

Extract:

All vendors (name, amount paid, frequency)
All customers (name, amount received, frequency)
All payment patterns (circular, round-trip, high-frequency)
Company structure (known shareholders, directors, joint ventures)

Step 2: AI Identification

Run detection rules:

Pattern analysis (high-frequency, round-trip, circular)
Shell company analysis (minimal presence indicators)
Entity matching (vendor name/address match to known parties)
Pricing analysis (deviation from market rates)

Output: Risk-scored list of suspected RPs (100-200 potential relationships)

Time: 30 min (fully automated)

Step 3: Manual Verification - Priority Ranking

Auditor reviews risk-scored list; prioritizes investigation:

High-priority suspects (investigate all):

Vendors >₹50L transactions (material)
Round-trip payments (obvious RP indicator)
Named entities matching known shareholders/directors

Medium-priority suspects (investigate sample):

Vendors ₹10-50L transactions
Unusual pricing (high/low variance)
Shell company indicators

Low-priority suspects (spot-check):

Small vendors <₹10L
One-time transactions
Minimal risk indicators

Step 4: Manual Verification - Detailed Investigation

For each priority-ranked suspect:

Obtain/review vendor agreement
- Verify vendor legitimacy (website, business address, track record)
- Document services/goods provided (is transaction genuine business purpose?)
Trace to shareholder/director records
- Cross-check vendor ownership/directors against shareholder/director lists
- If matches found → likely RP (or at minimum suspicious)
Interview management
- Ask: "Do you know this vendor?" "What is the relationship?"
- Listen for hesitation, vague answers (often indicates hidden relationship)
Determine RP classification
- Confirm as RP (if relationship identified) OR
- Reclassify as non-RP (if verified unrelated)

Output: Verified list of RP entities

Time: 2-4 hours (depending on # suspects)

Arm's-Length Verification

Procedure 1: RP Pricing Analysis

For each RP transaction:

Obtain comparable market pricing:
- Price same goods/services to non-RP customers (if available)
- Research market rates (industry benchmarks, published pricing)
- Obtain third-party quotes
Compare:
- RP pricing vs. non-RP pricing
- RP pricing vs. market rate
- RP pricing vs. industry benchmark
Assess:
- If within 5% of market: Likely arm's-length ✓
- If 5-10% variance: Question/investigate
- If 10%+ variance: Likely not arm's-length ✗
Document:
- Basis for pricing assessment
- Any differences; management explanation

Output: RP pricing assessment; any adjustments needed

Procedure 2: RP Transaction Reasonableness

For each RP transaction:

Verify business purpose
- Is transaction necessary for operations? (eliminate unnecessary transactions)
- Is transaction timing reasonable? (not forced/artificial timing)
- Is transaction value reasonable? (not inflated/minimal)
Review authorization
- Was transaction approved per policy? (RP transactions require specific approval)
- Was approval by independent party? (not by RP themselves)
- Is documentation sufficient?
Assess going concern impact
- Any contingent RPs liabilities? (undisclosed obligations to related parties)
- Any related-party loan impairments? (loans unlikely to be repaid)

Testing Procedures

Procedure 1: Transaction Authorization Testing

For material RP transactions:

Trace to board approval (RP transactions >threshold require board approval)
Verify approval was by independent directors (not RP themselves)
Verify terms disclosed to board

Procedure 2: Disclosure Completeness

Verify Schedule 7 includes:

All identified RPs (entities AND individuals)
Nature of relationship (family, shareholder, director, etc.)
Quantum of transactions (annual amount)
Balances outstanding (year-end amounts due to/from RPs)
Terms & conditions (are they disclosed?)
Any contingent liabilities (guarantees, commitments)

Real Results

Case Study 1: Hidden RP Vendor Identified

Background: Manufacturing company

Management's RP list: 5 entities (all known to management)

AI analysis identified: 12 additional suspected related parties (circular payments, round amounts, entity matching)

Manual verification found: 4 additional RPs confirmed (others were false positives)

Details of confirmed RPs:

Vendor 1: ₹100L payments; entity director = CEO's brother (hidden RP)
Vendor 2: ₹75L circular transactions; entity owned by shareholder's trust
Vendor 3: ₹50L payments; supply contract included RP markup
Vendor 4: ₹30L payments; shell company indicator, minimal business presence

Audit adjustments:

RP disclosure expansion (4 new entities added to Schedule 7)
Related-party pricing analysis (Vendor 3 required pricing adjustment ₹8L)
Related-party loan classification (Vendor 4 payment was disguised loan, reclassified)

Impact: Additional RP disclosure required; pricing adjustment; classification fix

NFRA finding: "Auditor identified previously undisclosed RPs through systematic testing; appropriate procedure"

Case Study 2: Round-Trip Payment Detection

Background: Tech company

Scenario:

Payment to RP Tech Services: ₹50L (Feb)
Receipt from RP Tech Services: ₹50L (Mar)
Same amount, consecutive month, round-trip pattern

Audit investigation:

Contract review: Services allegedly provided (custom software development)
Work verification: No evidence of work performed; no deliverables
Discussion with management: CEO acknowledged service was pretext for capital transfer

Root cause: CEO needed to transfer funds to family entity; used RP "service" as cover

Audit classification:

Reclassify as related-party loan (not service expense)
RP loan classification on balance sheet
Disclosure requirement updated

Net accounting impact: Minimal (both were expenses/receipts before; now loans), but disclosure corrected

Common Questions

Q1: How do I prove a vendor is NOT a related party?

A: Document:

Vendor's legitimate business (website, history, other customers)
Arm's-length pricing verification
No shared directors/shareholders/family relationships
Industry-normal transaction patterns

Absence of RP characteristics + verification = reasonable basis to classify as non-RP

Q2: Should I test all RP transactions or sample?

A: Test:

100% of material RPs (>5% of revenue/profit or >₹50L)
Sample of non-material RPs (minimum 30%)

Q3: What if RP pricing is non-arm's-length?

A: Audit adjustment needed to record at arm's-length:

Reduce expense (if paid too high)
Increase revenue (if charged too low)
Record related-party adjustment in memo

Conclusion

5 Key Takeaways

AI pattern detection identifies RPs that manual review would miss. Circular payments, round-trip transactions, shell companies → flagged automatically.
Manual verification remains essential. AI identifies suspects; auditor verifies legitimacy through investigation and testing.
Arm's-length pricing verification is critical. RP transactions not at market rates require adjustment.
100% of material RPTs must be tested. Sampling insufficient; NFRA expects comprehensive RP testing.
Disclosure completeness is often weak. Verify Schedule 7 complete; common omissions include terms & conditions, contingent liabilities.

Ready to strengthen your RP testing?

Start Free Trial: Sign up here
Book a Demo: See CORAA's RPT Detection in action
Read More: 100% Ledger Testing with AI

About CORAA

CORAA automates related-party identification and testing for Indian auditors. Use AI to identify suspected RPs; focus manual verification on high-risk relationships. Comprehensive RP testing → better audit quality → NFRA defensibility.

Learn more: Visit our website

Free newsletter

Get weekly audit insights

Practical guides on audit automation, SQM1 compliance, and Ind AS procedures — delivered to 2,000+ CA professionals every Friday.

No spam. Unsubscribe any time.

Topics

related party audit proceduresRPT identificationAI related party detectionarm's-length pricing auditNFRA related party testing

Back to all articles