Under the Real Estate (Regulation and Development) Act, 2016, compliance lives in the details: which account a payment lands in, when money can be withdrawn, what your brochure says, and whether your quarterly update reached the state portal on time. For real estate developers running several projects, spreadsheets cannot keep up. This checklist sets out what your ERP, CRM, and sales systems should do to support RERA compliance.

State RERA rules differ. Confirm each item against the rules of every state where you have registered projects, and have your legal and finance advisors sign off.

1. Project master data

  • [ ] Each project and phase stored with its RERA registration number, validity dates, and state authority
  • [ ] Alerts before registration expiry and for extension filings
  • [ ] Sanctioned plans, layout, and specifications stored with version history
  • [ ] Carpet area recorded per unit as defined under RERA, separately from built-up or super built-up area
  • [ ] Declared completion date tracked, with a warning when progress slips against it

2. Designated project account (the 70% rule)

  • [ ] Every project mapped to its dedicated RERA bank account
  • [ ] Customer receipts automatically split so at least 70% goes to the designated account (or 100% where state rules require it, for example when receivables fall short of the remaining cost)
  • [ ] Withdrawals only against project cost, in proportion to completion
  • [ ] Withdrawal workflow requires certificates from the project engineer, architect, and chartered accountant before approval
  • [ ] Dashboard showing collections, withdrawals, and headroom per project, with alerts as limits approach
  • [ ] Data ready for the annual audit of project accounts by a chartered accountant

3. Sales and CRM

  • [ ] Advance collected before a registered agreement for sale capped at the legal limit (10% of cost), with the system blocking further demands until the agreement is registered
  • [ ] Agreement for sale generated from the state's prescribed model format, with approved clause changes tracked
  • [ ] Payment demands tied to construction milestones, not arbitrary dates
  • [ ] Interest calculation for delayed payments applied equally to buyers and developer delays, at the rate your state rules prescribe
  • [ ] Unit allotment history with a full audit trail, so no unit can be sold twice
  • [ ] Cancellation and refund workflows with timelines and deductions as per the agreement and state rules

4. Marketing and disclosures

  • [ ] Every advertisement, brochure, landing page, and listing shows the RERA registration number and the authority's website (and QR code where your state mandates it)
  • [ ] Marketing approvals workflow that checks for registration details before anything goes live
  • [ ] Specifications and amenities in marketing match the registered project details
  • [ ] Registered real estate agents only, with their RERA agent numbers stored and verified

5. Periodic filings and updates

  • [ ] Quarterly progress updates prepared from live project data: units booked, construction status, approvals received
  • [ ] Filing calendar per project and state, with reminders ahead of each deadline
  • [ ] Annual reports and audited statements stored and linked to the relevant project
  • [ ] Record of every submission to the state portal, with dates and acknowledgements

6. Post-possession obligations

  • [ ] Structural defect complaints logged and tracked through the five-year defect liability period
  • [ ] Handover of common areas and documents to the association of allottees recorded
  • [ ] Occupancy and completion certificates attached to project records

7. Data, security, and audit

  • [ ] Role-based access: sales cannot alter collections, finance cannot alter allotments
  • [ ] Immutable audit logs on payments, allotments, and withdrawals
  • [ ] Buyer personal data handled under India's DPDP Act, including consent and retention rules
  • [ ] Regular backups and a tested restore process

Red flags

  • Collections and RERA account transfers done manually after month end
  • Brochures and landing pages published without a registration number check
  • Quarterly updates compiled from spreadsheets by one person
  • CRM and ERP holding different unit statuses

How to use this checklist

Review it with finance, sales, marketing, and legal. For every unchecked item, note whether the gap is a process problem, a configuration change in your existing ERP or CRM, or a missing capability. The last category is where investment is needed.

How Syslabs helps

Syslabs builds custom ERP and CRM workflows for real estate developers, including automated 70/30 account splits, filing calendars, and disclosure checks, and offers compliance and risk consulting to map state rules into system controls. For buyer data and transaction platforms, see our data security and compliance checklist.