eKhata Correction or Mutation in Bengaluru? Choose the Right Process

The key distinction: did the underlying owner change?

A correction fixes a factual or clerical problem in an existing record. A mutation records an owner-changing event such as a registered transaction, inheritance, or court order. Selecting “correction” because it sounds simpler can send the case down the wrong path.

The current Khata Management System displays correction, automatic mutation, inheritance mutation, owner-share update, eKYC update, bifurcation, and amalgamation as separate tasks. The public pending-mutation report also shows distinct mutation bases and an objection action.

NammaGuide is independent of GBA, Bengaluru city corporations, and e-Aasthi. This guide helps classify the task; it does not decide ownership, title, or the authority's result.

NammaGuide decision tree

Did a legal event change the person/right recorded for the property?
├── No
│   ├── Spelling, contact, eKYC or another factual field → Correction/update
│   └── Property split, merge or structural record issue → Dedicated service
└── Yes
    ├── Registered sale/gift/release/partition → Transaction mutation
    ├── Death/succession → Inheritance mutation
    ├── Court order → Court-based mutation
    └── Competing or unsupported claims → Disputed/legal route, not correction

This diagram is practical NammaGuide guidance. The live service determines which route is available for the property and which evidence it accepts.

First classify the change

If the property is not found at all, return to the Bengaluru eKhata application guide instead of forcing either route.

Preparation checklist

Prepare one short “change statement” before uploading anything:

• current ePID/property identifier and current city corporation/ward;
• exact field or recorded person shown now;
• exact result requested;
• event that justifies the change;
• event/document date and registration/reference number, where applicable;
• existing Khata/eKhata and current property-tax receipt;
• Request ID if a case is already open; and
• whether any other owner/heir/person objects.

The public e-Aasthi document page verifies general classes such as owner/property photographs, accepted identity proof, relevant registered deed, existing Khata record, and current tax receipt. It does not publish one complete checklist for every correction or mutation scenario.

For that reason, treat the following as evidence categories to confirm in the live form—not a universal upload list:

• registered instrument for a transaction-based mutation;
• succession evidence for an inheritance route;
• certified order for a court-based route;
• existing record plus proof of the correct value for a factual correction; or
• survey/approval records for bifurcation or amalgamation.

Do not upload family records, Aadhaar, financial papers, or other sensitive documents “just in case.” Use only what the official route requests.

Process in plain language

1. Confirm corporation and existing record

Use the GBA website to check current jurisdiction, then locate the property/ePID. Legacy BBMP labels may remain on the operational screen.

2. Match the event to the service

Ask what changed, not what wording looks easiest. A sale, gift, partition, succession, or court direction points toward mutation. A same-owner clerical problem points toward correction. A split, merge, share, or eKYC issue may have its own route.

3. Review the before-and-after data

Compare the exact names, identifiers, shares, property description, and transaction basis. Make a one-page comparison so the requested change is unambiguous.

4. Use the live checklist

Authenticate through the current municipal portal and upload the evidence requested for that route. Public pages do not expose every case-specific field, so this guide does not fabricate them.

5. Save the application trail

Keep the Request ID/ePID, submission date, payment reference if the portal generates one, and copies of clarification requests.

6. Monitor notice and objection status for mutation

The official pending-mutation report publishes notice-related records and an objection action. Do not assume “submitted” means the notice/objection stage is finished.

Troubleshooting

Common mistakes

• Using correction after an owner-changing transaction.
• Treating mutation as conversion from B record to A category.
• Assuming property-tax payment automatically updates ownership.
• Using an old ward/corporation without checking GBA.
• Uploading only a tax receipt for a registered transaction.
• Missing the public notice/objection trail.
• Quoting a legacy processing time as a guarantee.
• Assuming a Khata mutation conclusively proves title.

Read A Khata, B record, and eKhata explained before drawing a legal conclusion from the municipal record. If the problem is only tax payment or receipt status, use the property-tax troubleshooting guide.

Fees and timing

The reviewed public sources do not establish one current fee or one guaranteed total turnaround for all correction and mutation types. The 2024 property-tax rules contain a notice/no-objection step for the process they describe, but current applicability can vary with the corporation and mutation route. This article therefore does not convert that sub-step into a universal deadline. Use the live demand/notice and responsible authority for the specific case.

Official next action

1. Confirm the current corporation on GBA.
2. Open the current Khata service selector and identify the event-specific route.
3. Review public pending mutations and objections.
4. Use the public e-Aasthi document categories, then follow the selected form's exact checklist.

Government instructions versus NammaGuide guidance

The authority determines jurisdiction, legal sufficiency, notices, objections, charges, and the final record. NammaGuide contributes the event classifier, comparison worksheet, privacy guardrails, and troubleshooting. Optional paid help is limited to guidance time and remains secondary; it cannot settle an ownership dispute, act as legal representation, speed the authority, or guarantee mutation.

Sources and review record

• Primary sources: GBA, Khata Management System, pending-mutation report, and e-Aasthi document categories.
• Legal context reviewed but not converted into a universal SLA: 2024 Property Tax Rules and the relevant India Code texts. Current applicability should be checked for a disputed case.
• Research verified: 13 August 2026.
• Researched and reviewed for NammaGuide by Manoj Mukherjee under the editorial and corrections policy.
• Review trigger: portal service changes, new mutation/correction rules, GBA jurisdiction changes, or updated fee/notice instructions.