Hindi to English Mutation Register Translation: Property Verification

A mutation register (jamabandi or nakal) is the revenue department's official record of ownership changes in a land parcel. When you need that document in English, for a visa application, OCI paperwork, or a property inheritance abroad, you want a translation that is accurate, keeps the tabular layout, and reflects the original Hindi fields faithfully. This guide explains what is inside the document, which terms appear most often, how AI translation handles the table-heavy format, and when a certified translation becomes necessary.

What a Hindi Mutation Register (Jamabandi / Nakal) Contains

A typical mutation register records the chain of ownership transfers for a khewat (ownership account) within a village or revenue estate. It lists the owner or joint owners by name, khewat and khatauni numbers, the khasra (survey) numbers with area and land type, the nature of the transfer, sale, gift, will, family partition, and the revenue officer's stamps. The document is the foundation for property verification in India’s land records system, as explained on the central land records portal. Every district maintains its own format, but the core data remains similar across states.

State-Level Differences in Mutation Formats

While the underlying revenue terms are shared, the layout and supplementary fields differ by state. Haryana’s jamabandi, accessible through the Jamabandi portal, spreads ownership, cultivation, and mutation history across a grid with separate columns for gair mumkin (non-cultivable) and chahi (irrigated) land. Uttar Pradesh uses a consolidated khatauni that bundles crop-type codes, whereas Maharashtra’s record (7/12 extract) merges mutation remarks into a single remarks column. A translator who knows these regional quirks can map column headers correctly and avoid misplacing vital data.

Common Hindi Terms in a Mutation Register

The table below covers the Devanagari terms you will encounter most often in a Hindi-language mutation register, from the higher-level account to the individual survey number.

Hindi (Devanagari)	Romanisation	English
दाखिल खारिज	dakhil kharij	mutation (entry of transfer)
जमाबंदी	jamabandi	record of rights / village land record
नकल	nakal	certified copy
खेवट	khewat	ownership register / account
खतौनी	khatauni	cultivation register / holding
खसरा	khasra	survey / plot number
पटवारी	patwari	village record keeper
कानूनगो	kanungo	revenue supervisor
राजस्व अधिकारी	rajsva adhikari	revenue officer
परिवारिक हस्तांतरण	parivarik hastantaran	family transfer
विल	will	will

Why People Translate a Mutation Register into English

An English version of a mutation register serves several practical needs. NRIs applying for an OCI card often submit a translated land document to prove ancestral ties; the OCI scheme outlines the supporting documents required. Visa officers assessing an applicant’s property ownership in India, or a foreign bank evaluating collateral for a loan, routinely ask for a readable English translation. Legal professionals handling cross-border inheritance likewise need the mutation chain rendered clearly. In all these cases, the translation must be a faithful rendering of the original ownership details and transfer history.

AI Translation vs. Certified Work for Mutation Records

For understanding the document, preparing a visa application draft, or discussing property details with family, an instant AI translation is fast and practical. Lekhak’s self-serve platform delivers an English DOCX in minutes, preserving the register’s table structure so you can review khewat numbers, khasra entries, and transfer dates without delay. The result is accurate enough for internal use, pre-screening, and any scenario that does not require an official stamp. If the receiving authority insists on a formal certificate of accuracy, a court, an embassy, or a government agency abroad, Lekhak also offers certified translation on‑demand (not self‑serve) to meet that requirement.

What Lekhak’s AI Translation of a Mutation Register Produces

When you upload a scanned PDF or clear photo of a Hindi mutation register, the platform runs OCR on the image, recognises the tabular layout, and outputs a downloadable DOCX file. All column headers, khewat number, khatauni number, khasra, area, transfer type, are translated into English while the original Hindi document remains untouched. The field values, dates, and numeric identifiers stay precisely where they belong in the table. You get a clean, editable Word document that you can immediately use for review, attach to an email, or forward to a lawyer. The translation runs on a multi-agent AI pipeline that checks consistency across rows before finalising the file.

Notarisation, Apostille, and Embassy Attestation for Translated Documents

A certified translation provides a signed statement of accuracy, but it is not the same as notarisation or attestation. Notarisation means a notary public witnesses a signatory and places a seal; apostille is a standardised authentication under the Hague Convention, handled in India by the Ministry of External Affairs. Embassy attestation adds a further layer for non-Hague countries. These are separate government procedures that the document holder must arrange directly. Lekhak does not perform notarisation, apostille, or embassy attestation, its role is providing the accurate translation, including a certified version on‑demand when an official statement of accuracy is needed.

Statutes and Rules Governing Mutation Records in India

Mutation records operate under state-specific land revenue legislation, but certain central laws form the backbone of property registration and transfer. The Registration Act, 1908 mandates registration of instruments that affect immovable property; the Transfer of Property Act, 1882 defines the modes of transfer such as sale, gift, and will. State revenue codes, the Punjab Land Revenue Act (applicable in Haryana) or the Uttar Pradesh Land Revenue Code, prescribe the exact format of jamabandi and the procedure for recording mutations. A translator does not need to apply these statutes but benefits from knowing the legal context that shapes the document’s fields.

Frequently Asked Questions

What is a jamabandi and how does it differ from a mutation register?

A jamabandi is the periodic record of rights that lists all landholders in a village; a mutation register records each individual transfer order that feeds into that record. Often the terms are used interchangeably when referring to the certified copy of the latest ownership state.

Can I use an AI‑translated mutation register for a visa application?

For pre‑submission review and draft preparation, yes. If the embassy’s checklist requires a certified translation, you will need a formally attested version. Lekhak’s instant AI output serves the first need, and certified translation is available on‑demand for the second.

Does the AI translation keep the rows and columns of the original?

Yes. The output is a DOCX file that preserves the table layout. Field names such as khewat and khasra remain in their proper columns, and all numeric data stays aligned.

Is a mutation register the same as a sale deed?

No. A sale deed is the contract that transfers ownership; the mutation register is the revenue department’s recording of that transfer in the land records. Both are often needed together for property verification.

What information is redacted or removed during translation?

The self‑serve AI translates the visible text faithfully. Identifying details that are already present in the original, owner names, Aadhaar numbers, registration numbers, appear in the translation as they do in the source; nothing is deliberately stripped unless you edit the DOCX afterwards.

How long does an AI translation take?

Typically a few minutes. The platform processes the uploaded file, runs OCR, translates, and builds the Word document. You can download the DOCX as soon as the job completes.

Do I need to notarise the translated document separately?

Notarisation is a separate process you arrange through a notary public if the receiving authority demands it. The translation itself does not include a notary seal unless you combine it with a certified translation and then proceed to notarisation on your own.

Can I get an apostille for an AI‑translated document?

An apostille authenticates a public official’s signature, not the translation content. If you need an apostille, you would typically obtain a certified translation first and then submit it to the MEA through the prescribed channel. Lekhak does not apply for apostilles.

What happens if the original register has handwritten entries?

The platform’s OCR handles printed and clear handwritten text. However, very faint or stylised handwriting may reduce accuracy. Scanning at 300 dpi or higher helps. For difficult cases, a typing service or certified translation may be the better path.

How does Lekhak handle regional variations in jamabandi formats?

The AI pipeline is trained on diverse document layouts and adapts to the columns and headers present in the uploaded file. It does not force a single template, so a Haryana grid, a UP khatauni, or a Maharashtra 7/12 extract each come out with their own structure intact.

Related: pricing