Registering a real estate project marks the beginning of ongoing disclosure responsibilities. Developers must also keep project information accurate throughout the development process.
For promoters managing RERA quarterly update tenali requirements, organised records and timely submissions help prevent avoidable compliance gaps.
Each quarterly update should present a clear picture of bookings, construction progress, infrastructure and approvals.
This information helps property buyers assess progress while allowing developers to maintain consistent public disclosures.
What Is a RERA Quarterly Update?
A RERA quarterly update records a registered project’s position at the end of a three-month reporting period.
Section 11(1) requires promoters to update information about bookings, garages, approvals and project status on the authority’s website.
Developers should treat this exercise as a review of actual project records.
A successful submission depends on coordination between the sales team, site personnel, accounts department and professionals responsible for supporting documents.
Copying an earlier submission without checking subsequent developments can create inconsistencies that become harder to explain later.
Which Authority Covers Projects in Tenali?
Projects in Tenali fall under Andhra Pradesh RERA requirements where the applicable registration and reporting obligations apply.
Developers should follow Andhra Pradesh procedures and check their individual project registration details before preparing submissions.
Municipal permissions and RERA reporting serve different purposes. Obtaining a local approval does not replace the responsibility to maintain the project’s RERA disclosures.
Similarly, filing a quarterly update does not authorise construction that departs from sanctioned plans.
For projects with separately registered phases, teams should organise information against the correct registration number rather than combining unrelated records.
When Must Developers Submit Quarterly Updates?
Andhra Pradesh Rule 15(1)(d) requires promoters to upload quarterly updates within seven days after each quarter ends.
The standard reporting calendar follows this schedule:
| Reporting Period | Quarter Ends | Standard Submission Deadline |
|---|---|---|
| January–March | 31 March | 7 April |
| April–June | 30 June | 7 July |
| July–September | 30 September | 7 October |
| October–December | 31 December | 7 January |
These dates reflect the seven-day requirement. Developers should check whether an applicable authority direction changes the deadline for a particular reporting period.
Do not assume that another state’s filing window applies to Tenali.
An earlier extension also does not establish a permanent revised deadline. Keep the relevant official communication with the project’s compliance records.
What Information Should Developers Submit?
The core disclosures cover booked inventory, building and floor progress, internal infrastructure, common areas and approval status.
Andhra Pradesh rules specifically include photographs supporting construction disclosures and information about approval applications, expected receipts and revisions.
The following preparation steps help developers assemble reliable information for those disclosures.
1. Apartment and Plot Booking Details
Start with a reconciled inventory register showing the position at quarter-end.
Check unit identifiers, property types, bookings and cancellations against the project’s records.
A clear working register should distinguish available inventory from booked inventory. Teams should also resolve duplicate entries before transferring figures into the submission.
For example, a cancelled booking may require an inventory adjustment even when the accounts team has not yet completed the refund process.
Record the reason for each adjustment so reviewers can trace the change.
2. Garage and Parking Information
Review garage and parking records separately from apartment or plot bookings.
Check the approved configuration and the project’s existing disclosures before entering updated figures.
Use consistent identifiers across allotment records, plans and internal registers.
If a field does not apply to the project, follow the portal’s permitted treatment rather than entering an invented number.
3. Building and Floor Progress
Prepare a factual description of work completed by the reporting cut-off.
For apartment developments, organise the working information building by building and floor by floor.
Useful internal categories include foundations, structural work, masonry, plastering, services installation and finishing.
Avoid broad statements that conceal differences between blocks.
One building may have completed structural work while another remains at foundation level. The supporting records should make that distinction clear.
4. Internal Infrastructure and Common Areas
Review shared facilities alongside individual buildings or plots.
Prepare progress notes for applicable works such as internal roads, drainage, water supply, electrical infrastructure, landscaping and common facilities.
For a plotted development, infrastructure may provide the clearest evidence of development progress.
Check whether the written description matches the photographs and site records.
A completed entrance feature, for example, does not demonstrate completion of drainage or internal road works across the entire layout.
5. Approval Status
Maintain an approval tracker that separates received permissions from pending applications.
For each relevant item, record the issuing authority, application reference, current position and supporting document location.
Check revised permissions carefully. Teams should identify which document remains operative and which earlier version it replaces.
Avoid describing an application acknowledgement as an approval.
Where a permission remains pending, use a realistic expected timeline supported by available correspondence rather than an unsupported promise.
How Should Developers Prepare Progress Photographs?
Photographs should help a reviewer connect the written update with visible site conditions.
Create a repeatable photography plan covering the same buildings, floors and infrastructure locations each quarter.
Keep original files and record when the site team captured them.
Use clear filenames containing the block, floor or work category. This makes internal checking faster and reduces accidental uploads from another project.
Avoid relying on promotional images, artistic impressions or photographs that no longer represent the reporting period.
Before uploading, check readability, orientation and whether each image actually supports the relevant progress statement.
What About Architect, Engineer and CA Certificates?
Developers should confirm the current AP RERA portal requirements for supporting professional certificates before finalising the filing package.
Do not assume that form numbers or templates used in another state apply automatically.
Coordinate with the project architect, engineer and chartered accountant early enough to address applicable certification requirements.
Provide each professional with the records relevant to their work.
These may include site measurements, progress statements, expenditure schedules, collection records and bank reconciliations.
Resolve differences before submission. A consultant should not alter a signed professional certificate merely to make its figures match another document.
The responsible professional should review and correct any necessary changes.
Which Financial Records Should Teams Keep Ready?
Maintain financial working papers even where the quarterly portal does not request every underlying record.
A useful preparation folder includes buyer collections, expenditure summaries, bank statements, reconciliations and explanations for significant adjustments.
Keep quarter-specific movements separate from cumulative totals.
For example, collections received during the quarter differ from total collections since the project began.
Likewise, expenditure booked in the accounts may require review before a professional uses it for certification.
Clearly label each schedule, identify its reporting period and record who prepared and checked it.
This approach reduces confusion when several departments contribute figures.
How Can Developers Organise the Filing Process?
Step 1: Confirm the Project and Reporting Period
Check the registration number, project name, phase and quarter before collecting information.
Use one reporting cut-off across all departments.
A sales register prepared to one date and a progress statement prepared to another can produce an inconsistent submission.
Step 2: Allocate Responsibilities
Assign an owner for each information category.
The sales team can prepare inventory records, site personnel can document progress, and the approvals coordinator can update permission status.
The accounts team should prepare financial working papers.
Nominate one person to consolidate the package and track outstanding information.
Step 3: Reconcile Supporting Records
Compare the proposed submission with the previous quarter.
Investigate changes in bookings, progress percentages, approval status and other material information.
A change may have a valid explanation, but the project file should contain that explanation before submission.
Step 4: Review Documents and Portal Entries
Check document legibility, signatures, dates and project references.
Compare uploaded attachments with the figures entered into the portal.
A correct attachment cannot resolve an incorrect portal entry if the two present conflicting information.
Step 5: Submit and Preserve Evidence
Complete the applicable submission process and check the resulting status.
Retain the acknowledgement, reference number, uploaded package and relevant confirmation records.
Saving a draft does not demonstrate that the promoter completed submission.
What If There Were No Bookings or Construction Progress?
A quiet quarter still requires an accurate assessment of the project’s reporting position.
Zero bookings do not necessarily mean zero activity across every category.
Construction may continue without new sales. Approval applications may also move forward while physical work remains paused.
Report each category according to the actual facts.
Where information remains unchanged, check it rather than automatically carrying it forward.
If work has stopped, maintain internal records explaining the position and seek advice on any separate compliance action the circumstances require.
What Mistakes Commonly Disrupt Quarterly Filing?
Mixing Quarterly and Cumulative Figures
A field asking for cumulative bookings requires a different figure from one asking for bookings during the reporting period.
Read each field carefully and label working schedules accordingly.
Reusing Old Photographs
Earlier photographs can misrepresent current progress even when the project has changed only slightly.
Refresh the evidence and preserve the originals.
Overlooking Cancellations
Sales teams may focus on new bookings while missing inventory returned through cancellations.
Reconcile both movements before finalising totals.
Combining Separate Phases
Information from one phase may not belong in another phase’s registered project record.
Check registration boundaries before consolidating data.
Leaving Review Until the Deadline
Late preparation leaves little time to correct mismatched figures, missing signatures or unreadable attachments.
Begin preparation before quarter-end, then finalise information using the correct closing position.
What Happens When a Developer Misses the Deadline?
Missing a filing deadline can expose the promoter to regulatory action.
Section 61 permits penalties extending to five per cent of the estimated project cost for covered contraventions, as the authority determines.
That statutory maximum does not mean every delayed update automatically attracts the same penalty.
Check the applicable circular, notice and project circumstances before calculating potential charges.
If a submission remains overdue, identify every outstanding quarter and prepare a separate evidence-based package for each.
Do not attempt to conceal an earlier gap by placing all subsequent activity into one later update.
How Should Developers Handle Portal Problems?
Keep screenshots showing the error, affected project, attempted action and relevant time.
Record any support request or communication with the authority.
Continue preparing the complete submission package while seeking resolution.
Technical evidence can explain the difficulty, but developers should not assume that an error automatically extends the deadline.
Follow the authority’s instructions on any permitted alternative submission route.
Once access returns, complete the required process and preserve confirmation.
Avoid leaving the issue unresolved merely because someone reported it verbally.
How Can Buyers Use Quarterly Updates?
Buyers can compare successive disclosures to assess whether the project’s reported position changes consistently.
Useful comparisons include construction progress, booked inventory and the movement of pending approvals.
Buyers should consider the reporting cut-off when comparing portal information with a later site visit.
A quarterly disclosure describes a particular period; it does not necessarily capture subsequent work.
Questions should identify the exact block, facility or approval concerned.
Specific questions make it easier for the promoter to provide a documented response.
How Can RERA E2E Consultants Support Filing Preparation?
Developers seeking assistance from RERA E2E Consultants should begin with their registration details, previous submissions and current project records.
A clearly defined engagement can cover document coordination, discrepancy tracking, deadline monitoring and submission preparation.
Agree on responsibilities for professional certifications, portal access, final review and record retention before work begins.
The promoter should approve the final information and maintain access to the completed filing package.
Professional support works best when project teams provide accurate records promptly and resolve questions before the submission window closes.
Conclusion
Reliable quarterly reporting starts with disciplined project records.
Tenali developers should track the seven-day filing requirement, reconcile information across departments and verify applicable portal instructions before submission.
Clear photographs, consistent inventory figures and accurate approval records make the process easier to review.
An organised quarterly routine also helps developers identify discrepancies early and maintain credible disclosures throughout project delivery.
FAQs
1. What is the deadline for RERA quarterly update tenali submissions?
The standard Andhra Pradesh requirement is within seven days after quarter-end, subject to any applicable official extension or direction.
2. What information does a RERA quarterly update tenali filing cover?
Core disclosures cover booked apartments or plots, garages or parking areas, construction progress, infrastructure, common areas and approvals.
3. Can developers skip an update when no units sell?
Developers should not treat zero sales as an exemption. Review and report the actual position across all applicable disclosure categories.
4. Can RERA E2E Consultants assist with quarterly update preparation?
Developers can discuss document coordination, reconciliation and submission preparation with RERA E2E Consultants, then confirm the agreed scope and professional responsibilities.