BLRPublic Service Dependency Atlas

Before you apply Khata transfer / mutation

Khata transfer / mutation · your situation

Draft or pending e-Khata

A property record is visible as a draft or has not reached a known final e-Khata state.

Jurisdiction
Bengaluru, Karnataka, India
Evidence as of
2026-08-30
Supported statements
24
Left unresolved
7
Full research
Atlas entry →

Your next step

Ask before you apply.

Our research left 7 requirements 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: Bruhat Bengaluru Mahanagara Palike / Bengaluru City Corporations Revenue Department, Greater Bengaluru Authority, Bengaluru City Corporations e-Aasthi / Greater Bengaluru Authority. 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.

24 statements

The public e-Aasthi citizen instructions say mobile/OTP login is used to see or download Draft eKhata; the draft is issued according to the existing BBMP Property Tax Register; additional information for Final eKhata includes a registered deed, Aadhaar-based eKYC, SAS Property Tax Application Number, property photo, and documents proving A-Khata, with an encumbrance certificate noted when immediate sale or transfer is planned.

Evidence BRecord verifiedBasis observation

Read this with itThis is a published checklist and route description, not evidence that every property must supply every listed item or that an upload will be accepted.

The current public e-Aasthi citizen page visibly advertises eKhata Automatic Mutations — Get Your Mutation and eKhata Pendency Reports.

Evidence BRecord verifiedBasis observation

Read this with itDirect public-page observation; the linked automatic-mutation flow and its eligibility were not entered or tested.

The current public e-Aasthi citizen page states that Draft eKhata has been issued as per the existing BBMP Property Tax Register and directs citizens to upload additional information online for Final eKhata, including a registered deed and other listed information.

Evidence BRecord verifiedBasis observation

Read this with itThis establishes what the public guidance says about Draft/Final e-Khata; it does not establish that Final e-Khata is a prerequisite for every mutation route.

The public e-Aasthi Khatha Transfer payment page says BBMP is not responsible for online-payment failure or auto-refund and directs a user whose amount was deducted but not updated in e-Aasthi to contact the Assistant Revenue Officer with details.

Evidence BRecord verifiedBasis observation

Read this with itPublished payment-recovery instruction only; no refund SLA or case-resolution outcome is stated.

A public e-Aasthi page is labelled Online payment for Khatha Transfer and visibly contains property details, mutation type, applicant name/mobile/email fields, a total amount field, and online payment options.

Evidence BRecord verifiedBasis observation

Read this with itThe generated public endpoint showed blank property/amount values. The observation proves a payment surface exists, not that an application can be initiated there or that payment completes transfer.

The public e-Aasthi search tells a user who does not find the property to click Do Not Find My Property eKhata so the Bengaluru City Corporation can check and revert.

Evidence BRecord verifiedBasis observation

Read this with itThe recovery route is visible; no details were entered and no request was submitted.

The public e-Aasthi citizen instructions say a citizen can file an objection not to issue Final eKhata on a property, and the public pending-mutation report exposes a File Objection label.

Evidence BRecord verifiedBasis observation

Read this with itOnly the public entry/label is verified; objection form fields, deadlines, standing, review, and outcome are not observed.

The public e-Aasthi citizen login page instructs citizens to ensure that tax for the current financial year is paid before trying to enter property details for existing records.

Evidence BRecord verifiedBasis observation

Read this with itThis records the page's visible notice only; it does not establish a universal eligibility rule or how tax status is checked.

Show the remaining 16 statements

The public e-Aasthi citizen page displays Mobile Number, Captcha, Captcha Answer, and an OTP-get control, and states that mobile-and-OTP login is used to see or download a property's Draft eKhata.

Evidence BRecord verifiedBasis observation

Read this with itDirect unauthenticated observation on 2026-08-30. The OTP control was not activated and no login, identifier, or property was supplied.

The public e-Aasthi ward/property map page exposes `Select your Property`, an `Enter a location` textbox, a `Go` control, and a map before a property or location is selected.

Evidence BRecord verifiedBasis observation

Read this with itNo location, property, or map control was used.

The current Greater Bengaluru Authority public directory lists e-Aasthi and B to A Khata / Single Plot Khata among its e-services and publishes an eKhata/New Khata helpline.

Evidence CRecord verifiedBasis observation

Read this with itDirectory-level observation; no transfer/mutation procedure, eligibility, or status contract is published on the directory page. Downgraded from Grade B on 2026-08-29: the available citation is a general-site reference rather than claim-specific evidence.

The public e-Aasthi citizen entry exposes a service labelled eKhata Automatic Mutations - Get Your Mutation.

Evidence BRecord verifiedBasis observation

Read this with itPublic availability of the entry does not establish that mutation is automatic for a particular deed or property.

The public e-Khata Application Status page accepts an EPID, displays stage/from/received/sent/sent-to/status/remarks columns, and publishes waiting-list and online-status guidance together with eKhata helpline 9480683695.

