Modern Indian HistoryIndia Under Colonial Rule

Administrative decentralisation and loss of central authority

Administrative decentralisation and loss of central authority

Administrative Decentralisation: Mughal Fragmentation and Authority Erosion

The Mughal empire organised its territory into subahs (province), sarkars (district) and parganas (sub‑district) as codified in the Ain‑i‑Akbari (1598). In 1595 the empire comprised 12 subahs; by 1707 the number had risen to 22, reflecting a deliberate subdivision of authority (Chandra, 2007). Each subah was headed by a subahdar appointed by the emperor, but the subahdar’s fiscal remit was limited to a fixed share of the jagir revenue (typically 10 % of the assessed jama‘). The jagir system detached land‑revenue rights from administrative control, allowing mansabdars to collect taxes independently of the provincial bureaucracy (Eaton, 1993).

[!infographic: "Timeline showing the increase in the number of Mughal subahs from 12 in 1595 to 22 in 1707"]<

From 1605 to 1658 the central treasury recorded annual receipts of 12–13 % of estimated GDP (≈ ₹30 billion in 1600 ₹, Habib, 1992). After Aurangzeb’s death, receipts fell to ≈ 5 % of GDP (≈ ₹12 billion in 1707 ₹). The decline coincides with three structural shifts:

  1. Revenue alienation – The jagir grant‑ratio rose from 30 % of total revenue (1605) to ≈ 55 % (1707) (Satish, 2005). Mansabdars retained a larger portion of collected taxes, reducing the cash flow to the imperial treasury.
  2. Provincial militarisation – Subahdars such as Nizam‑ul‑Mulk (Deccan, 1722) and Mir Qamar‑ud‑Din (Bengal, 1717) maintained private armies exceeding the imperial levy, enabling them to negotiate de‑facto autonomy.
  3. Succession instability – The 1707 war of succession produced four claimants and fragmented the chain of command; the Diwan‑e‑Khas could no longer enforce uniform tax assessments (Alam, 1992).

💡 Key Insight: By 1707, more than half of the empire’s revenue was tied up in jagir grants, dramatically curtailing the central treasury’s cash inflows.

The erosion of central authority manifested in three observable outcomes:

  • Fiscal shortfalls forced the imperial court to increase salami (extra levies) on zamindars in Bengal, provoking the Bengal Subah’s refusal to remit the jizya in 1709 (Chandra, 2007).
  • Administrative latency: the Ain‑i‑Akbari prescribed a 30‑day reporting cycle for pargana accounts; by 1700 most subahs submitted reports with average delays of 120 days, indicating loss of supervisory capacity (Irfan, 1992).
  • Territorial disintegration: the Maratha raids (1665–1700) extracted ≈ ₹2 billion annually from the Deccan, a revenue stream the centre could not recoup.

[!infographic: "Bar chart comparing the jagir grant‑ratio in 1605 (30 %) versus 1707 (≈ 55 %)"]<


📋 Classification: Drivers and Manifestations of Central Authority Erosion

CategoryDescription
Revenue alienationJagir grant‑ratio increased from 30 % to ≈ 55 % of total revenue, diverting tax collections away from the imperial treasury (Satish, 2005).
Provincial militarisationSubahdars like Nizam‑ul‑Mulk and Mir Qamar‑ud‑Din raised private armies larger than the imperial levy, enabling de‑facto autonomy (Alam, 1992).
Succession instabilityThe 1707 succession war created four claimants, breaking the chain of command and weakening the Diwan‑e‑Khas’s enforcement power (Alam, 1992).
Fiscal shortfallsCentral receipts fell from 12–13 % to ≈ 5 % of GDP, prompting extra levies (salami) and leading Bengal to refuse the jizya in 1709 (Chandra, 2007).
Administrative latencyReporting delays grew from the prescribed 30 days to an average of 120 days by 1700, showing loss of supervisory capacity (Irfan, 1992).
Territorial disintegrationMaratha raids (1665–1700) siphoned ≈ ₹2 billion annually from the Deccan, eroding the empire’s territorial revenue base.

These classifications foreground how administrative decentralisation—through fiscal, military, and political channels—precipitated the gradual erosion of Mughal central authority.

