RBI Early Warning Signals: The Complete List, Explained in Plain Language

TL;DR

• RBI does not publish one fixed numbered list of Early Warning Signals. The July 2024 directions (RBI/2024-25/118) require each bank Risk Management Committee of the Board to approve its own indicators.
• The reference list below, the ~40 signals every bank framework descends from, comes from RBI May 2015 circular RBI/2014-15/590, grouped here under the 2024 directions four illustrative bases: account transactions, financial performance, market intelligence, borrower conduct.
• One or more indicators raise suspicion. That suspicion, examined, can lead to a Red Flagged Account. An alert is not a fraud finding. The bank gets natural-justice process before any fraud label.

Borrowers usually meet Early Warning Signals the wrong way round: a bank query arrives, and only then does anyone explain what the signal was. This page flips that order. Below is the complete RBI EWS reference list, all ~40 signals in five groups, with each signal translated into plain borrower language: what it looks like in your books, why your bank cares, and the practical fix you can make before it becomes an alert.

Read it as a self-audit, not a scare list. Most of these signals are ordinary business conduct seen through a bank analytical lens. The gap between clean and flagged is usually documentation, not honesty.

What are RBI early warning signals, exactly?

An Early Warning Signal is an indicator, quantitative or qualitative, that throws up suspicion of possible wrongdoing in a loan account. The July 2024 directions define the trigger rule plainly: a Red Flagged Account is one where suspicion of fraudulent activity is raised by the presence of one or more EWS indicators. One or more. That is the whole threshold. Signals cluster, and clusters carry weight.

Three facts matter most. First, the bank shall run a Board-approved EWS and RFA framework. "Shall" is direction language for mandatory on the bank. Second, the indicators themselves are approved by the Risk Management Committee of the Board. RBI does not hand banks a numbered list; it says the system may illustratively capture indicators based on four bases: transactional data of accounts, financial performance of borrowers, market intelligence, and conduct of borrowers. Third, an EWS alert is suspicion, not a finding. An alert shall be examined for whether the account needs red-flagging and fraud-angle investigation. Examination comes first. A fraud label needs a hearing, a show-cause notice, and not less than 21 days to reply.

What happens after a flag is a different guide. If you want the full sequence, read what happens after red-flagging and the EWS-to-forensic-audit workflow that the parent pillar maps end to end. The audit stage itself gets the full borrower-side treatment in our forensic audit in bank fraud cases.

Where does the EWS list actually come from?

Every "complete list" of EWS signals circulating online has the same ancestor. On 7 May 2015, RBI issued circular RBI/2014-15/590 titled "Some Early Warning signals which should alert the bank officials about some wrongdoings in the loan accounts which may turn out to be fraudulent." That circular is the source of the ~40-signal list below. It was superseded as an instrument when the July 2024 Master Directions (RBI/2024-25/118) replaced the old fraud framework and withdrew 36 earlier circulars, but its signal catalogue remains the industry reference canon. Every bank EWS engine descends from it.

A note on count honesty, because this is where most articles mislead you. The 2015 text, faithfully reproduced by TaxGuru and a CA-firm mirror, carries 39 signals. A law-firm note on the 2024 directions lists 41. Contemporary 2015 press reported 45. There is no canonical RBI count. The 2024 directions call their indicators "illustrative." Any page that asserts "RBI list of 42 signals" or "34 mandatory triggers" is quoting a miscount or inventing clause numbers. Treat the list below as the complete reference list, about forty signals, not as a numbered RBI schedule. The legal rule that matters is the 2024 one: your bank Risk Management Committee approves its own indicators.

The 2024 directions changed the architecture around that old list. Banks shall run a dedicated Data Analytics and Market Intelligence Unit. EWS shall cover quantitative and qualitative indicators. And Chapter 3.4 extended EWS to non-credit transactions: banks shall identify indicators, parameterise them, and monitor on a real-time basis, staying vigilant specifically on non-KYC-compliant and money-mule accounts and unusual digital-platform transactions. That is why Group E below exists. Nobody else publishing this list covers it.

What fund-movement signals do banks watch in your accounts?

This is the largest group, and the one that fires most often. The bank watches where money enters, leaves, and rests in your loan and current accounts. Fourteen signals. If you want the fund-diversion mechanics in depth, the companion piece money-trail analysis in financial fraud detection traces how investigators read these same patterns.

1. Default in payment to banks, sundry debtors, statutory bodies, and bouncing of high-value cheques. Your books: EMIs and interest paid late, vendor payments stretching, PF, ESI and GST dues piling up while you keep operating. Why the bank cares: unpaid statutory dues rank ahead of the bank in a failure. Cheque bounces are the earliest machine-readable distress. Fix: clear statutory arrears first. Never let an EMI or a large cheque bounce twice. One bounce is an event; a pattern is a signal.

