Grab your tea, because this is a topic nobody likes to talk about on the floor, and a team leader who has never thought about it is exposed. Fraud by staff inside processes that touch money (refunds, credits, collections, claims, account changes) is a real risk in any BPO. The good news is that the ideas for preventing it are not complicated.
Why decent people do it
A well-known model, the fraud triangle, comes from the criminologist Donald Cressey. It says three things usually come together: pressure, opportunity and rationalisation. Pressure is a personal need, like debt, a family medical bill or a lifestyle beyond the salary. Opportunity is a gap in controls that lets the act happen and go unnoticed. Rationalisation is the story the person tells themselves: “the company earns crores, this is small”, or “I am owed this after what they did with my appraisal”.
You cannot control the first or the third corner very much. You can shrink the second. That is the whole practical lesson: do not try to guess who is dishonest; design the process so that honesty is the easy and only path.
What it looks like in practice
Some patterns that recur in processes handling money or customer accounts:
- Refunds or credits issued to an account or wallet linked to the agent’s own contacts.
- Changing a customer’s registered mobile number or bank details, then moving money out.
- Collections agents recording a payment as received and pocketing the cash, or the reverse, waiving charges for a favour.
- Splitting a transaction into pieces just under an approval limit.
- Two staff colluding, one as maker and one as checker, which defeats the very control meant to stop it.
Prevention: close the opportunity
Maker-checker separation is the foundation: no single person starts and approves a money movement. Approval limits scale with the amount. System permissions follow job role, so an agent who handles queries cannot also edit bank details. Sensitive changes trigger a notification to the customer on the registered number, and changes to that number itself get a cooling-off period before high-value actions. Rotate duties where you can, and enforce mandatory leave, because many schemes depend on the same person being present every day to keep the books tidy.
Background verification at hiring and clear written rules, signed and explained, matter too. A rule people never heard of is hard to enforce.
Detection: compare people with each other
Prevention never closes every gap, so you also look. The cheapest detection method is a comparison against peers. Take an illustrative refund desk in Bhubaneswar with 25 agents who issued 80 refunds last month. The average is 80 / 25 = 3.2 per agent. One agent, Mohan, issued 19. That is 19 / 80, about 24 per cent of all refunds from 4 per cent of the staff.
That number proves nothing. Mohan may sit on the escalation line, where refunds are naturally more frequent. The data only tells you where to look. The next questions are ordinary ones: what do the customers’ cases show, are the refund destinations varied or repeated, is there a pattern of timing, such as late evening or just before month-end, and do the amounts cluster just below an approval limit?
Other useful reports: the same destination account receiving credits from different customer cases; many address or mobile changes followed by a withdrawal within hours; transactions at unusual times; accounts accessed by an agent with no ticket logged against them; and sudden changes in someone’s behaviour, like reluctance to take leave. These are red flags, not verdicts.
When you suspect something
Do not confront the person yourself, and do not discuss it with the team. Preserve the evidence (logs, tickets, call recordings), restrict the access if policy allows it, and report to the people responsible: your compliance or risk team, HR and, where the client’s data is involved, the client as per contract. Investigations have legal consequences in India, including possible criminal complaints, so they need proper handling and documentation. A team leader’s hunch, acted on loudly, can destroy both the case and an innocent colleague’s reputation.
A culture point
Staff must have a safe way to raise concerns, such as a whistleblower line that works and is not routed to the very manager in question. Many frauds are discovered by a colleague who noticed something odd. If raising it costs that colleague their peace, they stay silent. Also, fair pay, honest appraisals and visible consequences for everyone, including senior people, reduce the “rationalisation” corner more than any poster does.
Keep one balance in mind. Controls cost time, and every extra approval slows a customer’s refund. The right level depends on the amounts at risk. A ₹200 goodwill credit and a ₹2 lakh settlement should not pass through the same checks.
Figures and names in the examples are illustrative.
Leave a Reply