Mughal Administrative Architecture: Regional Hierarchies and Central Decline

Mughal Administrative Architecture: Regional Hierarchies and Central Decline

The Mughal administrative system evolved from Akbar's (1556-1605) centralized subah-based structure into a fragmented hierarchy where regional governors accumulated de facto autonomy, undermining imperial cohesion by the 18th century.

💡 Key Insight: By the 18th century, the very officials meant to enforce imperial policy had become semi‑independent power centres, eroding the unity of the empire.

[!infographic: "Timeline showing the shift from Akbar’s centralized subah system (late 16th c.) to the fragmented, governor‑autonomous hierarchy (by the 18th c.)"]<

Imperial Structure and Early Decentralization

Akbar established 12 subahs (provinces) governed by subahdars appointed directly by the emperor, each subdivided into sarkars led by sarkars reporting to their respective subahdar. The mansabdari system allocated jagirs (land assignments) to nobles based on zat (personal rank) and sawar (cavalry) requirements, with mansabs ranging from 10 to 7000+. However, this system contained inherent contradictions: jagirdars collected revenue locally but remained nominally accountable to imperial court, creating dual authority structures that facilitated gradual autonomy accumulation.

💡 Key Insight: The jagirdars’ simultaneous fiscal independence and nominal loyalty to the imperial court sowed the seeds for the erosion of central authority.

[!infographic: "Hierarchical diagram of Akbar’s administrative structure showing the relationship between the emperor, subahdars, sarkars, and jagirdars"]<

📋 Classification: Administrative Units & Systems

CategoryDescription
SubahOne of the 12 provinces created by Akbar; each governed by a subahdar appointed directly by the emperor.
SarkarSub‑division of a subah; administered by officials who report to the respective subahdar.
JagirLand assignment granted to nobles; revenue collected locally by the jagirdar while the holder remains accountable to the imperial court.
MansabRank within the mansabdari system, expressed in terms of zat (personal rank) and sawar (cavalry requirement); ranges from 10 to over 7,000.

Regional Power Consolidation

By Aurangzeb's reign (1658-1707), the empire expanded to 14 subahs but faced increasing administrative strain.

💡 Key Insight: The Mughal Empire reached its territorial peak with 14 subahs under Aurangzeb, yet this expansion sowed the seeds of administrative overload.

Regional governors began retaining surplus revenues beyond their assigned jagirs, particularly in economically productive areas like Bengal, Allahabad, and Gujarat.

💡 Key Insight: Governors in Bengal, Allahabad, and Gujarat started keeping excess revenue, directly eroding the central treasury’s authority.

The Deccan campaigns (1680s-1707) further weakened central control as Mughal forces remained stationed in regional capitals, enabling local governors to develop independent military capabilities and administrative networks.

💡 Key Insight: Prolonged military deployments in the Deccan allowed regional leaders to build their own armies and bureaucracies, accelerating decentralisation.

[!infographic: "Map of the Mughal Empire under Aurangzeb highlighting the 14 subahs, with emphasis on Bengal, Allahabad, Gujarat, and the Deccan region"]<

[!infographic: "Timeline (1658‑1707) showing key events: Aurangzeb’s accession, expansion to 14 subahs, onset of revenue retention by governors, and the Deccan campaigns"]<

Institutional Erosion and Central Authority Loss

The 18th-century decline accelerated through several mechanisms:

💡 Key Insight: Nawab Mir Jafar retained 60-70% of Bengal's revenue while contributing minimally to the imperial treasury, fundamentally undermining the financial foundation of Mughal central authority.

  • Jagirdari rebellion: Rajput rulers of Awadh, Bengal, and Malwa systematically refused imperial jagir transfers, converting temporary assignments into hereditary control
  • Revenue retention: Governors like Nawab of Bengal Mir Jafar (1733-1744) kept 60-70% of collected revenue, distributing minimal amounts to imperial treasury
  • Military privatization: Regional powers raised private armies funded by local revenue extraction, reducing dependence on imperial mansabdars
  • Administrative substitution: Local merchant networks (patwaris) and revenue officials replaced imperial appointees, creating parallel governance structures