2. Delay observed in payment of outstanding dues. Your books: penal interest and late-payment charges appearing as a regular line in your P&L. Why the bank cares: chronic lateness predicts default better than any single missed payment. Fix: put EMIs and interest on auto-debit. If cash flow is tight, ask for rescheduling before the delay, not after.

3. Funds coming from other banks to liquidate the outstanding loan amount, unless in the normal course. Your books: a loan closed by a lump-sum transfer from an unrelated bank account instead of business cash flow. Why the bank cares: it smells like evergreening through another lender or a round-trip. Fix: close loans from operating cash flow. If you refinance, document the new sanction and keep the paper trail clean.

4. Foreign bills remaining outstanding for a long time, with a tendency to remain overdue. Your books: export bills stuck unrealised in your receivables. Why the bank cares: overdue forex bills can hide fictitious exports or diverted realisations. Fix: follow up realisation within the FEMA window. Report genuine delays to the bank with buyer correspondence.

5. Merchanting trade where the import leg is not revealed to the bank. Your books: trade where goods never enter India but the financing does. Why the bank cares: merchanting trade is a classic trade-based money-laundering channel. Fix: disclose the full trade cycle, both legs, to the bank upfront. Do not finance merchanting through a working-capital line meant for domestic trade.

6. Frequent invocation of bank guarantees and devolvement of letters of credit. Your books: contingent liabilities suddenly becoming real debt. Why the bank cares: a guarantee being called means your counterparty no longer trusts you, or you engineered it. Fix: honour the underlying contracts so guarantees and LCs are never invoked. Explain any invocation to the bank the same week.

7. Funding of interest by sanctioning additional facilities. Your books: interest paid out of a fresh top-up loan instead of profits. Why the bank cares: interest paid from new borrowing is the textbook definition of a Ponzi structure. Fix: never roll interest into principal informally. If debt service is unviable, seek formal restructuring.

8. Floating front or associate companies by investing borrowed money. Your books: loan money landing in newly incorporated entities with common directors. Why the bank cares: diversion of funds, the single most investigated EWS. Fix: never route borrowed funds to group entities except for a disclosed, sanctioned purpose. Keep end-use certificates ready.

9. Significant increase in working capital borrowing as a percentage of turnover. Your books: cash-credit utilisation climbing toward the limit while sales stay flat. Why the bank cares: the gap between borrowing and sales is where diversion lives. Fix: keep utilisation in line with actual sales. Submit stock statements that tie to your GST filings.

10. Movement of an account from one bank to another. Your books: shifting your main operating account to a new bank. Why the bank cares: borrowers sometimes move to escape monitoring after signals fire. Fix: keep your primary operating account stable. If you switch lenders, carry the full track record and disclose it.

11. Frequent ad hoc sanctions. Your books: repeated temporary overdrafts and top-ups outside the sanctioned structure. Why the bank cares: ad hoc requests signal that the sanctioned limits do not match reality. Fix: get the limit structure right at renewal. Do not live on ad hocs.

12. Non-routing of sales proceeds through the lending or consortium bank. Your books: revenue credited to a different bank while the lending bank account goes quiet. Why the bank cares: the lender loses visibility of your cash flow, the first step in most diversion cases. Fix: route all operating sales through the lending or consortium account as your sanction terms require.

13. High-value RTGS payments to unrelated parties. Your books: large transfers to entities with no business relationship to you. Why the bank cares: unrelated-party transfers are the footprint of siphoning. Fix: keep payments to genuine vendors and employees. Document any large one-off transfer with the underlying invoice or agreement.

14. Heavy cash withdrawal in loan accounts. Your books: large cash withdrawals from cash credit or overdraft. Why the bank cares: cash leaves no trail, and diversion prefers no trail. Fix: run business payments through banking channels. Keep cash drawings small, explained, and consistent with your business type.

What do banks read in your financial statements?

Thirteen signals. The bank checks whether your audited numbers tell the same story as your bank account. Mismatches between what you file and what you do are the cheapest analytical red flag a credit officer has. For how the bank reads these same numbers at appraisal time, see how banks build a Credit Appraisal Memorandum.

15. Significant movements in inventory disproportionate to turnover. Your books: stock piling up while sales do not grow, or stock vanishing without matching sales. Why the bank cares: inflated stock inflates drawing power. It is borrowed money against phantom goods. Fix: submit stock statements that reconcile with your books and GST returns, every month.

