How to Find Related-Party Transactions Hiding in a Client's Bank Statement

Why related parties hide as ordinary rows

A bank statement records movement, not relationship. When a director draws Rs 3,00,000 from the company account by IMPS, the row shows the amount, the mode and a name. It does not say director. When rent goes to the proprietor's mother every month, the narration carries her name, not the word relative. The relationship that triggers disclosure is knowledge you hold about the client, so a related-party flow survives a straight top-to-bottom read of the statement.

The second reason is arrangement. A statement is date-wise. A single sister concern that received fourteen transfers across the year shows up as fourteen scattered rows, each unremarkable on its own. Review fatigue does the rest: by the time you reach the payment in November you have long forgotten the one in April. The pattern only becomes visible when you stop reading date-wise and start reading party-wise.

One honest framing before the method. This is not primarily about catching fraud. Most related-party flows are perfectly legitimate: genuine rent, real salary, an ordinary inter-company loan. The audit obligation is disclosure and compliance, not suspicion. Your job is to make sure nothing that should have been disclosed, approved or reported quietly passed through as an ordinary payment.

Build the related-party universe before you open the statement

You cannot find a related party you have not defined. The most common mistake is to open the statement first and hope the names jump out. Reverse the order. Build the list of related parties, then read the statement against it.

Who belongs on that list depends on the framework you are reporting under. AS 18 uses a specific and deliberately limited set of relationships:

For the Companies Act layer the net is wider. Pull the related parties under section 2(76), the register of contracts and arrangements in which directors are interested maintained under section 189, and the relatives list under section 2(77). Cross-reference the client's directorships by DIN, the shareholding pattern, the latest MGT-7, and the board's own section 188 disclosures. For a proprietor or a firm where AS 18 may not apply, ask directly: which family members are on the payroll or receive rent, what other businesses does the family run, and in which companies do the proprietor or partners hold shares or a directorship.

Keep the output as a working sheet: each related party with every alias you can anticipate, the legal name, the common name, the UPI handle, and the name of the other firm. That alias sheet is exactly what you will match the party ledger against.

• Holding, subsidiary and fellow-subsidiary companies, associates and joint ventures.
• Key management personnel: the persons with authority and responsibility for planning, directing and controlling the enterprise, typically the directors and equivalent officers.
• Relatives of KMP as AS 18 defines them, a narrow list: the spouse, son, daughter, brother, sister, father and mother who may be expected to influence, or be influenced by, that individual.
• Enterprises over which any KMP or a relative has control or significant influence, which is the classic sister concern or family firm.

Turn the statement party-wise, then match

Now the mechanical work: collapse the date-wise statement into a counterparty view. For each party you want the transaction count, total debits, total credits and net position for the year. That single rollup is what turns fourteen scattered rows into one line that reads, this name received Rs X across fourteen transfers. Placed next to your related-party sheet, the matches announce themselves.

The obstacle is that the counterparty name is buried inside narration formats that differ by bank, and the same party wears different spellings. HDFC hyphen-delimits its narration segments (see the HDFC statement format). ICICI leads with coded prefixes such as MMT/ and BIL/ (ICICI format). SBI wraps transfers in TO TRANSFER and BY TRANSFER strings (SBI format). A single director can surface as RAJESH KUMAR on an RTGS, rajesh.k@okhdfc on a UPI credit and RAJESHKUMAR on an IMPS, three rows that must roll into one party before the pattern is visible.

You can do this by hand in Excel with a helper column, a cleaned name, and a pivot, and for a short statement that is entirely reasonable. Across a full year and several accounts it becomes slow and error-prone, which is where an analyser earns its place. Greenote Lite takes the Excel or CSV export, resolves those narration variants into one counterparty, and returns a party-wise ledger with every transaction already categorised, so the rollup you would otherwise have built by hand is your starting point rather than your evening's work.

However you build it, then match. Run your alias sheet against the party ledger and tag every hit as a candidate related party. Do not stop at exact matches. Scan for shared surnames with the promoter, individual names sitting among business-to-business payments, and any counterparty whose name echoes a group entity.

The tells: what a related-party flow looks like in the rows

