Yardi Voyager Common Errors and How to Fix Them Fast

Yardi Voyager is a powerful platform, and complex enough that even experienced users hit errors and unexpected behavior in their day-to-day work. Most of these issues are not bugs. They come from configuration settings that don’t quite match the workflow being attempted, data conditions the system was not set up to handle, or permissions that need adjustment.

This guide covers the errors and problems that Yardi Voyager users encounter most frequently, organized by the area of the platform they occur in. For each issue, we describe what causes it and how to resolve it. Where resolution requires system administrator access or configuration changes that should involve a consultant, we say so clearly.

Accounting and Financial Errors

Issue: Rent Payment Posts to Wrong Property or Ledger

This typically occurs when a tenant’s unit assignment is incorrect in the system or when the lease record has a property code that does not match the intended property. It can also occur when a payment is applied manually to the wrong account during entry.

Resolution: Review the tenant’s lease record and confirm the property and unit assignment are correct. Check the chart of accounts to confirm the income category being used is the right one for that property type. If the posting has already occurred, a journal entry reversal is needed. For a recurring issue affecting multiple tenants, this is likely a configuration problem in the chart of accounts or property setup that requires administrator review.

Issue: Bank Reconciliation Will Not Balance

A reconciliation that refuses to balance is usually caused by an amount mismatch between Yardi and the bank, a bank-originated entry (fees, interest, NSF, ACH credits) that was not recorded in Yardi, a duplicate posting in Yardi, or a voided transaction in Yardi that the bank still shows as cleared. Outstanding items (transactions recorded in Yardi but not yet cleared at the bank) are normal and will show up in the workspace, but they should not prevent the reconciliation from balancing.

Resolution: Work through the outstanding items list systematically. Sort by transaction date and compare against your bank statement line by line. Voided transactions in Yardi that cleared the bank need to be investigated with your accountant before any correction is made. Transactions that are in the bank but not in Yardi need to be posted. Do not force a reconciliation to balance by adjusting the opening balance. That creates a discrepancy that compounds forward.

Issue: Owner Statement Shows Incorrect Balance

Incorrect owner statement balances are most commonly caused by a management fee configuration error, an incorrectly applied charge or credit on the owner’s account, or a previous disbursement that was posted to the wrong period.

Resolution: Pull the owner ledger for the affected period and review it transaction by transaction. Compare each entry against what it should show based on the rent collected, the expenses incurred, and the management fee terms in the management agreement. If the error is in the management fee calculation, this is a configuration setting that your Yardi administrator needs to review.

Leasing and Tenant Record Errors

Issue: Lease Renewal Not Appearing in the Renewal Queue

Leases that should appear in the renewal queue but do not are usually caused by one of two things: the lease end date is not set correctly in the system, or the unit’s lease type is set to month-to-month rather than fixed term, which changes how Yardi handles the renewal workflow.

Resolution: Pull the lease record directly and confirm the end date. Check the lease type setting. If the lease end date is correct and the lease type is fixed term, check your renewal queue configuration to confirm the look-ahead window is set to capture leases expiring within the expected range. In Yardi Voyager, the renewal queue look-ahead period is a configurable setting that varies between implementations.

Issue: Online Application Not Linking to Correct Property

When a prospective tenant submits an application through RentCafe and the application does not appear linked to the correct property or unit in Voyager, the most common cause is a mismatch between the property code in RentCafe and the corresponding property code in Voyager. This can also occur when a unit is marked as unavailable in one system but available in the other.

Resolution: Check the property and unit availability status in both Voyager and RentCafe. Confirm that property codes match between the two systems. If applications are consistently going to the wrong property, this is a RentCafe configuration issue that requires your system administrator or consultant to resolve in the integration settings.

Issue: Tenant Balance Showing Incorrect Amount on Portal

When the balance shown in the tenant’s RentCafe portal does not match the balance in Voyager, the most common causes are a sync delay between the two systems, scheduled charges that are due to post but have not yet been processed in Voyager, or a cached portal session showing stale data. Payments made in Voyager take a short time to reflect in RentCafe. If the discrepancy persists for more than a few hours after the tenant has logged out and back in, it indicates a sync issue.