16. Significant movements in receivables disproportionate to turnover, or ageing receivables. Your books: debtors growing much faster than sales, or old dues nobody is collecting. Why the bank cares: uncollectible receivables are often fictitious sales. Fix: age your receivables monthly. Provide for or write off dead debtors instead of carrying them.

17. Disproportionate increase in other current assets. Your books: a swelling "other current assets" line nobody can explain. Why the bank cares: it is the balance sheet junk drawer. Advances to related parties hide here. Fix: break the line down in your notes. Clear unexplained advances.

18. Increase in fixed assets without a matching increase in long-term sources, when a project is implemented. Your books: new plant and machinery funded by short-term borrowing. Why the bank cares: short-term money in long-term assets means end-use diversion and a future repayment crisis. Fix: fund capex only from term loans, equity, or internal accruals. Never from cash credit.

19. Increase in borrowings despite huge cash and cash equivalents. Your books: crores sitting in FDs while you draw more working capital. Why the bank cares: nobody rationally pays 12 percent on a loan while holding cash, unless the cash is not really theirs. Fix: use surplus cash before drawing fresh limits. Explain any genuine reason, margin money or earmarked funds, in writing.

20. Claims not acknowledged as debt running high. Your books: large disputed claims sitting in contingent liabilities. Why the bank cares: today contingent claim is tomorrow decree against your cash flow. Fix: disclose, quantify, and where possible settle or provision. Do not let the footnote grow quietly.

21. Substantial increase in unbilled revenue year after year. Your books: revenue booked without raising invoices or collecting cash. Why the bank cares: unbilled revenue that never converts is the classic receivables bubble before a fraud surfaces. Fix: bill on milestone completion. Convert unbilled revenue to receivables and then to cash on a visible cycle.

22. Substantial related-party transactions. Your books: heavy buying, selling, or lending with group companies. Why the bank cares: related-party pricing is the easiest way to move profits, or losses, across entities. Fix: keep related-party deals at arm length, documented, and disclosed. Be ready with your pricing logic.

23. Large number of transactions with inter-connected companies and large outstanding from them. Your books: constant two-way flows with sister concerns and big uncleared balances. Why the bank cares: circular transactions between connected entities simulate turnover without real business. Fix: settle inter-company balances periodically. Do not let them compound.

24. Material discrepancies in the annual report. Your books: numbers in the annual report that do not match the audited financials or your bank submissions. Why the bank cares: if the public document and the bank document disagree, one of them is managed. Fix: give the bank exactly what you file with the ROC. Never maintain two versions of the truth.

25. Significant inconsistencies within the annual report, between its sections. Your books: the directors report, MD&A, and financials telling different stories. Why the bank cares: internal inconsistency is the cheapest analytical red flag a credit officer has. Fix: have your CA read the full annual report as one document before it goes out.

26. Poor disclosure of materially adverse information, with no qualification by statutory auditors. Your books: a clean audit report while the business is visibly deteriorating. Why the bank cares: a clean opinion next to bad account conduct suggests the audit is not seeing, or not saying. Fix: disclose adverse developments, lost contracts, litigation, covenant breaches, proactively. A qualified audit with honesty beats a clean one with surprises.

27. Frequent change in accounting period or accounting policies. Your books: year-ends shifting, depreciation or revenue-recognition policies changing often. Why the bank cares: moving the goalposts makes year-on-year comparison, the bank main analytical tool, impossible. Fix: keep policies stable. If a change is genuinely needed, disclose it and restate comparatives.

Which project, security and documentation signals trigger alerts?

Thirteen signals. The bank checks whether the project, the collateral, and your paperwork are what you said they were. For how banks physically verify your stock and drawing power, read what a bank stock audit checks and how drawing power is calculated.

28. Frequent change in the scope of the project. Your books: the sanctioned project keeps morphing: new machinery, new location, new product line. Why the bank cares: shifting scope breaks the link between disbursement and end use. Fix: execute the sanctioned project as appraised. Get formal approval before any material change.

29. Costing of the project in wide variance with the standard cost of installation. Your books: your project costs far more, or far less, than industry benchmarks. Why the bank cares: inflated project cost is the oldest route to skim disbursements. Fix: keep independent cost estimates and actual invoices aligned. Explain variances with evidence.

30. Under-insured or over-insured inventory. Your books: insurance cover that does not match declared stock. Why the bank cares: under-insurance suggests the stock is not really there. Over-insurance suggests a planned claim. Fix: insure stock for its actual book value and renew on time.