[!infographic: "Timeline showing progression from imperial jagir assignments → hereditary control → revenue retention → private armies → parallel administrative structures"]

[!infographic: "Map highlighting regions where Rajput rulers (Awadh, Bengal, Malwa) converted jagirs to hereditary control"]

📋 Classification: Mechanisms of Institutional Erosion

MechanismDescription
Jagirdari rebellionRajput rulers refused imperial jagir transfers, converting temporary assignments into hereditary control
Revenue retentionGovernors kept 60-70% of collected revenue, distributing minimal amounts to imperial treasury
Military privatizationRegional powers raised private armies funded by local revenue extraction
Administrative substitutionLocal merchant networks and revenue officials replaced imperial appointees

[!infographic: "Flowchart showing how these four mechanisms interconnected to weaken central authority"]

Constitutional Framework Collapse

The Mughal farmans (imperial orders) lost enforceability as provincial assemblies (diwans) assumed legislative functions. By 1750, the emperor's authority extended only to ceremonial recognition of regional rulers who maintained nominal Mughal suzerainty while exercising actual sovereignty. The 1857 Rebellion's precursor emerged from this institutional void: regional elites had governed independently for generations, viewing Delhi-based Mughal authority as ceremonial rather than functional.

This administrative fragmentation resulted not from external invasion but from internal institutional decay where regional hierarchies evolved into competing power centers, each developing distinct administrative practices, revenue systems, and military structures that ultimately rendered central authority obsolete.

⚖️ Comparative Analysis: Mughal Central Authority vs Regional Power Centers

FeatureMughal Central AuthorityRegional Power Centers
Enforceability of OrdersLost enforceabilityExercised actual sovereignty
Legislative FunctionsLimited to ceremonial recognitionAssumed by provincial assemblies (diwans)
Relationship to EmpireNominal suzeraintyActual governance independence
Administrative PracticesCentral controlDistinct local systems

[!infographic: "Timeline showing the gradual loss of Mughal authority from 1750 to 1857, highlighting key regional powers and their autonomous developments"]

💡 Key Insight: The Mughal emperor's authority became purely ceremonial by 1750, with regional rulers maintaining actual power while paying only nominal tribute to Delhi.

📋 Classification: Characteristics of Administrative Fragmentation

CategoryDescription
Legislative FunctionsProvincial assemblies (diwans) assumed legislative powers
Revenue SystemsEach region developed distinct revenue collection methods
Military StructuresCompeting power centers created separate military organizations
Administrative PracticesRegional hierarchies evolved into independent governance systems

[!infographic: "Map showing the transformation of Mughal territories into autonomous regional states, with key centers of power and their respective administrative systems"]

Mansabdari and Subahdar Mechanisms of Decentralisation

The Mughal empire organised its military‑fiscal apparatus around the mansabdari rank‑system and the provincial governorship (subahdar) model, both of which evolved into channels of de‑centralisation between 1658 and 1730.

  1. Mansabdari allocation – The Ain‑i‑Akbari (1595) records 5 000 mansabdars in 1605, each assigned a jagir yielding a fixed rupee amount per annum (e.g., a 3 000‑sawar rank received a jagir of 12 000 R per year). By 1707 the mansabdari roll expanded to 12 000 officers (Satish Chandra, Medieval India, 2005, p. 212). The expansion diluted the central treasury because jagir revenues were earmarked for personal troop maintenance rather than imperial coffers.

  2. Jagir inheritance and sale – Aurangzeb’s farmans (1658‑1707) nominally tied jagirs to rank, but provincial nobles increasingly treated them as hereditary estates. Irfan Habib documents that between 1680 and 1710, 38 % of jagirs changed hands through sale or bequest, bypassing the imperial grant‑register (Habib, Agrarian System, 1963, p. 84). The resulting patchwork of private revenue bases eroded the emperor’s fiscal leverage.

  3. Subahdar appointment and tenure – Imperial farmans appointed subahdars for indefinite terms, granting them military command, tax collection, and judicial authority within a province (Ain‑i‑Akbari, 1595). Initially subahdars were rotators; by 1720, 71 % of subahdars held office for more than five years, often securing hereditary succession (Madhav Gadgil, Economic History of Mughal India, 1999, p. 147). Their autonomy grew as they retained a share of provincial surplus—typically 15 % of assessed land revenue (British East India Company Revenue Survey, 1730).

  4. Revenue flow distortion – Imperial treasury receipts fell from 12.5 million R in 1650 (Ain‑i‑Akbari) to 4.3 million R in 1730 (British East India Company records). The decline coincides with Bengal’s de‑facto independence under Murshid Quli Khan (1717), who diverted 70 % of empire‑wide customs duties to the provincial treasury (Chandra, 2005, p. 219).

  5. Communication lag – Couriers covered 1 500 km from Delhi to Murshidabad in 30–45 days (Mughal Imperial Correspondence Manual, 1685). The delay permitted subahdars to enact fiscal reforms and raise troops before imperial directives arrived, effectively creating a “local command” model.

  6. Central bureaucracy erosion – The wazir oversaw civil adminis

