Before you apply Property tax name transfer

Property tax name transfer · your situation

Payment or name discrepancy

A public payment/correction surface is visible, but a property-specific demand or name correction is unresolved.

Jurisdiction
Bengaluru, Karnataka, India
Evidence as of
2026-08-31
Supported statements
14
Left unresolved
1
Full research
Atlas entry →

Your next step

Ask before you apply.

Our research left one requirement for this situation unresolved in the public record. Take the clarification below to the responsible office and get the current position in writing before you submit anything.

Responsible on the public record: Greater Bengaluru Authority / Bengaluru City Corporations e-Aasthi, BBMP Property Tax System / Revenue Department, Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department. We did not confirm that any of them decide this particular case.

Block one

What the published record says

Found in public documents, graded and dated. The statements closest to your situation come first; a single first-person account never outranks the documentary record. Open any source to read it yourself.

14 statements

The current BBMP Property Tax System page exposes an Online Grievance form with application, taxpayer-name, mobile, email, and OTP controls.

Evidence BRecord verifiedBasis observation

Read this with itNo values or OTP were entered. The page does not establish that this form accepts or resolves a particular e-Aasthi/khata transfer discrepancy.

The current public e-Aasthi transfer-payment and download notices direct a user whose payment was deducted but not updated in e-Aasthi to contact the ARO with details.

Evidence BRecord verifiedBasis observation

Read this with itThe notices do not state the required details, refund timing, or a guaranteed reconciliation outcome.

The current public e-Aasthi transfer-payment and download notices direct online-payment failure or auto-refund issues to the user's bank.

Evidence BRecord verifiedBasis observation

Read this with itNo payment, bank contact, refund, or timing was observed.

The public payment notice directs a user to their bank for online-payment failure or auto-refund and to the ARO when money is deducted but not updated in e-Aasthi.

Evidence BRecord verifiedBasis observation

Read this with itRecovery handoffs are visible; refund timing and evidence requirements are not.

The public e-Aasthi payment page labelled Online payment for Khatha Transfer exposes ward/property/mutation fields, applicant name/mobile/email, total amount, card/UPI/net-banking modes, and convenience-charge text.

Evidence BRecord verifiedBasis observation

Read this with itThe generated page was viewed without a property context; amount, applicability, and payment completion are Unknown.

The public BBMP Property Tax System page lists Name and Address change under property corrections and directs name/receipt discrepancy users to Find Your ARO, with Revenue contact details and business hours.

Evidence BRecord partialBasis observation

Read this with itThe page marks its feature list as last updated 27-06-2017; current correction eligibility and outcome are not established.

The current BBMP Property Tax System grievance page directs receipt discrepancies, name-related queries, and related queries to Find Your ARO.

Evidence BRecord verifiedBasis observation

Read this with itThe source exposes the official handoff, not a name-correction document checklist or completed correction.

The public e-Aasthi system exposes a Find ARO details by Ward Name entry.

Evidence BRecord verifiedBasis observation

Read this with itNo ward was selected; the jurisdiction-specific office result remains unobserved.

Show the remaining 6 statements

The public BBMP Property Tax System grievance form lists owner-name correction or update in a receipt as a selectable subject.

Evidence BRecord partialBasis observation

Read this with itSelectable grievance subjects, not triggered errors; no grievance was submitted.

The public BBMP Property Tax System correction page lists Name and Address Change under property corrections for Form 2 and Form 3 properties.

Evidence BRecord partialBasis observation

Read this with itThe public feature list is dated 2017; current eligibility and outcome are not established.

One citizen reported a property-tax receipt showing their name while an e-Aasthi page sought a mutation-related payment, leaving the person uncertain whether the khata transfer had already occurred.

Evidence ERecord partialBasis observation

Read this with itOne 2026 account of inconsistent displayed indicators. It does not prove that the tax receipt and khata record have a required relationship, that the payment was due, or that either record was correct.

One citizen reported that, despite a completed e-Khata and paid mutation charge, their property-tax name-update grievance remained pending.

Evidence ERecord partialBasis observation

Read this with itOne public account; it does not establish a general queue state, deadline, or recovery.

One citizen reported that a mutation component was rejected but a final e-Khata was later issued in the prior owner's name, and that the displayed online correction route could not be used in their case because it showed a prior-owner e-KYC condition.

Evidence ERecord partialBasis observation

Read this with itOne 2026 account. It does not establish a current e-KYC rule, final-record effect, correction eligibility, cause of rejection, or that reapplication is unavailable in other cases.

One citizen reported that their name was absent from a property-record ledger after an incorrect page had been uploaded, that the issue was later corrected, and that they were asked to submit a new e-Khata application with a new e-PID and an additional mutation-fee demand whose reason was unclear to them.

