Jamabandi: the annual audit of the village accounts

Jamabandi — literally the “binding of the jama”, the settling of the demand — is the classical annual audit of a village’s revenue accounts. For a century it was the discipline that kept the record honest: once a year, an officer senior to those who wrote the registers sat down with the village’s books, checked them against each other and against the field, corrected what was wrong, and formally closed the year’s accounts. Much of what a probationer will hear about jamabandi today is in the past tense, because the practice decayed badly in the Dharani years. But its logic has not aged, the Bhu Bharati Act has re-laid its statutory foundation, and reviving it — village by village — is precisely the kind of work a Deputy Collector’s early postings will involve. This page describes the classical practice as the frame being revived; verify the current year’s jamabandi instructions from the CCLA before conducting one.

What jamabandi is for

Every revenue village generates a set of interlocking accounts across the fasli year: the pahani recording holdings and crops, the registers of demand (what each khata owes as sistu and other dues), collection (what was actually paid, receipt by receipt), balance (arrears), and the records of changes — new sub-divisions, mutations, conversions, assignments, encroachments. Each register is written by someone — historically the patwari, then the VRO, now the Grama Palana Officer — and each is capable of quiet, compounding error: a mutation entered in the RoR but never carried into the pahani; collection shown against the wrong khata; an encroachment recorded once and never pursued; water tax demanded on a dried source.

Jamabandi is the annual reconciliation of all of it. Its output is the faisal patti — the settled statement of the village’s final demand for the year, signed by the inspecting officer. “Faisal” is decision: after jamabandi, the year’s accounts are decided, and the next year opens from a clean, checked baseline.

Who conducts it

Jamabandi is deliberately conducted above the level that wrote the accounts. In the classical Telangana pattern, the inspecting officers are of RDO and DRO rank (with the Collector reviewing overall progress), each officer taking an allotted batch of villages, camping in or near them, with the Tahsildar and the village functionary in attendance with the records. The structure embodies the audit principle: the mandal office that supervised the writing of the accounts does not certify its own work.

For a Deputy Collector this is one of the classic independent tasks: a jamabandi allotment of villages is a self-contained assignment with a defined product — checked accounts and a signed faisal patti per village.

What is checked, register by register

The exact schedule of village accounts and their numbering comes from the Board’s Standing Orders and the District Office Manual compilations — read the current prescribed list before sitting down. The functional checks, though, are stable and worth internalising as a sequence:

1. Pahani against the field record. Does the pahani reflect this year’s azmoish — the crops actually inspected — or has it been copied forward from last year? Copied-forward entries are the classic decay signal.
2. Pahani against the RoR. Every mutation, sub-division and change ordered during the year must appear in the village record. Under Bhu Bharati this is now a statutory requirement — Section 13 directs that RoR entries flow into the village accounts and survey records, with survey numbers sub-divided and maps updated on mutation. Jamabandi is where compliance is actually verified.
3. Demand. Is the year’s demand correctly built — sistu, water tax, NALA-assessed items, lease amounts on government land, and miscellaneous dues — khata by khata? Wrong demand poisons everything downstream.
4. Collection against remittance. Receipts issued in the village must tally with challans remitted into the treasury. The gap between “collected” and “remitted” is where misappropriation lives; jamabandi’s receipt-to-challan check is its oldest fraud control.
5. Balances and arrears. Are arrears real, correctly carried forward, and pursued? Are old, irrecoverable items proposed for write-off through the proper channel rather than rolled forward forever?
6. Government land accounts. Encroachments recorded and acted on; assignments entered with conditions; poramboke and tank shikam intact against the record. Jamabandi is historically the one forum where the village’s government-land position gets an annual look.
7. The registers themselves. Pages numbered, entries attested, corrections initialled — the hygiene without which no later enquiry can rely on the record.

Discrepancies are listed, orders passed on the spot where the inspecting officer can, and the rest carried into an objection list for the Tahsildar to answer — the jamabandi analogue of an audit para. When the objections are settled, the faisal patti is drawn and signed.

Why it decayed — and how it is coming back