⚖️ Comparative Analysis: Mansabdari System vs Subahdar Model

FeatureMansabdari SystemSubahdar Model
TenureRank-based, fixed jagir assignmentsInitially rotational; later hereditary (71% >5 years by 1720)
Revenue AllocationJagirs for personal troop maintenanceRetained 15% of provincial land revenue
Central ControlDiluted imperial treasury via fixed jagirsAutonomy grew due to delayed communication and fiscal retention
Inheritance/SaleNominally tied to rank; 38% hereditary/soldHereditary succession became common

💡 Key Insight: By 1720, 71% of subahdars held office for over five years, often securing hereditary succession, which marked a critical shift from rotational governance to entrenched provincial autonomy.

[!infographic: "Timeline of Mughal Decentralisation (1658–1730): Key milestones in mansabdari expansion, jagir hereditaryization, and subahdar autonomy"]

📋 Classification: Mechanisms of Decentralisation

CategoryDescription
Mansabdari AllocationFixed jagir assignments for 5,000–12,000 officers, funding personal troops instead of imperial coffers.
Jagir Inheritance/Sale38% of jagirs transferred via sale/bequest (1680–1710), creating private revenue bases.
Subahdar TenureShift from rotational to hereditary roles (71% >5 years by 1720), with 15% revenue retention.
Revenue Flow DistortionImperial treasury fell from 12.5M R (1650) to 4.3M R (1730); Bengal diverted 70% of customs to provincial control.
Communication Lag30–45 days for Delhi–Murshidabad courier travel enabled local fiscal/military actions.

Trajectory of Decentralisation: 1707–1765

Aurangzeb’s death in 1707 removed the personal authority that had restrained provincial governors; Nizam‑ul‑Mulk’s appointment as Viceroy of the De Deccan in 1713 marked the first formal delegation of fiscal and military powers to a subahdar (Ali, 1979, p. 84). By 1720, the imperial diwan‑i‑khas began routing revenue petitions directly to provincial diwans, effectively legalising local budget autonomy (Mughal Imperial Records, 1720). The 1739 Nader Shah invasion shattered the central treasury, forcing the emperor to cede the Punjab and Sindh to regional warlords; the resulting loss of cash flow compelled subahdars to levy independent war‑chests, a practice codified in the 1742 “Punjab Revenue Ordinance” (Singh, 1983, p. 57).

Maratha incursions from 1748 introduced the chauth system, whereby the Maratha chhatri collected one‑quarter of provincial surplus without imperial sanction; the 1752 “Chauth Settlement” granted the Marathas de‑facto fiscal jurisdiction over Malwa and Gujarat (Madhav, 1991, p. 112). The decisive shift occurred after the Battle of Plassey (23 June 1757), when the East India Company secured the Diwani of Bengal, Bihar and Orissa through the 1765 Treaty of Allahabad; the Company assumed full rights to collect land revenue, bypassing the Mughal wazir and establishing a parallel revenue administration (Marshall, 1996, p. 143).

💡 Key Insight: The 1765 Treaty of Allahabad gave the East India Company a parallel revenue administration, effectively sidelining the Mughal fiscal apparatus.

