Filings & statutory work

The work beside the valuation, and it has its own deadlines

A practice does not only value. It registers projects, files quarterly, watches approvals expire, computes duty on a transfer and drafts the instrument that effects it. All of that is date arithmetic and state-specific rules — which is to say it is exactly the kind of work that is tedious to do by hand and unforgiving when it is done wrong.

Five areas

Dates, rates and instruments

All of it is arithmetic against rules that differ by state — which is to say it is tedious to do by hand and unforgiving when it is done wrong.

Registration and periodic obligations

Registration for a project under the state authority it falls under, and the periodic obligations that follow from it. The obligations are generated with actual due dates for that state rather than as a checklist someone maps onto a calendar themselves.

Obligations generated per state, from the registration date and the project’s end date
Due dates rather than reminders — a date you can put in a diary and be held to
The prescribed schedule for the state in question, rather than a generic form
A calendar view of what is due across the projects a person is responsible for

Approvals and their expiry

Commencement and occupancy certificates, fire and environment clearances, layout approvals — each with the authority that issued it, its reference, when it was issued and when it stops being valid. The expiry is the point: an approval that lapsed is a problem that was visible for months.

Validity and expiry on every approval, with the issuing authority recorded
Anything lapsing within ninety days surfaced without being asked for
Each approval linked to the document that evidences it, openable by a reviewer
The same approval rows the evidence gate reads when a report asserts an approval is held

Duty and the notified rate

Duty on a transfer is computed against the consideration and against the notified rate for the property, and the higher of the two applies. Both are shown, because a person defending the calculation needs to see which one governed and by how much.

Both bases computed and displayed, with the governing one identified
State rates, and the concessions that vary by the parties to the instrument
Exact decimal arithmetic, rounded once — the same discipline the valuation uses
The working is on the record, so a disputed figure is answered from the file

Transaction documents

Deeds, leases, rental agreements, development agreements, memoranda and powers of attorney, drafted against a clause schedule rather than assembled from a template someone edited last year. Parties, recitals, consideration, covenants and the schedule of property are structural requirements, not sections a drafter might remember.

A clause schedule per instrument type, and an unregistered section type raises rather than falling through
Consideration figures come from the record, on the same rule the valuation figures follow
The evidence gate applies here too: an instrument cannot assert a title fact nothing supports
Exports as documents, and as structured data for a system that has to read them

Rent rolls and portfolio reporting

The reconciliation work: a rent roll as of any date, and a roll-up across a book of properties. This path runs with no drafting model involved at all — its content is arithmetic, so it is computed rather than written, and it produces the same figures every time it runs.

Weighted average unexpired lease term, expiry profile, vacancy and escalation schedule
A total that ties to the sum of its lines to the rupee, per property and in aggregate
Concentration by tenant, city and asset class
Construction disbursement checked against the certified stage, so a tranche ahead of progress is flagged rather than paid

Why state-specific is the whole difficulty

The rule is national. The number never is.

Almost everything on this page varies by state — the authority, the prescribed schedule, the due dates, the duty rate, the notified rate, and the factor a local area unit converts by. Software that treats any of those as a constant is wrong somewhere and does not know where.

Obligations and their due dates are resolved per state rather than from a national default.
Duty rates and the concessions attached to them are per state, and the notified rate is per locality within it.
Local area units — bigha, biswa, katha, vigha — have factors that differ by state, and getting one wrong moves an area by a multiple rather than a percentage.
Those state-dependent unit factors are held as unverified against notified schedules and refuse to convert unless somebody explicitly instructs them to. A blocked conversion is recoverable; a silently wrong area is not.

Said plainly

Statutory data is a maintenance commitment, not a dataset

Rules change, rates are revised, schedules are re-notified and a factor that was right last year is wrong this year. Any product in this category is only as current as the person whose job it is to keep it current — so we would rather tell you that than let a page imply the software knows things it cannot know. Where a value is not verified against a notified source, the software says so and refuses to use it silently. Where a due date comes from a schedule, that schedule is what we check it against. If you find something stale, telling us is the fastest route to it being fixed, and we would rather hear it from you than have you find out from an authority.

Tell us which states you actually work in

It is the first thing that changes what we would show you: the authority, the schedule, the duty rate and the unit factors are all downstream of that one answer.

Talk to us For developers

Get in touch

Talk to the people building it

No chatbot and no ticket queue. Tell us what your practice actually looks like — how many valuers, which asset classes, who reviews, which banks you are on the panel of — and someone who works on the software will reply.

info@legosphere.com