Two blows nearly killed the practice. First, the long shrinking of land revenue itself: sistu became financially trivial, and an audit built around closing the demand lost its fiscal urgency. Second, and decisively, the 2020 reforms: the VRO system was abolished, village accounts effectively ceased to be maintained, and Dharani made the record a portal transaction with no village-level books to audit. With no accounts and no accountant, there was nothing for jamabandi to check; between 2020 and 2025 the institution existed mostly in memory and in the departmental tests.

The Bhu Bharati regime rebuilt the preconditions. The Act restores manual village records alongside the electronic RoR and mandates (Section 13) that every RoR change be entered in the village accounts; the Grama Palana Officer cadre — 10,954 posts created in 2025, partially filled — restores someone whose job it is to write them. A record maintained in parallel, by a new cadre, migrating out of a portal known to carry legacy errors, is exactly the situation the jamabandi discipline was designed for. Expect the revival to be gradual and instruction-driven: as of August 2026, treat the classical pattern described here as the template, and the CCLA’s current circulars as the operative word on when and how this year’s jamabandi runs.

A worked example

A Deputy Collector under training is allotted six villages of a mandal for jamabandi camp. In the third village, the checks run clean until collection: the GPO’s receipt book shows ₹48,000 collected across the year against water tax and lease dues, but treasury challans account for ₹41,500. The gap traces to two receipt foils marked “cancelled” whose originals, when the payers are called, turn out to be live receipts in their hands.

The officer lists the objection, records statements of the two payers, seizes the receipt book under a panchanama, and reports to the RDO recommending recovery and disciplinary action — while completing the rest of the audit. In the same village, the pahani check shows a court-decree mutation ordered eight months earlier that never reached the village record; it is carried in on the spot, with the Section 13 requirement noted. The faisal patti issues with the settled demand, the objection memo travels with the report, and the village opens the new fasli year with accounts that mean something.

Edge cases and common mistakes

• Jamabandi as a signing ceremony. The decayed form of the institution is an officer signing faisal pattis in the office from registers brought in a jeep. The value is in the cross-checks and the camp; a signature without them certifies errors.
• Auditing only money. The collection check matters, but in today’s conditions the record checks — RoR-to-village-account flow, government land, encroachments — carry the real risk. A village can have trivial demand and catastrophic records.
• No GPO in post. Many villages still lack a Grama Palana Officer; the RI covers them and the accounts may be skeletal. Record the fact rather than manufacturing an audit of registers that do not exist — the honest objection list is the lever that gets the village staffed.
• Treating portal data as the record. The Bhu Bharati portal is the RoR; jamabandi’s question is whether the village accounts match it. Printing the portal and filing it is not the reconciliation.
• Old arrears rolled forward blind. An arrear carried for a decade without process is a fiction. Either revive recovery lawfully or propose write-off; jamabandi is the annual chance to choose.

Questions you’ll actually get

“Does jamabandi still legally exist?” The accounts framework it audits does — the 1317 Fasli Land Revenue Act and the Board’s Standing Orders were never repealed, and Bhu Bharati’s Section 13 re-mandates village accounts. What lapsed was the practice. Whether a formal statewide jamabandi programme has been re-notified for the current fasli is a matter to verify from CCLA instructions.

“What exactly do I sign at the end?” The faisal patti for each village — the settled statement of the year’s demand — plus your inspection report and objection list to the RDO/DRO.

“The registers for 2020–2025 simply don’t exist. What is the baseline?” The migrated RoR as corrected under Bhu Bharati, the last pre-2020 village accounts, and the current year’s azmoish. Part of the revival is reconstructing opening balances honestly — record what is reconstructed and from what source.

“Is this the same as the Revenue Sadassu?” No. A Revenue Sadassu is a public grievance hearing about the record; jamabandi is an internal audit of the accounts. They complement each other — sadassu applications often surface exactly the discrepancies jamabandi should have caught.

What to watch in the field

When you first take charge anywhere, ask one question of each village in your jurisdiction: when was its last jamabandi, and where is its last faisal patti? The answers will map the decay better than any briefing — and the villages with the oldest answers are where your first camp should be.