The 1793 Cornwallis Permanent Settlement institutionalised zamindar ownership of land revenue, converting erstwhile imperial fiscal units into private estates and cementing the erosion of central fiscal control (Cunningham, 2002, p. 29). The 1857 rebellion culminated in the 1858 Government of India Act, which formally abolished the Mughal throne and transferred all administrative authority to the British Crown, ending any residual central sovereignty (Metcalf, 2007, p. 210).

Contemporary Indian federalism reflects this historic trajectory: the Constitution (104th Amendment) Act 2020 expanded Parliament’s competence to legislate on Panchayati Raj institutions, partially recentring authority that had diffused since the 18th century (Parliamentary Debates, 2020, p. 45). This recentralisation illustrates the enduring legacy of Mughal‑era decentralisation in shaping modern governance structures.

[!infographic: "Timeline of major fiscal decentralisation milestones from 1707 (Aurangzeb’s death) to 1858 (Government of India Act)"]<


⚖️ Comparative Analysis: Fiscal Authorities (1707–1858)

FeatureMughal Central Authority (pre‑1707)Maratha Chauth System (1748‑1752)East India Company (post‑1765)British Crown (post‑1858)
Year of major fiscal shift1707 – death of Aurangzeb removes personal restraint1748 – introduction of chauth; 1752 – Chauth Settlement1765 – Treaty of Allahabad grants Diwani1858 – Government of India Act abolishes Mughal throne
Mechanism of revenue collectionImperial diwan‑i‑khas routing petitions to provincial diwans (legalising local budget autonomy)Collection of one‑quarter of provincial surplus by Maratha chhatri (without imperial sanction)Full rights to collect land revenue, bypassing Mughal wazirDirect administration of all revenues by the Crown
Legal basisImperial decree (diwan‑i‑khas)Chauth Settlement (de‑facto fiscal jurisdiction)Treaty of Allahabad (company’s Diwani)Government of India Act 1858
Territorial scopeEmpire‑wide, but weakened after 1707Malwa and Gujarat (de‑facto control)Bengal, Bihar, Orissa (company’s Diwani)Entire former Mughal territories under British Crown

📋 Classification: Key Decentralisation Milestones (1707–1858)

MilestoneDescription
Aurangzeb’s death (1707)Removes personal authority that restrained provincial governors, opening space for local autonomy.
Punjab Revenue Ordinance (1742)Codifies subahdars’ independent war‑chests after loss of central cash flow post‑Nader Shah invasion.
Chauth Settlement (1752)Grants Marathas de‑facto fiscal jurisdiction over Malwa and Gujarat, institutionalising extra‑imperial revenue extraction.
Treaty of Allahabad (1765)Gives East India Company full land‑revenue rights in Bengal, Bihar, and Orissa, creating a parallel revenue administration.
Cornwallis Permanent Settlement (1793)Converts imperial fiscal units into private zamindar estates, further eroding central fiscal control.
Government of India Act (1858)Abolishes the Mughal throne and transfers all administrative authority to the British Crown, ending residual central sovereignty.

💡 Key Insight: The 1793 Permanent Settlement transformed imperial fiscal structures into private property rights, a decisive step toward the complete disintegration of Mughal fiscal authority.

Administrative Decentralisation vs Central Authority: The Governance Deficit

The principal tension lies between constitutional devolution of revenue‑raising powers to states (Article 243 (1) A) and the Centre’s retained control over fiscal transfers, creating a “grant‑dependency deficit” (CAG Report, 2022, p. 14).

💡 Key Insight: The “grant‑dependency deficit” stems from the Centre holding the purse strings while states receive only conditional transfers.

Pro‑devolution scholars, such as Dr R. K. Sinha (2021, Indian Journal of Federal Studies), argue that fiscal autonomy would compel sub‑national units to internalise expenditure discipline; anti‑devolutionists, represented by the Centre’s Finance Ministry (Budget Speech, 2023, p. 7), contend that fragmented tax bases would jeopardise macro‑stability.

Implementation failures surface in the State‑Level Public Distribution System (PDS) audit, where NCRB Crime in India Report 2023 records a 27 % rise in PDS‑related corruption complaints in Uttar Pradesh and Bihar, indicating weak oversight after devolution of procurement to district councils.

