Filing DHCR annual registration in ORRA / ARRO is not just a login task. It is the final step in a data-readiness workflow that starts with building records, apartment records, tenant data, lease status, rent fields, user access, and internal review ownership.
This guide is written for owners, managing agents, property managers, finance leaders, compliance teams, and Yardi administrators responsible for preparing annual rent registration. It is not legal advice and does not replace HCR rent registration instructions, HCR's ARRO FAQ, or counsel. It is a practical operations guide for getting the right data clean before filing.
Key Takeaways
What owners should know before logging in
ORRA is the owner application environment; ARRO is the Annual Rent Registration Online application used for annual registration.
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 registrations for registration years 2001 onward are filed online using ARRO after initial registration is already on file.
Before filing, teams should confirm provider access, building registration numbers, apartment records, tenant status, rent fields, and internal approval ownership.
The best use of Yardi is upstream: clean the source records, validate the report logic, review exceptions, and preserve submission evidence.
Chapter 1
ORRA vs. ARRO
ORRA stands for Owner Rent Regulation Applications. It is the owner application environment that gives owners and designated users access to rent-regulation applications. ARRO stands for Annual Rent Registration Online. It is the annual registration application inside that owner application environment.
That distinction matters because many filing problems start before the annual registration screen appears. Someone must have the right user ID, provider information, building access, and internal authority to work inside ORRA. Then the annual registration work happens in ARRO.
HCR's rent registration materials describe annual registration as an online ARRO process for registration years 2001 onward after initial registration is already on file. Initial registration is a separate process and should not be blended into this annual-registration workflow.
Plain-English distinction: ORRA is the doorway. ARRO is the annual registration room. Your team's preparation work should start before anyone is standing in that room trying to finish the filing.
Chapter 2
Before You Log In
Before logging into ORRA, the team should confirm who owns the filing, who controls access, which buildings are in scope, which apartment records need review, and which report will be used as the source of truth. The login is not the beginning of the process; it is where preparation gets tested.
HCR's ARRO FAQ explains that access requests involve provider and user information, including the email address that will be associated with the ORRA account. It also explains the provider-code concept and notes that buildings and apartments can be associated under a provider code for access and filing purposes. Owners should confirm current access requirements directly with HCR before filing.
For a Yardi team, the pre-login work usually means pulling a rent-stabilized registration review report, checking exception records, and deciding which corrections belong in the source system before filing data is entered or uploaded. If a correction lives only in a spreadsheet, the same issue may return next year.
Pre-login questions to answer
Who owns ORRA/ARRO access for the organization?
Which provider code or user setup applies to this portfolio?
Which building registration numbers are required for this year's filing?
Which report or export will be treated as the source of truth?
Who reviews rent, lease, tenant, exemption, and status exceptions?
Who has authority to approve the final filing?
Chapter 3
The ORRA / ARRO Filing Workflow
HCR's ARRO FAQ lays out a general filing flow: log into ORRA, open the Annual Rent Registration application, choose the registration year, add or select the building, complete building details, move into apartment records, review the building and apartment information, and submit through the certification screen.
Owners should treat those steps as the public filing sequence, not as a substitute for internal review. By the time the team is choosing the registration year and working through the building and apartment screens, source data should already be reviewed and exceptions should already have an owner.
1. Access ORRAConfirm the correct owner, managing agent, or assigned user has access before the filing window gets crowded.
2. Open ARROUse the Annual Rent Registration Online application for annual registration after initial registration is on file.
3. Select year and buildingChoose the registration year and confirm the building registration number and building status.
4. Complete building detailsReview building-level owner, provider, address, service, and status information against internal records.
5. Complete apartment recordsReview each apartment record for tenant, status, rent, lease, exemption, and required detail fields.
6. Review and submitUse the review step before certification. Retain submission evidence and exception records after filing.
Chapter 4
Building List and Building Detail Checks
The Building List and Building Detail steps are where portfolio scope and ownership assumptions show up. If the wrong building is selected, a registration year is missing, a building registration number is unknown, or provider information is stale, the filing can slow down before the apartment-level work even begins.
HCR's ARRO FAQ notes that owners can use the Rent Regulated Building Search to help locate a building registration number and that the Building List status can help users sort records. For teams managing multiple buildings, those details are not clerical. They are portfolio-control checkpoints.
Before the team starts editing annual registration details, compare the Building List against your internal portfolio list. Confirm which buildings are active, which changed ownership or management responsibility, which have newly stabilized units, and which records need escalation before submission.
Building-Level Item
What to Check
Why It Matters
Building registration number
Confirm each building can be identified before filing begins.
Missing or mismatched building IDs can delay the filing sequence.
Provider and user access
Confirm who can access, edit, review, and submit records.
Access problems become deadline problems when they are found late.
Ownership and address records
Review owner name, address, agent, and contact information.
Stale owner records can create downstream correction work.
Building status
Check whether the building is in progress, submitted, or missing from the expected list.
Status review helps the team track completion across a portfolio.
Chapter 5
Apartment Detail Checks
Apartment Detail is where annual registration becomes operationally demanding. Each apartment record may depend on tenant status, occupancy, lease dates, legal regulated rent, preferential rent, exemption status, improvements, special program history, and records maintained by different teams.
The safest process is to review apartment records before the filing screen is open. That review should identify blanks, stale statuses, unexpected deregulated units, rent-field inconsistencies, spreadsheet adjustments, and records that need compliance or counsel review before submission.
If Yardi is the operating system of record, the apartment-level review should be tied back to Yardi fields and reports. Do not let annual registration become a separate spreadsheet process that never cleans the system. The more corrections flow back into source records, the easier the next filing cycle becomes.
Apartment-level records to review
Apartment identifiers and unit status.
Tenant and occupancy status as of the registration snapshot.
Lease dates, renewal status, and related renewal forms.
Legal regulated rent and preferential rent where applicable.
Permanent exemption, temporary exemption, or program-specific statuses.
Spreadsheet corrections made outside the system during prior filings.
Chapter 6
Review, Certification, and Submission
Review and certification should be treated as control points, not afterthoughts. HCR's ARRO FAQ references reviewing building and apartment information before submission and submitting through a certification screen. Internally, owners should decide who reviews the data, who resolves exceptions, who certifies the filing, and where the final record is retained.
That matters because annual registration often reveals prior-year process issues. A record may be technically ready to submit, but the team may still need to answer whether an unexpected value is a true source-system correction, a reporting issue, a legal question, or a workflow problem.
Before certification, create a final review package. It does not need to be ornate. It should identify the source report, the exception log, who reviewed exceptions, which items were escalated, what was corrected in Yardi, and where proof of submission will be stored after the filing is complete.
Control point: If the person certifying the filing cannot explain where the data came from, who reviewed it, and where exceptions were resolved, the process is not ready enough.
Chapter 7
Common Filing Problems Owners Run Into
Most ORRA/ARRO filing problems are not mysterious. They come from access gaps, missing building IDs, stale provider information, inconsistent apartment records, unclear ownership of exceptions, or late discovery that source reports do not match the filing workflow.
HCR materials should be the source for application-specific questions, login issues, access requirements, amendments, add-ons, and current filing instructions. Use HCR's Owners and Managers page, Tenant/Owner Forms, Owner Rent Regulation Applications, and Rent Registration page for current agency context. Internally, the team should separate agency questions from operational questions. That separation keeps everyone from blaming the filing system for problems that actually live in data governance, reporting, or review ownership.
Problem
Likely Root Cause
Operational Response
User cannot access the right filing area
ORRA account, provider, or user setup issue
Confirm account ownership and HCR access instructions early.
Building is missing or not expected
Portfolio scope, registration ID, ownership, or provider mismatch
Compare Building List to internal portfolio records before filing.
Apartment records do not match reports
Source-system data, report logic, or spreadsheet edits
Fix source records and document any reviewed adjustments.
Rent fields create uncertainty
Legal rent, preferential rent, renewal, or increase assumptions
Escalate before submission and preserve the decision trail.
Submission is technically complete but not auditable
No exception log or retained submission record
Retain source report, final review, and proof of filing.
Chapter 8
Where Yardi Data Needs to Be Clean
Yardi is an ideal tool to support ORRA/ARRO filing preparation when the underlying records, reports, roles, and review process are maintained. The annual registration filing does not start inside ARRO. It starts in the operating data owners rely on before filing.
The most important Yardi work is not cosmetic. It is making sure rent-stabilized unit records, tenant records, lease dates, rent fields, exemption flags, user roles, and reporting extracts are aligned before final filing. If custom reports are used, their logic should be reviewed against the current registration workflow and current portfolio structure.
This is also where internal ownership matters. Property management may know unit status. Accounting may know rent fields. Compliance may know exemption or rider questions. System administrators may know where fields live and how reports are built. The annual registration process needs all of those perspectives before submission.
Confirm rent-stabilized unit flags and apartment status.
Review tenant records, lease dates, and renewal status.
Validate legal regulated rent and preferential rent fields.
Check custom report logic before using it as a filing source.
Review user roles and approval ownership before the deadline.
Move repeat corrections back into Yardi wherever possible.
Chapter 9
ORRA / ARRO Readiness Checklist
Use this checklist before treating annual registration as ready for entry or upload. The goal is to reduce filing friction and make the process more repeatable every year.
Confirm the person responsible for ORRA/ARRO access.
Confirm provider information, user access, and internal filing ownership.
Identify every building expected to be filed for the registration year.
Confirm building registration numbers and building-level information.
Pull the source Yardi report or export before entering filing data.
Review apartment status, tenant status, lease dates, and rent fields.
Separate data corrections from items requiring compliance, ownership, or counsel review.
Resolve source-system corrections before relying on a final spreadsheet.
Review final building and apartment records before certification.
Retain submission evidence, source reports, and exception notes after filing.
FAQ
ORRA / ARRO Annual Registration FAQ
What is ORRA?
ORRA stands for Owner Rent Regulation Applications. It is the owner application environment used to access rent-regulation applications, including annual registration.
What is ARRO?
ARRO stands for Annual Rent Registration Online. HCR's ARRO FAQ describes ARRO as the online system used for annual rent registration after initial registration is on file.
Is this the same as the DHCR annual rent registration deadline page?
No. The deadline page answers when annual registration is due and what owners should prepare before the deadline. This page focuses on the filing workflow: ORRA access, ARRO sequence, building records, apartment details, review, submission, and Yardi data readiness.
What should owners prepare before filing in ARRO?
Owners should prepare ORRA access, provider information, building registration numbers, apartment records, tenant and lease data, legal regulated rent, preferential rent where applicable, exemption status, and an internal review process before filing.
How does ARRO filing connect to Yardi?
ARRO filing depends on clean building, apartment, tenant, lease, rent, and status data. Yardi can support that process when reports, fields, user permissions, and review workflows are maintained before filing.
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.
BC Solutions helps Yardi users prepare source reports, clean apartment and tenant records, validate rent fields, review exceptions, and align teams before deadline-driven annual registration work begins.