Evidence BRecord verifiedBasis observation

Read this with itThe page also states that applications are sent to the respective corporation outside the sub-division and says not to meet/contact anyone in the corporation. No EPID was entered, so no case-specific status or error was observed.

The public e-Aasthi Pending Mutation Report is headed Aadhar based Automatic Mutation and exposes fields for the registered-deed or mutation-application date, basis of mutation (including registered deed, inheritance, court order, or bank order), property EPID, seller/giving party, purchaser/receiving party, public-notice date, pending-with-whom state, and File Objection.

Evidence BRecord verifiedBasis observation

Read this with itThe public table observed No Data Available. The exposed columns are not proof that every mutation uses every basis or that a listed pending state is an error.

The public e-Aasthi citizen entry exposes search using a Ward Name or Number, Property ePID, or SAS Property Tax ID.

Evidence BRecord verifiedBasis observation

Read this with itOnly the public controls and instructions were observed; no property-specific search was run.

The public eKhatha Application Status page exposes an EPID input with SEARCH STATUS and RESET, shows status/routing/date/remarks headings, and renders the literal default row `No Data Available` when no EPID is entered; it also publishes waiting-list guidance and helpline 9480683695.

Evidence BRecord verifiedBasis observation

Read this with itNo EPID was entered; the default no-data row is not a property-specific outcome.

The official BBMP-hosted 2024 Form 24 e-Khata Order template says that after due-process verification based on submitted documents, the name is transferred and recorded in the property-tax register and the property-tax records and eKhata stand as stated in the order.

Evidence CRecord partialBasis observation

Read this with itThe document is an official order template. It does not prove that a current portal application follows the template, nor provide a live approval time or property-specific result. The original official endpoint is currently unavailable; this claim is retained as incomplete historical/public evidence, not a current complete procedure.

In a follow-up to the statusless application report, the citizen said the application was rejected for a missing document and advised reapplying based on the stated reason.

Evidence ERecord partialBasis observation

Read this with itThis is a reported case outcome and recovery, not a document checklist or a verified status-disclosure sequence.

One citizen reported having a physical khata in their own name while the draft e-Khata displayed a previous owner's name.

Evidence ERecord partialBasis observation

Read this with itA single report of a record mismatch. The reported scanning explanation and the meaning of a draft record were not independently verified.

The same citizen reported submitting a request to invalidate an existing e-Khata application and then reapplying with their khata document, after which they obtained an e-Khata.

Evidence ERecord partialBasis observation

Read this with itPossible case-specific recovery only. Another citizen report instead describes reapplication following an eventually visible missing-document rejection; neither report establishes when invalidation or reapplication is appropriate.

One citizen reported that their application showed documents uploaded but did not expose a status online, and that visits to multiple BBMP offices did not clarify its state.

Evidence ERecord partialBasis observation

Read this with itOne applicant's reported visibility failure; it does not prove a system-wide outage or office-access rule.

One citizen reported that after a final e-Khata issued in a prior holder's name, the online correction path displayed a condition that the prior holder's eKYC was not complete, leaving the citizen unable to complete that correction online.

Evidence ERecord partialBasis observation

Read this with itOne redacted Grade E account reporting a prior-holder record and an inability to complete correction; it does not establish an eKYC rule or general correction barrier.

One citizen reported both an upload/validation error and that their e-Khata application did not proceed; this single account does not establish causation or a general defect.

Evidence ERecord partialBasis observation

Read this with itOne redacted Grade E account; no general cause, official recovery, or universal barrier is established.

One citizen reported receiving an e-Khata after filing an application without using an agent.

Evidence ERecord partialBasis observation

Read this with itA single reported success. Do not generalize its reported turnaround, costs, or informal document-selection advice.

Block two

Where the record disagrees with itself

Accounts we could not reconcile. We kept both rather than picking a winner.

1 contested

One buyer with a bifurcated e-Khata in a prior holder's name stated that their manual-khata registration case would not mutate automatically.

Evidence FRecord contestedBasis observation

Read this with itThe post identifies manual khata as a potentially material term, but predicts an outcome rather than reporting a completed transfer. A separate reply's claim that mutation happens automatically is not first-person evidence and is intentionally excluded.

Block three

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.

6 open

No reviewed public official page establishes a complete current sequence from registered deed to Automatic Mutation, Final eKhata order, payment, download, and municipal record update, or a service-level time for that sequence.

The record leaves this openEvidence UnknownRecord unknownBasis inference

What we checkedForm 24 describes an approved-order effect, and public pages expose separate services; the relationship and timing remain unverified.

The reviewed public municipal pages expose an objection entry but do not establish objection form fields, filing deadline, review owner, status visibility, or recovery after an objection or mutation rejection.

The record leaves this openEvidence UnknownRecord unknownBasis observation

What we checkedNo objection or rejection was submitted or opened.

