How NBFCs Use Counterparty Detection to Spot Related-Party Lending Risks

A promoter-run trading business applies for a ₹40 lakh working capital loan. The bank statement shows regular monthly credits of ₹6–9 lakh over 12 months. Income looks steady, turnover appears plausible.

What the manual review didn’t catch: a substantial portion of those credits were coming from two entities that the promoter’s wife and brother controlled. The same money was cycling between accounts. The business had two genuine external customers. The rest of the “revenue” was rotation.

This is related-party fund inflation, and it’s one of the more reliable ways MSME borrowers conceal a weak underlying business from a lender’s view. It’s also one of the harder risks to spot through a conventional bank statement review. Counterparty detection is how credit teams catch it, using a bank statement analyser like Precisa that maps every counterparty across all submitted accounts automatically.

Key Takeaways

• Related-party fund rotation is one of the harder credit risks to detect manually because the transactions look like ordinary business receipts in isolation.
• Automated counterparty detection maps every entity a borrower transacts with across all submitted accounts, flagging concentration, circularity, and cross-account connections that account-level review misses.
• The RBI’s Amendment Directions on Lending to Related Parties, issued on 5 January 2026 and in force from 1 April 2026, treat related-party exposure as a distinct governance risk requiring board-level oversight.
•  Counterparty detection doesn’t replace underwriter judgment; it gives the credit officer the right question to ask before approving.
• The analysis is only as thorough as the accounts submitted, which is why PDF forensics and Account Aggregator data matter alongside counterparty detection.

What Related-Party Flows Look Like in Bank Statements

Related-party transactions in a borrower’s account don’t announce themselves. They appear in one of several forms, each of which can look ordinary in isolation:

• Regular transfers from entities controlled by promoters, directors, or family members are recorded as business receipts or supplier payments.
• Circular flows between connected accounts, where money leaves one account and returns to the same or a linked account within days or weeks.
• Heavy credit concentration: a business whose incoming receipts come from one or two counterparties with no visible customer diversification.
• Periodic large credits timed precisely around the assessment window, from counterparties who don’t appear in earlier or later months.

None of these patterns is inherently fraudulent on its own. A business might legitimately receive most of its revenue from one large client. A promoter might make legitimate director loans to the company. The risk signal is in the combination: concentrated sources, circular timing, and counterparties that can be traced back to the promoter group.

When 70–80% of a borrower’s credits originate from entities linked to the same promoter, and those same entities are receiving transfers from the borrower’s account, the picture stops looking like a trading business and starts looking like a closed loop.

Why Manual Review Can’t Catch This Reliably

Standard bank statement review focuses on average monthly balances, the ratio of credits to debits, salary credits, EMI bounces, and the presence of large unexplained debits. An experienced reviewer will catch the obvious flags.

The problem is that manual review is almost always account-level. A reviewer looking at a single bank account sees the credits. Unless they systematically identify each counterparty in the statement and cross-check whether those counterparties are connected to the borrower, the circular flow goes unnoticed.

Even when borrowers submit multiple accounts, tracing counterparties across accounts manually, across a 12-month statement period with hundreds of transactions, is not something a credit analyst can do at lending speed. Teams processing dozens or hundreds of applications a month cannot run this kind of review on a case-by-case basis.

How Counterparty Detection Works

Automated counterparty detection processes all transactions across every submitted account and builds a structured map of who the borrower is transacting with: counterparty names, amounts, frequency, direction, and timing.

From this map, the system identifies:

• Counterparties that appear on both the credit side and the debit side of the statement, i.e., entities that pay the borrower and also receive payments from them.
• High concentration of receipts from a small number of counterparties.
• Timing patterns that indicate circular rotation, specifically credits followed by debits of similar amounts to the same counterparty within short windows.
• Counterparties appearing across multiple accounts submitted by the same borrower indicate a shared financial network. 

What counterparty detection gives the credit team is visibility into who is genuinely paying this borrower, and whether the money has any real business origin. That’s a fundamentally different question from “how much money came in this month.”

The Regulatory Context: RBI’s Related-Party Lending Directions

The risk of related-party exposure in lending has been under the RBI’s active scrutiny for some time.

In January 2026, the RBI issued amendment directions tightening how regulated entities, including all categories of NBFCs, manage lending to related parties. The new directions expanded the definition of who qualifies as a “related party” to include not just directors and senior officers but also entities where promoters or significant shareholders hold more than 10% equity. Boards are now required to maintain an updated register of related-party exposures, and any NBFC director or Key Managerial Personnel (KMP) with an interest in a related-party transaction must fully recuse themselves from the credit decision. The directions came into force on 1 April 2026.

