Yardi's property management software features go far beyond what most teams actually use. After hundreds of Yardi Voyager implementations and optimization projects, we have a clear picture of which underutilized Yardi property management features deliver the fastest payoff once they are properly configured. These are not add-on modules that require a new contract. They are capabilities already included in your license that need the right setup to start working for you and maximizing the return on your Yardi investment.
If you are new to the platform, our aptly named What Is Yardi guide covers the full product ecosystem. The features below assume you are running Voyager or Breeze Premier and want to get more out of what you already have.
Key Takeaways
- Financial Analytics Notes and custom account trees are the two most consistently underutilized features across our client base
- Automated lease renewals and workflow approvals eliminate the manual steps where most data entry errors originate
- YSR reporting has replaced SSRS as the standard for custom Yardi reports, and most teams have not made the switch
- RentCafe's online leasing and resident screening tools share Voyager's database with zero sync lag
- Utility billing via RUBS can recover costs that currently come out of your NOI
Yardi Tips: 10 Features Worth Configuring Today
1. Financial Analytics Notes
Financial Analytics is one of Voyager's most praised capabilities, but the Notes feature within it goes largely unused. Notes let you attach contextual annotations directly to financial data: variance explanations, one-time expense justifications, and period-over-period commentary that lives alongside the numbers rather than in a separate email thread or spreadsheet.
This matters during budget reviews and audits. Instead of digging through old emails to remember why insurance spiked in Q3, the explanation is right there on the line item. Notes are visible to anyone with Financial Analytics access, which means your accounting team, asset managers, and ownership all see the same context.
What we see clients get wrong: Teams treat Financial Analytics as read-only. They run the variance report, export it to Excel, and annotate it there. The problem is that those annotations die with the spreadsheet. Entering notes directly in Yardi keeps the institutional knowledge inside the system where it persists across reporting periods. Our full walkthrough of Financial Analytics Notes in Yardi covers the setup and best practices.
2. Custom Account Trees
Your chart of accounts is fixed. It reflects your legal entity structure, your accounting conventions, and probably some decisions made during implementation that nobody wants to revisit. Custom account trees let you create alternative reporting hierarchies on top of that fixed structure without changing a single GL account.
A common use case: your COA groups expenses by department, but ownership wants to see them grouped by cost category. Instead of maintaining a manual mapping spreadsheet, you build an account tree that reorganizes the same GL data into the hierarchy ownership expects. Multiple trees can coexist, each serving a different audience.
What we see clients get wrong: Teams either do not know account trees exist or they set one up during implementation and never update it. Account trees should evolve with your reporting needs. When you acquire a new property or restructure entities, the trees need to reflect that change. Our guide to Yardi chart of accounts setup and best practices covers common mistakes and how to fix them.
3. Automated Lease Renewals
Manual lease renewals create two problems: the administrative burden of generating notices and agreements one by one, and the risk that renewals slip through the cracks entirely. Yardi's automated lease renewal feature generates renewal notices and lease agreements based on criteria you define (days before expiration, rent increase percentage, property type) and routes them through your approval process.
The configuration lives under Lease Settings in the property setup. You set the renewal window (typically 60 to 90 days before expiration), define rent increase rules (flat dollar amount, percentage, or CPI-based), and choose whether the system generates offers automatically or queues them for manual review. For Voyager 8 users, the Renewals Dashboard provides a consolidated view of all pending, sent, and accepted renewals across your portfolio.
What we see clients get wrong: Configuring the renewal automation without testing it against edge cases. Month-to-month residents, tenants with special renewal terms, and commercial leases with CPI escalations all need their own renewal rules. A single set of criteria across all lease types leads to incorrect offers going out to tenants.
4. YSR Custom Reporting
If your team is still building custom reports in SSRS (SQL Server Reporting Services), it is time to migrate. Yardi Spreadsheet Reporting (YSR) replaced SSRS as the standard for custom Yardi reporting, and Microsoft has discontinued SSRS from SQL Server 2025 onward. YSR uses native Excel and Word templates instead of the RDLC files that required Visual Studio, which means report development is accessible to anyone comfortable in Excel.
YSR datasets pull from three sources: Custom Financial Analytics queries, standard analytics data, and SQL scripts. Reports run inside Voyager, inherit its security model, and can be scheduled for automatic distribution. The output goes directly to Excel, PDF, or Word, eliminating the export-and-reformat step that eats hours every reporting cycle.
What we see clients get wrong: Trying to replicate their SSRS reports line-for-line in YSR. The template format is different, and what worked in RDLC often is not the best approach in Excel. Use the migration as an opportunity to simplify. Many clients find they can replace three SSRS reports with a single YSR report that handles all three use cases. Our custom reporting team handles this transition regularly.
5. Mobile Maintenance Management
Yardi's Maintenance IQ module puts work order management on your maintenance team's phones and tablets. Technicians can receive assignments, update status, log time and materials, attach photos, and close work orders without returning to the office. Residents submit requests through the RentCafe portal, and those requests flow directly into Voyager as work orders with no manual data entry in between.
The mobile interface also supports the make-ready board, which tracks every task required to turn a unit after move-out. Painting, cleaning, carpet replacement, appliance checks: each task gets assigned to a technician or vendor, and the community manager sees real-time progress from their dashboard. This replaces the clipboard-and-spreadsheet approach that most teams default to during heavy turnover seasons.
What we see clients get wrong: Deploying mobile maintenance without configuring work order categories and priority levels first. If everything comes in as "General Maintenance" with no priority flag, the mobile tool becomes a digital version of the same disorganized process. Define your category hierarchy and priority rules before rollout.
6. Advanced Budgeting and Forecasting
Voyager's budgeting tools go well beyond entering line-item estimates for next year. Advanced Budgeting lets you incorporate lease-level revenue projections (future rent, recoveries, escalations) alongside expense assumptions. You can model occupancy scenarios, project renewal probabilities by unit type, and compare multiple budget versions side by side.
Voyager 8 adds the Report Builder for budget-to-actual dashboards that property managers can configure without consultant help. Combined with Financial Analytics, you can drill from a budget variance down to the individual transaction that caused it, all within one interface. For organizations that previously exported budget data to Excel for analysis, this eliminates an entire manual workflow.
What we see clients get wrong: Building budgets in Excel and importing them into Yardi as a flat file. This strips out the lease-level assumptions and forecasting logic, reducing the budget to a static target that cannot be refreshed when conditions change. Build your budgets inside Yardi to preserve the connection between assumptions and projections.
7. RentCafe Online Leasing
RentCafe is not a bolt-on marketing website. It shares Voyager's database, which means unit availability, pricing, floor plans, and specials update in real time without any sync or export. Prospects can search available units, submit applications, upload documents, and sign leases electronically. Every step posts directly to Voyager.
The full RentCafe platform extends beyond listing units. CRM IQ tracks every prospect interaction across email, text, phone, and chat. Chat IQ handles after-hours inquiries with AI-powered responses drawn from your actual property data. The communication history follows the prospect from first inquiry through move-in, giving your leasing team full context at every touchpoint.
What we see clients get wrong: Using RentCafe only for rent payments while maintaining a separate CRM and a separate property website. You end up with three systems holding prospect data when one would do. The value of RentCafe compounds when you consolidate your marketing site, CRM, leasing workflow, and resident portal into the single platform that already talks to your accounting system.
8. Workflow Approvals
Yardi's approval workflow engine handles more than AP invoice approvals. It can route lease changes, purchase orders, journal entries, budget amendments, and vendor setup through multi-level approval chains with conditional logic. You define who approves what, set dollar thresholds that trigger additional review levels, and configure escalation paths for when approvers are unavailable.
The Preferred Approver setting assigns specific approval chains based on criteria like vendor, property, or expense category. Delegation rules handle vacations and role changes without manual intervention. Our guide to workflow approvals in Yardi covers how to configure delegation for employee absences without creating security gaps.
What we see clients get wrong: Building a single approval workflow for all transaction types. AP invoices, lease modifications, and journal entries have different risk profiles and should have different approval thresholds. A $500 maintenance invoice and a $500,000 capital expenditure should not follow the same path.
9. Integrated Resident Screening
Yardi's resident screening runs background checks, credit assessments, criminal history, and rental history verification directly within the leasing workflow. When a prospect applies through RentCafe, the screening process triggers automatically. Results post to the applicant record in Voyager with a recommendation (approve, conditional, deny) based on criteria you configure.
The value is not just the screening itself; it is the elimination of context-switching. Your leasing team does not need to log into a separate screening platform, manually enter applicant data, wait for results, and then return to Voyager to update the record. The entire process happens in one system, and the screening results become part of the permanent applicant file.
What we see clients get wrong: Using the default screening criteria without tailoring them to the property and local regulations. Fair housing laws vary by jurisdiction, and some screening criteria that are standard in one state may be restricted in another. Review your screening criteria with legal counsel and configure Yardi to reflect your specific compliance requirements.
10. Utility Billing and RUBS
If your properties do not have individual utility meters for each unit, you are likely absorbing utility costs that could be allocated to residents. Yardi's utility billing module supports both submetered billing (based on actual usage from individual meters) and RUBS (Ratio Utility Billing System), which allocates costs based on unit square footage, occupancy, or a combination of factors.
The module calculates allocations automatically each billing cycle, generates resident charges, and posts them to Voyager. It handles mid-month move-ins and move-outs with prorated calculations, and it produces the backup documentation that residents inevitably request when they see a utility charge on their statement.
What we see clients get wrong: Choosing between RUBS and submetering based on cost alone. Submetering is more accurate but requires hardware investment and ongoing meter maintenance. RUBS is simpler to implement but can feel arbitrary to residents, especially in units with very different usage patterns. The right choice depends on property type, local regulations (some jurisdictions restrict RUBS), and how much variance exists between units.
Yardi Tips FAQ
What are the most underutilized features in Yardi Voyager?
Based on our consulting work across hundreds of Yardi installations, the most consistently underutilized features are Financial Analytics Notes, custom account trees, and automated workflow approvals. These three are included in standard Voyager licenses but require deliberate configuration to activate. Most teams either do not know they exist or received a brief overview during implementation that did not stick.
How can I get more out of my Yardi system without buying new modules?
Start with the features already in your license. Financial Analytics Notes, custom account trees, approval workflows, and the report scheduler are available to every Voyager user. If you have RentCafe, confirm that online leasing, resident screening, and Chat IQ are fully configured. Most "underperforming" Yardi installations are not missing features; they are missing configuration.
What Yardi features help reduce manual work for property managers?
The biggest time savers are automated lease renewals (eliminates manual notice generation), workflow approvals (routes transactions without email chains), Maintenance IQ (mobile work orders instead of paper), RentCafe online leasing (applications flow directly to Voyager), and utility billing automation (RUBS calculations post without spreadsheet math). Each one removes a manual step where data entry errors typically originate.