31. Invoices devoid of TAN and other details. Your books: purchase invoices missing tax numbers and proper particulars. Why the bank cares: incomplete invoices are the fingerprint of shell vendors and accommodation entries. Fix: buy only against proper GST-compliant invoices. Keep the trail verifiable.

32. Dispute on the title of collateral securities. Your books: someone else claims your mortgaged property. Why the bank cares: disputed collateral has no realisable value. The bank security evaporates. Fix: get a clean title search before mortgaging. Disclose any litigation on the property upfront.

33. Same collateral charged to several lenders. Your books: one property mortgaged to two banks. Why the bank cares: double-charged security means at least one lender is unsecured without knowing it. Fix: never create a second charge without the first lender written NOC. Keep charge filings with the ROC current.

34. Concealment of vital documents such as the master agreement or insurance coverage. Your books: key contracts or policies you "cannot locate" when the bank asks. Why the bank cares: hidden documents usually hide hidden obligations. Fix: maintain a complete credit file. Hand over whatever the sanction terms require, on time.

35. Critical issues highlighted in the stock audit report. Your books: the stock auditor qualifications and discrepancies. Why the bank cares: the stock audit is the bank physical check on your drawing power. Flags here go straight to the credit file. Fix: act on every stock-audit observation before the next inspection. Do not repeat qualifications.

36. Request to postpone godown inspection for flimsy reasons. Your books: the bank inspector keeps getting turned away. Why the bank cares: evaded inspection plus inventory signals is the classic diversion setup. Fix: never delay a scheduled inspection. Keep stock accessible and records ready.

37. Liabilities appearing in the ROC search report but not in the annual report. Your books: MCA filings showing borrowings your annual report does not mention. Why the bank cares: the ROC is public. Hidden borrowings surface here first, and concealment itself is the signal. Fix: reconcile your ROC filings with your books quarterly. Disclose every charge.

38. Financing the unit far away from the branch. Your books: your factory is three states from your lending branch. Why the bank cares: distance weakens monitoring. Inspections, stock audits, and local intelligence all degrade. Fix: bank with a branch near your operations. If that is impossible, expect, and cooperate with, more intensive monitoring.

39. Onerous clauses in BG, LC, or standby LC issuance. Your books: guarantee or LC terms heavily skewed against you. Why the bank cares: onerous trade terms can indicate the underlying transaction is not genuine. Fix: negotiate clean, standard trade documentation. Do not accept clauses you cannot explain.

40. Non-production of original bills for verification upon request. Your books: originals "with the accountant" every time the bank asks. Why the bank cares: copies can be manufactured. Originals anchor the transaction. Fix: keep original purchase and sale documents filed and producible on demand.

What governance and market-intelligence signals matter?

Four signals. The bank watches who runs the company and what the outside world says about it.

41. Raid by income tax, sales tax, or GST officials. Your books: a search or survey operation at your premises. Why the bank cares: tax raids corroborate fund-flow anomalies and often precede bank action. Fix: you cannot "fix" a raid. Full cooperation, clean records, and prompt disclosure to the bank limit the damage.

42. Reduction in promoter or director stake, or increase in encumbered (pledged) shares. Your books: promoters selling down or pledging their holding. Why the bank cares: promoters cashing out while the bank is exposed signals they know something the bank does not. Fix: disclose stake changes and pledges. Do not pledge promoter shares to raise parallel personal funding against the company prospects.

43. Resignation of key personnel and frequent changes in management. Your books: CFO, auditors, or compliance officers exiting in quick succession. Why the bank cares: insiders leave before bad news breaks. Attrition at the top is the market earliest warning. Fix: stabilise key roles. If a change is genuine, communicate the reason to the bank proactively.

44. Frequent request for general-purpose loans. Your books: repeated asks for unsecured, purpose-free funding. Why the bank cares: general-purpose borrowing with no end use is the hardest to monitor and the easiest to divert. Fix: borrow against specific, verifiable purposes. Keep general-purpose asks rare and documented.

What is new in 2024 and 2026: the non-credit signals

The old list was written for credit accounts. The July 2024 directions added a new group that no ranker publishing this list covers. Chapter 3.4 says banks shall develop EWS for other banking and non-credit transactions: identify suitable indicators, parameterise them, and monitor on a real-time basis.

45. Money-mule and non-KYC-compliant accounts under watch. The directions require banks to stay vigilant on non-KYC-compliant and money-mule accounts and contain misuse of the banking channel. Your books: your business accounts receive or pass through third-party funds you cannot explain. Why the bank cares: mule networks move illicit money through ordinary current accounts. Fix: if funds pass through your account that are not yours, document the agency relationship in writing. Expect scrutiny even with zero credit exposure.