The same logic applies to underwriting. If an MSME applicant’s revenue is substantially dependent on promoter-controlled entities, that’s a material fact for the credit decision, whether or not the borrower has disclosed it. Counterparty detection addresses the borrower-side equivalent of what the RBI now requires NBFCs to govern on their own lending side.

What the Analysis Shows in Practice

For an NBFC assessing a working capital application, counterparty detection as part of bank statement analysis produces a set of outputs that a manual review wouldn’t generate:

• A ranked list of all counterparties transacted with during the analysis period, by volume.
• Identification of counterparties appearing on both credit and debit sides, with amounts and dates.
• Transaction-level flagging of patterns that match circular or round-trip structures.
• A concentration breakdown showing what percentage of credits originate from how many distinct counterparties.

This doesn’t replace underwriter judgment. A high credit concentration might reflect a genuine anchor client rather than related-party inflation. But if a borrower can’t explain why 80% of their receipts come from two entities controlled by the same family, the credit decision changes. 

A Practical Limitation Worth Noting

Counterparty detection operates on the bank statements that are actually submitted. If a borrower deliberately withholds accounts where the circular transactions are running, the analysis is limited to what’s available.

This is why PDF forensics and full account declaration requirements matter alongside counterparty analysis. Cross-checking the submitted statements for coverage gaps, metadata consistency, and balance continuity reduces the window for selective submission. But the principle remains: counterparty detection is as thorough as the data behind it.

For lenders who need the strongest detection capability, requiring all active accounts to be submitted (or using Account Aggregator data fetched directly from the financial information network) significantly reduces this limitation.

How Precisa’s Counterparty Detection Works

Precisa runs counterparty detection across all uploaded bank accounts simultaneously. The platform identifies all counterparties across the full analysis period, flags entities appearing on both the credit and debit sides of statements, and shows concentration risk with transaction-level date and amount breakdowns.

The counterparty module works alongside Precisa’s inter-bank transfer detection, which identifies funds moving between multiple accounts held by the same entity or promoter group. Together, these two features give NBFC credit teams a layered view of related-party risk that transaction-level manual review cannot match.

Trusted by 1,000+ clients across 25+ countries, Precisa supports 1,200+ bank formats from 850+ banks and is available via API for teams that need the analysis embedded directly in a loan origination system. Account Aggregator integration is also available for lenders who prefer to fetch account data directly rather than relying on borrower-uploaded PDFs.

Try Precisa free | Talk to our team

Frequently Asked Questions

1. What is counterparty detection in bank statement analysis?

Counterparty detection identifies all entities a borrower has transacted with across submitted bank statements, maps the direction and volume of those flows, and flags circular patterns or concentrated receipts from a small number of related sources. It answers the question that manual review rarely asks: who is genuinely paying this borrower?

2. How are related-party flows different from normal business transactions?

The distinguishing characteristics are circularity and concentration. In a genuine business, money flows in from external customers and out to suppliers. In related-party rotation, the same funds return to the originating network through loans, payments, or intermediate entities. A borrower inflating revenue through related parties tends to show receipts concentrated in a small number of connected counterparties rather than dispersed across a real customer base.

3. Can counterparty detection catch circular transactions running across multiple bank accounts?

Yes, provided all relevant accounts are submitted. Precisa runs counterparty detection across all uploaded accounts simultaneously and identifies when the same entity appears across multiple accounts, or when transfers between them form a circular pattern. Accounts not submitted remain outside the detection scope.

Conlusion

Related-party fund inflation doesn’t show up as a red flag in a statement summary. It hides inside transactions that individually look ordinary. The question isn’t whether credit teams can identify these issues; it’s whether they can consistently analyse hundreds of applications each month at this level without automation. That’s the operational problem a bank statement analyser with counterparty detection solves. What happens at the credit decision depends on what the analysis actually found.

Precisa supports both PDF bank statement uploads and Account Aggregator integration. For lenders using Account Aggregator data, the counterparty detection, inter-bank transfer analysis, and all other analytical modules run on the fetched data in the same way they run on uploaded PDFs. This can improve detection reliability by reducing the scope for selective statement submission.

To see how Precisa works in real time, try it for free.