The public Draft/Final eKhata instructions list a registered deed as an input, but the unauthenticated route exposes no deed-validation error, rejection text, or public recovery route; those outcomes are Unknown without login and upload.

The record leaves this openEvidence UnknownRecord unknownBasis observation

What we checkedThe public login page was inspected; no login, upload, or validation action was attempted.

The reviewed public ward/property map page does not establish what property result, ward assignment, validation error, or Draft eKhata handoff follows entering a location or selecting a property; those outcomes are Unknown.

The record leaves this openEvidence UnknownRecord unknownBasis observation

What we checkedNo location or property was entered.

The reviewed public municipal pages do not establish which properties or registered deeds qualify for Automatic Mutation, when manual mutation is required, or whether a displayed EPID proves that ownership has been updated.

The record leaves this openEvidence UnknownRecord unknownBasis inference

What we checkedThe public service/report labels establish routes and fields, not eligibility rules or universal sequence.

The unauthenticated public pages do not establish the complete post-login Draft/Final eKhata form, current field-level validation, document rejection messages, or upload-to-status handoff for a particular property.

The record leaves this openEvidence UnknownRecord unknownBasis observation

What we checkedMobile/OTP login and listed uploads are visible, but this pass did not authenticate, transmit data, upload documents, or submit a request.

Block four

Where this route is known to break

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

8 recorded
documentation

Automatic-mutation eligibility is not exposed publicly

The citizen portal exposes Automatic Mutations and the report exposes mutation bases, but no individual property was checked.

Likely cause
Unknown; the reviewed public pages do not publish eligibility, manual-versus-automatic branching, or correction rules.
Recovery
Use the public EPID/status and mutation-report surfaces only for an authorized case; seek official case-specific guidance if the row or eligibility is absent.
process

Draft/Final eKhata form and upload outcome are login-gated

The public page directs mobile/OTP login and lists Final eKhata uploads, but the authenticated form and validation state are not visible in this pass.

Likely cause
Authentication and property-specific context are required; no access-control bypass was attempted.
Recovery
Treat the public checklist as a shelf reference only. The exact field, upload, rejection, and status path remains Unknown until a user completes an authorized session.
documentation

Objection or pending-mutation recovery is undocumented in the public view

Public pages expose File Objection and pending-with-whom fields but provide no case-specific row or downstream handling in this pass.

Likely cause
Unknown; no objection or property-specific mutation was opened or submitted.
Recovery
Record the public entry as a possible handoff only; do not infer deadline, owner, resubmission, or resolution from its label.
infrastructure

Documents appear uploaded but application state is not visible

A citizen reports uploaded documents with no visible online status and no clear status from visited offices.

Likely cause
Unknown; the account does not distinguish application rejection, workflow queueing, or interface failure.
Recovery
Treat the reported later rejection reason as a case-specific lead. Seek authorized, case-specific status guidance rather than resubmitting repeatedly.
documentation

Bifurcated or draft record retains a prior holder

Citizen accounts describe a prior holder's name remaining despite a later physical khata or bifurcated e-Khata state.

Likely cause
Unknown. The accounts indicate different property histories and do not establish a common technical or legal cause.
Recovery
Use the accounts only to identify terms for official case-specific support: draft e-Khata, physical/manual khata, bifurcation, mutation, and application invalidation.
process

Default public views do not expose a case outcome

The public status and pendency pages show blank/no-data defaults, while deed processing and map selection stop before an authenticated or property-specific result.

Likely cause
No EPID, property, filter, location, login, upload, or submission was used in this public-only pass.
Recovery
Use the published non-submission handoffs (eKhata helpline and any visible official report route) when a real case is authorised; validation, rejection, property result, and resolution timing remain Unknown here.
infrastructure

Reported supporting-document upload and validation dead end

A citizen reports that an attempted upload produced a repeat re-login error while the next step still required a deed document.

Likely cause
Unknown; the account cannot distinguish portal availability, session state, document selection, file handling, authentication, or case-specific validation.
Recovery
No authoritative recovery outcome was reported. Preserve the displayed messages and seek authorised, case-specific support; do not infer a general document checklist or workaround from this account.
process

Reported online correction block after prior-holder final record

A citizen reports receiving a final e-Khata in a prior holder's name and seeing a prior-holder eKYC condition on the online correction path.

Likely cause
Unknown; the account does not establish record ownership, the correction policy, the eKYC condition's applicability, or whether another authorised route can resolve the case.
Recovery
No completed recovery was reported. Obtain authorised, property-specific guidance on the issued record and correction state; do not generalise the reported eKYC condition or rely on informal workarounds.

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.

15 sources

Not your case?

Other situations for this service

Clean saleProperty not found in public e-Aasthi searchMutation pending or objection visible

How to read the gradesB — current official procedure, form, portal or agency page. C — official but indirect, incomplete, archived, undated or potentially outdated. E — genuine public first-person evidence. F — uncorroborated lead. 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-30; 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.