Resolution: Check the sync status between Voyager and RentCafe in your integration settings. If the sync log shows errors, contact Yardi support with the specific error codes. If the sync appears to be running but balances are still mismatched, this is a configuration issue requiring technical review.

Maintenance Module Errors

Issue: Work Order Not Routing to Correct Vendor

Work orders that do not route to the expected vendor are usually caused by vendor assignment rules that have not been configured correctly, or by a service category that does not have a default vendor assigned. In some implementations, vendor routing is manual rather than automated, which means someone needs to assign the vendor at the time the work order is created.

Resolution: Review the service category configuration for the type of work order that is failing to route. Check whether a default vendor is assigned to that category for the property in question. If your implementation uses geographic or property-level vendor assignments, confirm that the vendor record includes the correct service areas. If routing should be automated but is not, your Yardi administrator needs to review the routing rules configuration.

Issue: Completed Work Orders Not Posting Cost to Ledger

When a work order is marked complete but the cost is not posting to the property expense ledger, it is typically because the work order was not linked to a purchase order, the purchase order was not approved, or the expense account mapping for that service category is not configured. This applies to implementations using the PO-driven workflow. Clients who post work order costs through direct vendor invoices or the invoice register should check invoice approval status instead.

Resolution: Check whether the work order has an associated purchase order and whether that purchase order is in approved status. Check the expense account mapping for the service category in your system configuration. If work order costs are consistently not posting, this is a configuration gap in the expense account mapping that your administrator needs to address.

Reporting Errors

Issue: Report Shows No Data or Incorrect Date Range

Reports that return no data when data clearly exists are almost always caused by a filter or date range that has been set incorrectly, a property selection that is too narrow, or a status filter that is excluding active records. In Yardi Voyager, report parameters are highly configurable and easy to set incorrectly.

Resolution: Review every filter parameter on the report. Pay particular attention to date range, property selection, and any status filters. For custom reports, check whether the base parameters were saved with defaults that do not match your intended use. If a report was working correctly and has stopped returning data, check whether any underlying data configuration has changed.

Issue: Financial Report Totals Do Not Match Expected Values

When financial report totals do not match what you expect based on your records, the most common causes are: the report is pulling data from a broader property set than intended, a transaction was posted to an unexpected account, or the chart of accounts has been modified since the report was last reviewed.

Resolution: Drill into the report totals to identify which property or account is producing unexpected numbers. Compare the chart of accounts against your expected structure to see if any accounts have been added, modified, or reassigned. If totals are consistently incorrect across multiple report runs, involve your Yardi administrator to review the report configuration and the underlying chart of accounts structure.

User Access and Permissions Errors

Issue: User Cannot Access a Module or Function They Should Have

Access issues in Yardi Voyager are controlled by security roles. When a user cannot access a function they need for their job, it means their security role does not include that function, or they have been assigned the wrong role.

Resolution: Your Yardi system administrator needs to review the user’s assigned security role and compare it against the permissions required for the function in question. Avoid granting broad administrative permissions to resolve a specific access gap. The correct approach is to either adjust the existing role or assign the user an additional role that covers the needed functions.

Issue: User Getting Locked Out After Login Attempts

Yardi Voyager locks accounts after a configurable number of failed login attempts as a security measure. This is expected behavior, not a system error.

Resolution: Your Yardi system administrator can unlock the account from the user management section of the system. If this is occurring repeatedly for the same user, it usually indicates they are attempting to log in with incorrect credentials. Resetting the password is the appropriate solution rather than repeatedly unlocking the account.

When to Involve a Consultant

The issues described above are resolvable at the user or administrator level. But there is a category of Yardi problems that require consultant involvement: issues that involve changes to the chart of accounts, changes to the entity or property configuration, problems that are affecting financial data integrity, and persistent issues that have not resolved after standard troubleshooting steps.

The reason to involve a consultant rather than attempting these changes yourself is not that the changes are technically inaccessible. It is that configuration changes in a live Yardi environment with real financial data carry risk. An incorrect change to the chart of accounts can affect the historical categorization of transactions. An incorrect entity configuration change can affect reporting across the portfolio. Involving someone who has made and reviewed these changes before reduces the risk of making a change that creates a larger problem than the one you started with.