Fighting Corruption
Forty Ways Officials Steal
Kautilya catalogued 40 ways officials embezzle. Understanding corruption is the first step to preventing it.
The Invisible Path

Chandragupta sat across from Kautilya in the torchlit chamber, studying a scroll. The young king's face showed frustration.
"This granary superintendent has served for ten years without any accusation. Yet the treasury reports shortfalls. How can he be stealing if no one sees it?"
Kautilya smiled thinly. "My lord, I could sooner trace the path of birds through the sky, or fish through water, than track the ways officials take wealth."
"Catvāriṃśadbhiḥ prakāraiḥ amātyāḥ kośa-hāriṇaḥ" - Officials steal from the treasury by forty methods.
"Forty?" Chandragupta looked startled.
"I have catalogued them. Not to teach corruption, but to detect it. You cannot fight an enemy you don't understand."
Why Catalogue Corruption?
Kautilya's approach seems counterintuitive. Isn't listing embezzlement methods a handbook for thieves?
The logic is investigative. A king who doesn't understand corruption techniques can't detect them. But one who knows all forty methods can audit for each one.
The catalogue also deters. When officials know the king understands all techniques and checks for them, the perceived risk increases. The existence of the list signals: "I know how this works. Don't try it."
The Methods
Kautilya grouped corruption techniques:
Record Manipulation:
- Under-recording revenue (collecting 1500, recording 1000)
- Over-recording expenses (paying 300, recording 500)
- Ghost employees (salaries for people who don't exist)
- Delayed recording (creating windows for theft)
- Destroying records ("losing" inconvenient documents)
Quality Substitution:
- Mixing inferior materials (diluting ghee with oil)
- Substituting worn items (new purchased, old delivered)
- Reducing quantity (delivering 90% of payment)
- Degrading specifications (cheaper materials, premium billing)
Collusion:
- Bid rigging (inflated contracts with kickbacks)
- Inspection fraud (bribes to certify substandard goods)
- Revenue sharing (multiple officials each taking cuts)
- Mutual protection (officials agreeing not to audit each other)
Authority Exploitation:
- Extortion (bribes to provide required services)
- Preferential treatment (payments for priority)
- False accusations (threats unless paid)
- Confiscation schemes (seizing property on false pretenses)
Resource Conversion:
- Using state labor for private projects
- Appropriating public materials
- Operating government equipment for personal profit
Detection Methods
Knowing techniques enables specific detection:

Cross-checking: Compare what different departments record for the same transaction. Discrepancies reveal error or fraud.
Physical verification: Don't just accept records. Count actual grain, inspect actual goods, verify employees exist.
Pattern analysis: Look for anomalies. Lifestyle exceeding salary. Suppliers who always win bids at similar prices.
Informant networks: People tasked with observing officials and reporting suspicious behavior.

Surprise audits: Announced inspections can be prepared for. Unannounced ones catch people in the act.
Prevention Through Design
Better than detection is prevention through system design:
Separation of functions: The person authorizing payments shouldn't make them. The person receiving goods shouldn't be the only inspector.
Rotation of assignments: Don't leave officials in lucrative posts long enough to build corruption networks.
Transparency: Public posting of prices, budgets, and transactions makes fraud harder to conceal.
Adequate compensation: Officials paid well enough to live comfortably are less tempted by small-scale theft.
The Trust Paradox
Kautilya recognized a fundamental problem: you need officials to check officials. Who watches the watchers?
His solution: multiple overlapping systems.
- Independent audit: Separate officials with no operational responsibilities
- Mutual oversight: Structures where officials naturally check each other
- Intelligence penetration: Secret agents among officials, reporting directly to the king
- Public reporting: Channels for citizens to report misconduct
- Personal royal attention: The king reviewing anomalies himself
No single mechanism suffices. Comprehensive anti-corruption requires layered defenses.
Modern Applications
Jeff Skilling at Enron used ancient techniques: record manipulation, phantom entities, collusion with auditors. Twenty-three centuries after Kautilya, the patterns remain.
Modern anti-corruption follows the same principles:
- Separation of duties
- Surprise audits
- Whistleblower systems
- Independent oversight
- Transparency requirements
The technologies change. The human nature doesn't.
Kautilya's approach remains valid: understand how corruption works, design systems that assume it will be attempted, and make detection probable enough that the risk exceeds the reward.
The forty methods aren't just historical curiosities. They're recognition that fighting corruption requires understanding corruption - not moralizing about it.
Fraud examination - studying corruption techniques to enable detection.
Modern fraud examiners study embezzlement methods exactly as Kautilya did. The Association of Certified Fraud Examiners trains investigators in patterns that echo the forty methods.
Kautilya provides a comprehensive framework, not just case studies. His systematic categorization enables systematic checking.
Enron's fraud used multiple ancient patterns: record manipulation, phantom entities, collusion with auditors. Those who understood the patterns caught the fraud; those who didn't missed it.
Trust but verify - or better, verify regardless of trust.
Reagan's famous 'trust but verify' echoes this. Modern internal controls don't assume virtue - they separate functions so no single person can steal without detection.
Verses
चत्वारिंशद्भिः प्रकारैः अमात्याः कोशहारिणः
catvāriṃśadbhiḥ prakāraiḥ amātyāḥ kośa-hāriṇaḥ
Officials steal from the treasury by forty methods.
Kautilya's enumeration isn't exhaustive but representative. By cataloguing methods, he enables systematic detection.
Book 2, Chapter 8, Verse 18 (R.P. Kangle)
अगोचरः अर्थहारः अमात्यानाम्
a-gocaraḥ artha-hāraḥ amātyānām
The taking of wealth by officials is imperceptible.
Corruption is designed to be invisible - like the path of birds in the sky. Officials structure their theft to avoid detection.
Book 2, Chapter 9, Verse 1 (R. Shamasastry)
लेखनीयम् अलेखयेत्, लिखितं वा न लेखयेत्
lekhanīyam alekhayed, likhitaṃ vā na lekhayed
He does not record what should be recorded, or does not record properly what is recorded.
Record manipulation is the most fundamental form of embezzlement. If records don't reflect reality, all subsequent oversight fails.
Book 2, Chapter 8, Verse 3-4 (L.N. Rangarajan)
Case studies
Enron: Ancient Patterns in Modern Guise
Enron Corporation, America's seventh-largest company, collapsed in 2001 after massive accounting fraud. Executives used complex financial structures to hide billions in debt and inflate profits. The fraud involved manipulating records, creating phantom entities, and collusion with auditors.
Enron employed multiple methods from Kautilya's catalogue: record manipulation (falsified financials), ghost entities (off-balance-sheet partnerships), quality substitution (reporting healthy profits while losing money), and collusion (Arthur Andersen cooperating with executives rather than providing independent oversight). The auditor independence Kautilya insisted upon was violated.
Enron filed bankruptcy. Executives were imprisoned. Arthur Andersen dissolved. The Sarbanes-Oxley Act imposed stricter standards and auditor independence requirements - rediscovering Kautilyan principles.
Sophisticated corruption follows ancient patterns. Record manipulation remains fundamental. Independent oversight fails when the overseer has conflicts of interest. Verify claims against reality, not just against other records.
Cryptocurrency rug pulls and DeFi exploits in the 2020s use remarkably similar methods to Kautilya's catalogue: fabricated transaction volumes (record manipulation), shell entities to move stolen funds (ghost entities), and inflated token values (quality substitution). The technology changes but the fraud patterns remain ancient.
Enron used over 3,000 special purpose entities to hide $38 billion in debt from its balance sheet. The resulting Sarbanes-Oxley Act of 2002 cost U.S. companies an estimated $1.4 billion annually in compliance, but restored independent auditor oversight.
Historical context
c. 4th century BCE
Earlier texts discussed proper conduct but lacked systematic anti-corruption frameworks. Kautilya's innovation was treating corruption as a technical problem requiring technical solutions.
Governing large territories requires delegating financial authority. Without anti-corruption systems, expansion becomes impossible - corruption consumes resources faster than expansion generates them.
Living traditions
- Internal Audit Functions: Corporate internal audit departments use techniques descended from Kautilya's methods for detecting and preventing corruption.
- Separation of Duties Controls: Preventing individuals from controlling all aspects of transactions continues Kautilya's prescription for limiting corruption opportunity.
- Whistleblower Systems: Formal channels for reporting misconduct parallel Kautilya's informant networks for detecting corruption.
- Association of Certified Fraud Examiners: Global organization for anti-fraud professionals
- Transparency International: Global coalition against corruption
- Central Bureau of Investigation: India's premier investigation agency continues the Kautilyan tradition of systematic anti-corruption enforcement. The CBI investigates corruption using methods Kautilya would recognize - surveillance, informants, documentation analysis, and coordinated raids.
- Central Vigilance Commission: India's apex vigilance institution implements preventive and punitive anti-corruption measures. The CVC's systems for detecting procurement fraud, asset disproportionate to income, and misuse of office continue Kautilya's systematic approach to corruption control.
Reflection
- If you were designing a system populated by imperfect people, some of whom would try to steal, how would you structure it?
- Is Kautilya's assumption that officials will steal if given opportunity cynical or realistic? How do you balance trust with verification?
- In situations where you have responsibility, which of Kautilya's corruption techniques could potentially occur? What oversight exists or should exist?