Possession is not the end of a handover. Every buyer in the project still needs three records in their own name — the khata (today, an e-khata), the property tax account and the BESCOM electricity connection — and until they have them, they keep calling your CRM team. Most of the delay on these files is not at the authority. It is a missing document, a name spelt two ways, or an area that does not match, found weeks after the file was sent.
This checklist is written for builders’ CRM and handover teams in Bangalore. It splits the paperwork into what you collect once for the project and what you collect for each unit, and lists the mismatches that most often send a file back.
Buying a flat yourself? This page is for developers. The buyer-side version is our after-buying-a-flat checklist for khata, tax, BESCOM and BWSSB.
Why a Checklist Matters at Project Scale
For one flat, a missing paper costs a week. Across a hundred units it becomes a backlog nobody can explain: some files waiting on the buyer, some on your team, some on the authority, and no one sure which is which.
A checklist fixes two things:
- Files go in complete. Each unit is checked before it is filed, so anything missing goes back to your team as a specific list, not as a rejection later.
- Timelines become measurable. If you record the date each unit’s documents were complete, you can see exactly where time is being lost.
Part 1 — Project-Level Documents (Collect Once)
These describe the building, not the buyer. They are the same for every unit, so collect them once at project setup and keep one clean set.
| Document | Why it is needed |
|---|---|
| Title documents for the land, with the registered deed chain | Shows the project land was the developer’s to build on and sell |
| Approved building plan | The units on record must match what was sanctioned |
| Occupancy certificate (OC) / completion certificate (CC), where applicable | Listed among the documents for a first (new) khata for each unit |
| The project’s existing khata and property tax records | Unit khatas are carved out of the project’s record |
| Encumbrance Certificate (EC) for the project land | Shows registered transactions and charges on the land |
| The list of units with their areas, as in the sale deeds | Used to check every unit’s details before filing |
Which documents the authority actually asks for depends on who has jurisdiction: the BBMP area, a BDA layout, a city or town municipal council, or a gram panchayat. Procedure, fees and timelines differ between them, so confirm the authority for the project before the first batch goes in.
If a document on this list is missing or out of date, every unit inherits the problem. It is worth fixing before any unit is filed.
Part 2 — Unit-Level Documents (Collect Per Buyer)
For each unit, keep one row on a sheet and one folder of documents. The essentials:
- Registered sale deed of the unit (a clear PDF of every page is enough to start)
- Buyer’s identity documents — Aadhaar and PAN of every buyer named on the deed
- Unit details as registered — flat number, block or tower, floor and area, exactly as the deed states them
- Latest property tax receipt for the unit, if it has already been assessed
- The unit’s BESCOM bill showing the RR number and account ID, for the name transfer
- Buyer contact details — mobile number and email
- Joint owners and representatives — documents for every co-owner, and a power of attorney where a buyer will not sign in person (for example, a buyer living abroad)
A simple per-unit sheet makes batches manageable. Useful columns: unit number, buyer name(s) as on the deed, deed registration number and date, services wanted (khata, tax, BESCOM), date documents were complete, current status, and the reason for any hold.
Part 3 — The Order That Works
These records depend on each other, so the order matters:
- Unit khata / e-khata first. It is the master record that the other two follow.
- Property tax next. The unit is assessed and the tax account is put in the buyer’s name, so the first receipts are right.
- BESCOM last. Electricity connections move from the developer to each buyer after handover.
Pending property tax on the project or a unit can hold up a khata application, so check for dues before a batch goes in. Our guide to property tax arrears after buying a flat explains why dues travel with the property.
The Mismatches That Send Files Back
Most returned files come down to the same few problems. Check for them before filing:
- Name spelt differently on the sale deed, Aadhaar and PAN. Decide which spelling is correct and how the difference will be explained before filing.
- Area or unit number different between the deed, the approved plan and the project’s records.
- A co-owner missing. If two buyers are on the deed, both buyers’ documents are needed.
- Pending tax dues on the project or the unit.
- An unreadable or partial deed scan. A missing page is a missing document.
- A buyer who cannot sign in person without a power of attorney in place.
Where a record genuinely does not match the deed, it has to be corrected before the transfer; see khata correction in Bangalore for how that works.
Government Charges: Agree the Rule Before the First Batch
Most unit files go through on the normal route. Occasionally an authority raises an objection on a particular file, and resolving it costs a government charge or extra time. Agree with whoever runs your filings, in advance, how those are approved: per unit, or under a standing limit your team sets. A charge that nobody approved is how a fixed-fee arrangement turns into a dispute.
Running It as a Batch, Not as Favours
The teams that clear handovers fastest treat them as a process:
- One project setup, with the parent documents checked once.
- Batches of units sent with the per-unit sheet.
- Scrutiny before filing, with gaps reported per unit.
- A unit-by-unit status report your CRM team can share with buyers.
- A monthly summary of units completed, in progress and held up, with the reason for each hold.
How Sevantay Helps Builders
Sevantay runs khata, property tax and BESCOM work for projects across Bengaluru, unit by unit and in batches. Your handover team gets a status report per unit, and can raise and track requests on the Sevantay Enterprise portal, with each unit’s documents uploaded against a checklist. Pricing is per unit and agreed per project; government charges are separate, at actuals, and only with your approval.
See how we run handovers for builders → — or start with a pilot batch from one project.
- WhatsApp: Message us about a project
- Call: +91 99869 14198
Individual services are also available on their own: new khata registration, khata transfer, property tax name change and BESCOM name transfer.
Sevantay is a private facilitation platform, not a government body. Approvals, timelines and official fees are decided by the authority concerned.