46. Digital-platform and application transaction monitoring. The Data Analytics and Market Intelligence unit must extensively monitor transactions through digital platforms and apps for unusual patterns. Your books: UPI and bulk-transfer patterns inconsistent with your declared business. Why the bank cares: machine-flagged, not noticed by your relationship manager. Fix: keep digital transaction behaviour consistent with your stated business profile. Sudden pattern breaks invite queries.

47. Real-time, or minimum-lag, transaction monitoring. Banks must design EWS systems so transaction monitoring for fraud prevention and detection runs on a real-time basis. Your books: the window between a suspicious transaction and a bank query has collapsed from months to near-real-time. Fix: assume the bank sees it today, not at renewal. Explain first, when asked, with documents ready.

48. Data Analytics and Market Intelligence units as a standing capability. Every bank shall run one. Your books: EWS is no longer your branch manager judgment call. It is a system comparing your account against patterns continuously. Fix: treat every filing you submit, GST, ROC, stock statements, as one input to one analytical engine. Consistency across filings is the only safe posture.

What happens when signals cluster together?

One signal is an alert. Signals from two or more groups, say heavy cash withdrawals (Group A) plus ageing receivables (Group B) plus a promoter stake sale (Group D), are the strongest predictor of trouble a bank analytical desk has. That is why the direction defines a Red Flagged Account on one or more indicators: clustering is the trigger, not a single event. An EWS alert shall be examined within a TAT the Risk Management Committee of the Board prescribes, preferably not more than 30 days. "Preferably" is guidance, not a borrower right. If the account meets the CRILC reporting threshold and gets red-flagged, the bank shall report it to RBI within seven days. The thresholds your lender cites for monitoring come from bank policy and CRILC practice, not from the direction text, so ask which paper each number comes from.

The full sequence, EWS alert to RFA to fraud-angle investigation to the fraud-or-clear decision, lives in the EWS pillar workflow and the RFA playbook. The direction that created this architecture is decoded in the RBI fraud-risk directions decoder.

EWS vs SMA vs wilful defaulter vs fraud: what is the difference?

Borrowers confuse four different labels. They sit in different frameworks, with different consequences. Here is the map.

The confusion to avoid: an EWS alert feels like an accusation but legally it is only the start of an examination. SMA is a calendar, not a suspicion. Wilful default and fraud are findings that follow a defined process with hearings. Signals are cheapest to fix at the alert stage, before any finding exists.

How can you self-scan for EWS before your bank does?

The same three reconciliation checks run inside every bank analytics desk. Run them yourself first, once a quarter.

Check one: stock statement vs books vs GST returns. Take the stock figure you submitted to the bank, the stock in your signed books, and the stock implied by your GST filings. If the three disagree beyond your own tolerance, your drawing power rests on a mismatch, and that mismatch is exactly what Group A and Group B signals describe.

Check two: bank credits vs reported turnover. Total the credits in your operating account for the quarter and compare with the turnover you reported to the bank. A wide gap means either revenue routed elsewhere (Group A signal 12) or turnover overstated to justify limits.

Check three: ROC and MCA filings vs annual report vs bank submissions. The liabilities in your ROC search report, the borrowings in your annual report, and the debt you declared to the bank must be one number. Group C signal 37 exists because they often are not.

The EWS Self-Scan Workbook automates this: all 48 signals with Clean / Watch / Fix now status dropdowns, the three reconciliation checks with auto-flags against your tolerance, and a score sheet with one red rule. Signals in three or more groups, or six or more "Fix now" items, is red. Run it quarterly, before your bank runs its own reading of your conduct. For the matching statement-level companion, see what credit officers look for in your bank statement.

Sources

• RBI Master Directions on Fraud Risk Management in Commercial Banks (including RRBs) and AIFIs: RBI/2024-25/118, DOS.CO.FMG.SEC.No.5/23.04.001/2024-25, 15 July 2024. Primary source for the EWS and RFA framework, Chapter III wording, TAT, CRILC reporting and natural-justice timelines.
• TaxGuru: Early Warning Signals and Red Flagged Accounts: verbatim reproduction of RBI circular RBI/2014-15/590 (DBS.CO.CFMC.BC.No.007/23.04.001/2014-15), 7 May 2015, the source of the reference signal list used in this guide.

Rupee thresholds for monitoring or reporting that lenders cite in practice come from bank policy and CRILC practice unless a direction paragraph states them. This article states that limit wherever a threshold appears.

Frequently Asked Questions

Last updated: October 2026. Direction wording is from the 15 July 2024 instruments cited above. Your sanction letter and your bank fraud policy decide your file.