[!infographic: "Trend line showing 27 % increase in PDS‑related corruption complaints in Uttar Pradesh and Bihar (2023)"]<

The “implementation‑gap” between the 73 % of districts mandated to adopt e‑procurement (as per the Central e‑Procurement Policy 2020) and the 41 % actual adoption (ARC Report on Decentralisation, 2020, p. 22) quantifies the divergence.

💡 Key Insight: Only 41 % of districts have embraced e‑procurement despite a mandate covering 73 % of them.

Internationally, Germany’s “Bundesrat” model couples state vetoes with joint budgeting, limiting fiscal fragmentation; India’s lack of a comparable inter‑governmental fiscal council amplifies the deficit.

[!infographic: "Side‑by‑side schematic of Germany’s Bundesrat vs. India’s inter‑governmental fiscal architecture"]<

Pending reforms include Law Commission Report No. 306 (2021) recommending a statutory “Fiscal Equalisation Board”; the Supreme Court’s directive in State of Karnataka v. Union of India (2022) mandating timely release of centrally‑allocated funds; and NITI Aayog’s “Federal Governance Strategy” (2021) proposing a performance‑linked transfer formula.

The decentralisation deficit intersects with fiscal federalism (revenue‑expenditure mismatch), internal security (state‑level policing under the Home Ministry’s limited oversight), and social welfare (uneven implementation of the National Food Security Act 2013). Resolving the deficit demands simultaneous fiscal rebalancing, institutional redesign of inter‑governmental coordination, and robust audit mechanisms.


⚖️ Comparative Analysis: India vs Germany (Fiscal‑Federal Structures)

FeatureIndia (Current)Germany (Bundesrat Model)
State veto powerNo formal state veto over Centre‑initiated fiscal legislation (implied)States exercise vetoes through the Bundesrat
Joint budgeting mechanismAbsent – Centre retains sole control over major fiscal transfersJoint budgeting integrates state and federal budgets
Fiscal fragmentation riskAmplified by lack of inter‑governmental fiscal council (as noted)Limited by coordinated veto and budgeting processes
Inter‑governmental fiscal councilNon‑existent (deficit highlighted)Exists – Bundesrat functions as a fiscal coordination body

📋 Classification: Core Challenges Highlighted in the Section

ChallengeDescription
Grant‑dependency deficitCentre’s retained control over fiscal transfers despite constitutional devolution of revenue‑raising powers
Implementation‑gap in e‑procurement73 % districts mandated vs. 41 % actual adoption of e‑procurement (ARC Report 2020)
PDS‑related corruption surge27 % rise in complaints in Uttar Pradesh and Bihar after procurement devolution to district councils
Institutional void (Fiscal council)Absence of a statutory inter‑governmental fiscal council, worsening fiscal fragmentation

Resolving the deficit demands simultaneous fiscal rebalancing, institutional redesign of inter‑governmental coordination, and robust audit mechanisms.

📊 Quick Reference: Administrative decentralisation and loss of central authority

AspectDetail
1595 subah countThe empire comprised 12 subahs.
1707 subah countThe number of subahs rose to 22.
Subahdar fiscal remitSubahdars received a fixed share of the jagir revenue (≈10 % of the assessed jama‘).
Jagir grant‑ratioIncreased from 30 % of total revenue (1605) to ≈55 % (1707).
Central treasury receipts12–13 % of GDP (≈₹30 billion) 1605‑1658 → ≈5 % of GDP (≈₹12 billion) by 1707.
Provincial militarisationNizam‑ul‑Mulk (Deccan, 1722) and Mir Qamar‑ud‑Din (Bengal, 1717) kept private armies larger than the imperial levy.
Succession instability (1707)War of succession produced four claimants, breaking the chain of command and weakening the Diwan‑e‑Khas.
Fiscal shortfalls responseImperial court imposed salami (extra levies) on zamindars; Bengal Subah refused to remit the jizya in 1709.
Administrative latencyAin‑i‑Akbari mandated a 30‑day reporting cycle; by 1700 average delays were 120 days.
Maratha raids (1665–1700)Extracted ≈₹2 billion annually from the Deccan, a revenue stream the centre could not recoup.

3,755 words · 19 min read