A person constructing fabricated bank statement transaction amounts manually tends to choose psychologically round figures, producing a higher concentration of amounts ending in multiple zeros than genuine spending data would generate. Standard transaction review does not measure this distribution.
Compute the proportion of transaction amounts that end in three or more zeros across the full statement. Exclude ATM withdrawal transactions from this calculation — Indian ATMs dispense in ₹100/₹200/₹500 multiples, making round-number ATM transactions structurally normal. If the adjusted concentration exceeds a calibrated threshold for the account type, flag for human review.
ATM withdrawal exclusion: identify transactions with ATM/ATW/cash withdrawal keywords in the description. Adjust baseline threshold for accounts where informal business or contractor payments explain elevated round-number rates. Apply check separately to credits and debits to detect selective fabrication of income entries.
Round-number concentration percentage (ATM-adjusted), classification (within normal range / elevated / high — review), and a breakout showing round-number rate for credits versus debits separately, presented in the fraud signals section of the analysis report.
When someone sits down to fabricate a bank statement, the transaction amounts they write are revealing not because any individual amount looks wrong, but because the set of amounts shows a pattern that real spending does not produce. Round-number clustering is the observation that fabricated statements contain a disproportionate share of amounts ending in three or more zeros — because those are the amounts people reach for when constructing numbers by hand.
Round number transaction fraud detection is a straightforward heuristic, but one that requires careful calibration for it to produce meaningful signals rather than false positives.
What Round-Number Clustering Is
In genuine bank statements from active accounts, transaction amounts are determined by the independent events of daily financial life: utility bills with odd rupee amounts, grocery totals, fuel fills, vendor invoices, EMI deductions. These amounts distribute across the full range and naturally produce some round numbers but not a concentration of them.
Fabricated statements show a different pattern. A person constructing amounts with the goal of looking realistic tends to use round figures — ₹10,000, ₹25,000, ₹50,000, ₹1,00,000 — at a rate that organic spending does not support. The mental effort required to consistently generate non-round amounts across hundreds of rows is too high, and most fabricated statements end up with 40 to 70% of transactions ending in three or more zeros.
The check counts what proportion of transaction amounts in the statement fall into the round-number category, then compares that proportion to a calibrated threshold for the account type.
The ATM Withdrawal Exception
The most important calibration in round-number clustering analysis is ATM withdrawals. Indian ATMs dispense currency in denominations of ₹100, ₹200, and ₹500 — which means every ATM withdrawal is inherently a multiple of ₹100. An account holder who withdraws ₹5,000 from an ATM is not fabricating that amount; they are constrained by the machine’s denominations.
An account where a significant share of transactions are ATM withdrawals will legitimately show a high proportion of round-number amounts. Applying the same threshold to that account as to one without ATM use would produce a false fraud signal.
Automated round-number clustering checks identify ATM withdrawals from the transaction description — keywords like ATM, ATW, CASH WITHDRAWAL, and ATM WDL — and exclude them from the concentration calculation. The resulting percentage is the round-number rate for non-ATM transactions, which is the meaningful comparison.
Concentration Reference Table
| Round-Number Rate (ATM-Adjusted) | Risk Interpretation | Recommended Follow-Up |
|---|---|---|
| Below 20% | Normal — consistent with organic spending | No action on this signal alone |
| 20% to 35% | Normal with some informal payment activity | Note; consider alongside other signals |
| 35% to 50% | Elevated — warrants context check | Review against account type and industry; check for other fraud signals |
| 50% to 65% | High — strong review trigger | Examine individual round transactions; request supporting documents |
| Above 65% | Very high — significant fabrication signal | Prioritise for document verification; treat as high-risk file |
India-Specific Context
Indian MSME accounts present the most significant calibration challenge. Informal business payments — subcontractor wages, daily cash purchases, supplier settlements — are often made in round figures because negotiated business amounts in informal markets tend to be round. A proprietorship account receiving payments from small counterparties may legitimately have 30 to 40% round-number transactions, particularly if the business is cash-intensive or operates in sectors like construction, retail, or trade.
Human reviewer calibration is necessary here: an account in construction or retail with 35% round-number transactions tells a different story than a salaried professional account with the same rate. Round-number clustering is most diagnostic when combined with counterparty spread analysis and sequence pattern checks — the combination of signals produces a more reliable picture than any single heuristic applied alone.
The Institute of Chartered Accountants of India includes round-number distribution review as a fraud risk indicator in its forensic accounting guidance — a heuristic that forensic CAs apply manually when examining suspected fabricated financial documents.
The bank statement analysis platform computes the ATM-adjusted round-number concentration on every statement and presents it as one signal in a consolidated fraud review rather than a standalone decision point. The bank statement fraud detection capability combines this check with digit-pattern analysis, sequence pattern review, and balance chain verification — so credit teams see the full picture before deciding whether to request additional documentation.