Evidence ERecord partialBasis observation

Read this with itOne 2026 account. It does not establish a missing-record cause, whether correction or reapplication was required, the source or validity of a fee, or a general e-PID rule.

Block two

What is still unsettled

Two kinds of thing sit here: questions the published record leaves open, and points where our own reading stopped — at a login we did not cross, or a step we could not observe without applying. Each item says which it is. Both are reasons to ask before you apply rather than after.

1 open

This pass did not establish a property-specific succession decision, record correction, missing-property response, payment reconciliation, name correction, mutation certification, or e-Khata order.

Our reading stopped hereEvidence UnknownRecord unknownBasis inference

Where we stoppedNo login, OTP, property identifier, EC, form, objection, payment, or submission was used.

Block three

Where this route is known to break

Failure points recorded for this situation, with the recovery the record supports — or the absence of one.

6 recorded
process

Payment or name correction needs an ARO/bank handoff

The public pages show a payment surface and name-correction route without a property-specific demand or completion state.

Likely cause
The generated payment context and legacy correction feature list do not expose current case rules.
Recovery
For a payment failure use the stated bank/ARO handoff; for a name discrepancy use the ward-based ARO route.
Owner on the public record
Greater Bengaluru Authority / Bengaluru City Corporations e-Aasthi, BBMP Property Tax System / Revenue Department
documentation

Property-tax name correction has no published completion standard

You need the property-tax record corrected, but the public page lists a route without saying what the office will accept or what completion looks like.

Likely cause
The correction page is a dated public feature list and the grievance form exposes subjects, not a published case-resolution procedure.
Recovery
Use the published correction or ARO route for a case-specific answer; do not treat the route as proof that correction will be accepted or completed.
process

Exception-route case result is not public

Public rules and screens identify succession, search, EC, payment, and ARO handoffs but do not expose a property-specific decision or correction result without case data.

Likely cause
Eligibility, identifiers, evidence, payment, notice, and authorised review are case-specific and were not entered or submitted in this pass.
Recovery
Use the applicable exact official route and preserve the resulting official acknowledgement or status; do not infer an outcome from public labels or default no-data screens.
Owner on the public record
Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department
documentation

Reported incorrect record followed by reapplication and unclear fee

One citizen reported a corrected ledger-name issue followed by a new e-Khata application, new e-PID and an additional mutation-fee demand that they could not explain.

Likely cause
Unknown; the account does not establish the record state, source of the earlier error, fee basis, application type, or municipal decision.
Recovery
Use the current official record/correction and payment routes to request a property-specific written explanation; do not infer a fee or reapplication requirement from this account.
Owner on the public record
Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department
process

Reported final record in a prior owner's name after rejected mutation

One citizen reported a final e-Khata in a prior owner's name after a rejected mutation component and an unavailable correction route in that case.

Likely cause
Unknown; the account does not establish the correct record, rejection reason, e-KYC rule, or a general correction path.
Recovery
Request a current property-specific correction or review route from the responsible revenue office; do not rely on a prior owner's identity credential or presume that final issuance closes every recovery option.
Owner on the public record
Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department
process

Reported mismatch between tax-receipt name and mutation-payment prompt

One citizen reported a tax receipt in their name while an e-Aasthi page sought a mutation-related payment, with no reported resolution.

Likely cause
Unknown; the report cannot establish the property-record state, payment validity, or relationship between the displayed tax and khata indicators.
Recovery
Obtain a current written, property-specific record and payment explanation from the authorised revenue channel before paying or assuming transfer completion.
Owner on the public record
Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department

Take it with you

Two ways to carry this

Both are built from the same claim records you just read. Neither one adds a fact that is not above.

Take this to the office

Prepare my clarification

The questions this situation leaves open, each with the document and date that raised it, and a note of what you have already read. It contains no personal details — you fill those in yourself before sending.

Same record, different reader

Copy for my agent

The identical evidence shaped for an assistant: supported facts with their grades and dates, the unresolved questions kept unresolved, and an explicit instruction that it authorises nothing.

Check us

Every source behind this brief

Read them yourself. If one has moved or changed since we checked it, that is worth knowing before you act.

10 sources

Not your case?

Other situations for this service

How to read the gradesB — current official procedure, form, portal or agency page. E — genuine public first-person evidence. Unknown — no usable source.

Independent research, not official advice. Public sources and known gaps are shown together; do not submit personal data through this ledger. Evidence collected as of 2026-08-31; nothing on this page is generated when you open it. Every statement is a recorded claim you can trace to the source above, and the unsettled items stay unsettled on purpose.