Once the statement is party-wise, certain shapes recur. None is proof on its own. Each is a prompt to ask the client for the relationship and the supporting paperwork.

Then cross-check the candidates against sources outside the statement. The AIS and SFT data, the TDS trail under the section 194 series (rent, professional fees and interest paid to related parties all leave one), and the client's own books RPT schedule should reconcile to what the bank actually did. A related-party payment sitting in the bank with no matching entry in the related-party note is precisely the gap the audit exists to close.

• Round-sum RTGS or NEFT, Rs 5,00,000 or Rs 10,00,000 with no invoice rhythm, especially to or from an individual: often a loan, a capital movement or an advance.
• Recurring transfers to the same individual on a monthly cadence: rent to a family member, salary to a relative, or interest on a family loan.
• Inter-company movement that behaves like a running current account: frequent transfers back and forth with one entity, netting close to zero over the year.
• Personal names among business payments: a proprietor's household name drawing funds from the business account, a hallmark of drawings or of a section 2(22)(e) situation in a company.
• Cash withdrawals clustered around transfers to a director or partner, worth reading alongside the 269SS and 269T limits.
• Loan-flavoured narrations: the words LOAN or LN, or a repayment cadence that looks like an EMI paid to a related lender rather than to a bank.

From flagged flows to a disclosure and compliance checklist

A tagged party ledger is only working-paper raw material. Convert each confirmed related party into the specific questions the frameworks ask, and run this checklist per party:

Not every line applies to every client. AS 18 and CARO are company-side obligations; a proprietorship under section 44AB may trigger only the tax clauses. Specified domestic transfer pricing under section 92BA applies to a narrow set of specified domestic transactions and should be checked only where the client actually falls within it. Verify every threshold and the applicability of each provision against the bare Act for the assessment year in front of you, and treat this checklist as a prompt, not a substitute for reading the section.

1. AS 18 disclosure: is the relationship, and the nature, volume and outstanding amount of the transactions, captured in the notes? Where control exists, the relationship is disclosed even if there were no transactions in the year.
2. Section 188 and CARO: for companies, are the transactions within section 188 (board or member approval where required) and section 177 (audit committee), so that CARO clause 3(xiii) is satisfied, that is, compliant and disclosed as the applicable accounting standards require?
3. CARO clause 3(iii) and section 189: are loans or advances granted to related parties recorded in the register of interested contracts, with their terms captured for the CARO reporting on loans, advances, guarantees and security?
4. Section 40A(2)(b) and Form 3CD clause 23: for tax audit, are payments to specified persons listed, and is any part of them excessive or unreasonable and therefore exposed to disallowance?
5. Sections 269SS, 269T and Form 3CD clause 31: were loans or deposits from or to related parties accepted or repaid otherwise than by account payee instrument beyond the Rs 20,000 threshold?
6. Section 2(22)(e) deemed dividend: did a closely held company advance a loan to a shareholder holding 10% or more of the voting power, or to a concern in which such a shareholder has a substantial interest? If so, it may be deemed dividend to the extent of the company's accumulated profits.

Working papers, and where a tool earns its place

Whatever you flag, leave a trail. For each related party, keep the party ledger extract, the basis on which you concluded the relationship, the alias mapping you used, and the disclosure conclusion. Keep an honest suspense line too: counterparties you could not attribute belong under a clearly labelled Suspense or Unknown head, not force-fitted to a name to make the sheet look complete. A reviewer, or you a year from now, should be able to trace how a string in the narration became a disclosure in the notes.

The judgement in all of this stays yours. A tool cannot know that RAJESH KUMAR is the managing director's brother. What it can do is take away the sorting. Greenote Lite reads an Excel or CSV bank statement, resolves the narration variants into one party, rolls the year into a party-wise ledger, categorises every transaction, and produces a category summary and an ITR summary with AIS and SFT flags: the tedious layer that sits between the raw statement and your related-party review. The statement is processed in memory and deleted the moment the report is ready, so the client's data does not linger on anyone's server. The first statement is free for the first set of transactions, and after that it is pay per statement with no subscription, which is enough to run one real client through it and judge, on your own narrations, whether the party ledger holds up.