A practical filing-readiness guide for NYC owners, property managers, and Yardi teams preparing rent-stabilized apartment data before the annual DHCR registration deadline.
DHCR annual rent registration is a recurring operational deadline for owners and managers of rent-regulated buildings. According to HCR's ARRO FAQ, annual registrations are accepted starting April 1 of the registration year and must be submitted no later than July 31 of the registration year. For 2026 planning, that means the practical work should start well before July.
This guide is written for owner-side teams, managing agents, property managers, finance leaders, and Yardi administrators. It is not legal advice and it does not replace HCR rent registration instructions or counsel. The goal is narrower and more practical: help your team understand what needs to be clean before filing, where Yardi data often breaks down, and how to avoid treating registration as a last-minute form exercise.
Key Takeaways
What owners should know before the deadline
HCR's ARRO FAQ says annual registrations are accepted beginning April 1 and must be submitted no later than July 31 of the registration year.
Annual registration reports the April 1 status of the building and apartments after initial registration is already on file.
The hardest part is usually not the deadline itself. It is reconciling unit status, rent fields, lease data, tenant records, exemptions, and review ownership before filing.
Owners should confirm ORRA access, building registration numbers, user roles, source reports, and exception ownership before the July filing crunch.
Lease renewals, lease riders, Rent Guidelines Board increases, legal rent, and preferential rent should be reconciled before submission because annual registration relies on those records.
Chapter 1
The 2026 Annual Registration Deadline
DHCR annual rent registration is due no later than July 31 of the registration year, based on HCR's current ARRO FAQ. The filing period opens April 1, and the registration reports the April 1 status of covered rent-regulated buildings and apartments. Owners should confirm current HCR rent registration instructions before filing.
That window creates a natural operating rhythm. By April 1, the portfolio snapshot matters. By July 31, the submission needs to be complete. In between, teams need enough time to verify building records, apartment status, legal regulated rents, preferential rent fields, tenant data, exemption status, owner information, and any records that require additional review.
The mistake is waiting until July and treating registration as a clerical task. A large NYC portfolio may have hundreds or thousands of apartment records, and a small inconsistency can become a review bottleneck if no one owns the correction path. Registration readiness should be a cross-functional workflow between operations, compliance, accounting, and the system administrator.
Operational note: Use the deadline as the forcing function, but manage the work as a data-readiness process. The filing is only as clean as the building, unit, tenant, lease, and rent records behind it.
Chapter 2
What Annual Rent Registration Reports
Annual rent registration reports the April 1 status of each covered building and apartment for the registration year. HCR's ARRO FAQ distinguishes initial registration from annual registration: after initial registration is on file, annual registrations are filed online through ARRO for later registration years.
For owners and property managers, the practical question is not only "What form do we file?" It is "Does our system accurately reflect the regulated portfolio as of the snapshot date?" If unit status, tenancy, rent amounts, exemptions, or ownership information are not aligned, the filing process can expose problems that already existed in the source data.
This is why annual registration belongs inside the broader operating calendar. It touches leasing, renewals, legal regulated rent, preferential rent, ownership records, unit history, and reporting. It also touches internal controls because someone has to certify the filing, track what was submitted, and preserve proof of what changed.
Workflow Area
What the Team Should Confirm
Why It Matters
Building records
Building ID, ownership, address, provider access
Incorrect building setup can delay filing.
Apartment records
Unit status, apartment identifiers, exemption flags
Unit-level mismatches create registration errors.
Tenant and lease data
Occupancy, lease dates, renewal status
Lease records support rent and status reporting.
Rent fields
Legal regulated rent and preferential rent where applicable
Rent data affects compliance records and later review.
Review controls
Approver, certifier, evidence, submission log
Submission should be traceable after filing.
Chapter 3
What Owners Should Prepare
Owners should prepare annual registration by confirming building access, apartment lists, tenant status, rent fields, ownership information, and review responsibilities before entering or uploading data. The safest process separates source-data cleanup from final submission so teams do not discover preventable issues at the deadline.
At minimum, the team should know which person controls ORRA/ARRO access, which buildings are in scope, which apartments require review, and which internal report will be used as the source of truth. If the portfolio changed ownership, added regulated units, completed construction, or changed management responsibility, those transition points should be checked early.
In a Yardi environment, the preparation work often starts with a source-data extract. That extract should not be treated as final just because it came from the system. It should be reviewed for blanks, stale statuses, rent-field inconsistencies, missing tenant records, unexpected deregulated units, odd lease dates, and records that require business review before filing.
Preparation should happen in layers
Portfolio scopeIdentify buildings, apartment records, ownership changes, provider access, and any newly stabilized or exempt units.
Data reviewCheck tenant, lease, legal rent, preferential rent, status, and unit-level fields against internal records.
Exception queueSeparate easy corrections from items that require compliance, accounting, ownership, or counsel review.
Submission controlDocument who approves the final data, who submits, and where proof of submission is stored.
Chapter 4
Where Registration Data Needs Extra Review
Annual registration data often needs extra review around ownership transitions, unit status, lease dates, rent fields, special programs, and spreadsheet-based adjustments. Yardi may contain the right data in pieces, but annual registration requires those pieces to align around a specific April 1 portfolio snapshot.
For NYC owners, the risk is rarely one dramatic system failure. It is a trail of small inconsistencies: a unit marked one way in operations and another way in a reporting extract, a preferential rent field that is not maintained consistently, an ownership change that never made its way into every reporting process, or a spreadsheet that became a separate source of truth.
This is where the team needs a clear review step between system data and submission-ready data. If the export depends on a custom report, the report logic should be reviewed before the deadline. If the filing depends on post-export clean-up, the team should document who performs that clean-up and how corrections flow back into the source system.
Good registration hygiene: When corrections are identified during registration prep, capture them in the source system whenever possible. That way, next year's filing starts from cleaner records instead of last year's deadline spreadsheet.
Chapter 5
When to Use HCR Filing Instructions
Once your building, apartment, tenant, lease, and rent data have been reviewed, the filing itself should follow HCR's current instructions. Start with HCR's Rent Registration page, the ARRO FAQ, and the Owner Rent Regulation Applications page before entering or submitting registration data.
The operational work and the filing instructions are related, but they should not be confused. Your team needs clean source data before submission, and HCR's materials should remain the authority for account access, application steps, filing requirements, forms, amendments, add-ons, and current agency instructions.
If there is a mismatch between your Yardi report, your registration records, and HCR's filing workflow, pause before submitting. Resolve whether the issue is a source-data correction, a reporting extract issue, a user-access problem, or a compliance question that should be reviewed outside the system.
Helps teams locate renewal, rider, registration, and owner forms from HCR.
Chapter 6
Lease, Rider, and Rent Increase Handoffs
Annual registration connects to lease renewals, riders, legal regulated rent, preferential rent, and annual Rent Guidelines Board adjustments. Those workflows can change the records that annual registration depends on, so they should be checked before submission rather than treated as unrelated leasing paperwork.
For example, the NYC Rent Guidelines Board's 2025-26 Apartment/Loft Order #57 applies to rent-stabilized apartment leases commencing between October 1, 2025 and September 30, 2026. Owners should also keep HCR's leases guidance and current forms close at hand when reviewing renewal and rider records.
The same is true for RTP-8 renewal leases and the RA-LR1 lease rider. They affect the operating record that registration depends on, and they should be reconciled against the tenant, lease, and rent fields being used for annual registration.
Related records to check before filing
ORRA/ARRO account access, user permissions, and building registration numbers.
RTP-8 renewal lease dates, renewal terms, and returned tenant responses.
RA-LR1 lease rider records and attachment requirements for NYC rent-stabilized leases.
Legal regulated rent and preferential rent fields in the source system.
Rent Guidelines Board increases that apply to the lease term being reviewed.
Chapter 7
Internal Controls Before Submission
Annual registration should have a simple internal control process: one source report, one exception log, one owner for corrections, one final reviewer, and one retained submission record. Without those controls, the team may submit on time while leaving unresolved data issues behind.
The review process does not need to be complicated. It needs to be repeatable. A portfolio manager should be able to explain which report was used, which records were reviewed, which exceptions were escalated, who signed off on the final data, and where the post-submission evidence lives.
This is especially important when property management, accounting, compliance, and asset management all touch the same records. If the filing team corrects a value only in a spreadsheet, the next report may repeat the same issue. If the correction is pushed back into Yardi with the right review, the next cycle starts from a stronger baseline.
Confirm the registration-year scope and all buildings expected to be filed.
Export the source report early enough to review exceptions before July.
Compare apartment status, tenant records, rent fields, and lease dates.
Separate data corrections from legal or policy questions that require review.
Document who certifies and submits the final registration.
Retain final submission evidence and any exception log used during review.
Chapter 8
Registration Readiness Checklist
A registration readiness checklist helps owners convert a deadline into a managed workflow. The checklist should cover access, scope, source data, exception review, Yardi corrections, submission approval, and post-filing records so the same issues do not return every year.
Confirm ORRA/ARRO access and who controls the active user account.
Confirm each building ID, building status, and ownership record.
Pull a Yardi source report or export before final filing work begins.
Review every rent-stabilized apartment for tenant status, lease dates, rent fields, and exemption status.
Identify records that need business review before any filing data is entered or uploaded.
Resolve source-system corrections in Yardi wherever possible rather than only editing a spreadsheet.
Confirm who approves legal regulated rent and preferential rent fields before submission.
Validate that any custom report logic still matches the current portfolio and filing process.
Retain proof of submission, review notes, and exception decisions in a consistent internal location.
Schedule a post-filing debrief so the next registration cycle starts cleaner.
FAQ
DHCR Annual Rent Registration FAQ
When is DHCR annual rent registration due in 2026?
HCR's ARRO FAQ says annual registrations are accepted starting April 1 of the registration year and must be submitted no later than July 31 of the registration year. Owners should verify current HCR instructions before filing because agency guidance and forms can change.
What is DHCR annual rent registration?
DHCR annual rent registration is the recurring filing used to report the April 1 status of rent-regulated buildings and apartments after initial registration is on file. For registration years 2001 onward, HCR's FAQ describes annual registration as an online ARRO process.
Is ARRO the same as ORRA?
ORRA is the Owner Rent Regulation Applications environment. ARRO is the Annual Rent Registration Online application used for annual registration. In practical terms, owners access the owner application environment and then use the annual registration application for the filing workflow.
What should owners prepare before filing?
Owners should prepare building IDs, apartment records, tenant and occupancy status, legal regulated rent, preferential rent where applicable, exemption status, owner information, and internal review controls. The exact filing requirements should be verified against current HCR instructions.
How does this connect to Yardi?
Annual rent registration depends on clean rent-stabilized unit records, tenant records, lease data, rent fields, reporting extracts, user roles, and review workflows. Yardi is an ideal tool to support those processes when the underlying data and controls are maintained before the deadline.
Sources
HCR Sources to Verify Before Filing
This guide is operational guidance, not legal advice. Owners should verify current filing requirements, forms, and deadlines with HCR sources and counsel before submitting annual registration materials.
Need to get your Yardi data ready before annual registration?
BC Solutions helps Yardi users clean source data, validate reporting logic, prepare exception workflows, and align property management, accounting, and compliance teams before deadline-driven filing work begins.
