---
title: How does the ElevateOS & Yardi integration work?
description: Learn about the Yardi & Elevated Living integration
---

[Skip to content](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#main-content)

English

Show submenu for translations

![Elevate OS Logo (2)](https://help.elevateos.com/hs-fs/hubfs/REBRAND/Elevate%20OS%20Logo%20(2).png?width=200&height=133&name=Elevate%20OS%20Logo%20(2).png)

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)

Open main navigation

Close main navigation

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)
- English
  
  Show submenu for translations
- Go to app.elevatedliving.com

 Go to app.elevatedliving.com

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Customer Success Portal](https://help.elevateos.com/?hsLang=en)
2. [Integrations](https://help.elevateos.com/integrations?hsLang=en)
3. [PMS - Yardi](https://help.elevateos.com/integrations?hsLang=en#pms-yardi)

# How does the ElevateOS & Yardi integration work?

## Learn about the Yardi & ElevateOS integration

How ElevateOS works with Yardi Voyager: what syncs, how to connect a building, how to use it day to day, and what to check when something does not look right.

*Last updated October 2026. For property management teams, on-site staff, Yardi administrators and IT.*

**On this page:** [Overview](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#overview) | [Requirements](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#requirements) | [Initial setup](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#setup) | [Sync schedule](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#sync) | [Residents and accounts](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#residents) | [Maintenance and work orders](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#work-orders) | [Checklists, inspections, vehicles](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#checklists) | [Rent payments and charges](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#payments) | [Phases and targeting](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#phases) | [Changing your connection](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#changes) | [Troubleshooting](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#troubleshooting) | [FAQ](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#faq) | [What is not covered](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#limits) | [Quick reference](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#reference)

 Overview

ElevateOS connects each building to Yardi Voyager. Yardi stays the place where residents, units, leases and the ledger are maintained. ElevateOS reads that information on a schedule, and sends work orders, photos, checklist answers, inspection PDFs and rent payments back to Yardi.

A building connects to either a single Yardi property or a Yardi group of properties. When a building has more than one property code, ElevateOS calls each one a **phase**.

### At a glance

| Function | Direction | How often | What it does |
| --- | --- | --- | --- |
| Residents and households | Yardi to ElevateOS | 5 times a day | Creates and updates resident accounts, including roommates. Deactivates residents who no longer come back from Yardi. |
| Units and leases | Yardi to ElevateOS | 5 times a day | Keeps units, lease dates and balances in step with Yardi and links residents to their units. |
| Work orders | Both ways | Sent to Yardi right away. Yardi changes arrive about every 15 minutes. | Requests created in ElevateOS are sent to Yardi first. Requests created in Yardi appear in ElevateOS. Status changes and notes carry across. |
| Work order photos | ElevateOS to Yardi | With the request | Photos attached in ElevateOS are added to the Yardi service request. |
| Checklist answers | ElevateOS to Yardi | When a task is completed or updated | Answers are written to the Yardi resident or other-occupant custom fields you map. |
| Inspection PDFs | ElevateOS to Yardi | After a unit inspection is completed | Attaches the inspection PDF to the unit in Yardi. Turned on per building by ElevateOS. |
| Vehicles | Yardi to ElevateOS | Once a day | Adds resident vehicles to Valet. |
| Rent payments and charges | Both ways | Balance read when a resident opens Payments. Receipts posted after a payment settles. | Residents see open charges from Yardi and pay in the app. The payment is posted to Yardi as a receipt. Turned on per building. |
| Autopay | ElevateOS to Yardi | First days of the month | Charges enrolled residents and posts the receipt to Yardi. |
| Reversals and amenity charges | ElevateOS to Yardi | When they occur | Disputed or refunded payments are reversed in Yardi. Amenity reservation charges are added to the resident ledger when configured. |
| Resident deactivation | Yardi to ElevateOS | With each sync | Accounts of residents Yardi no longer returns are deactivated. They are not deleted. |
| Staff phase filters and announcement targeting | Uses Yardi property IDs | n/a | Staff can filter and target by phase when a building has more than one Yardi property. |

> **Good to know**
> 
> Yardi is the source of truth for resident details. Change names, emails, unit and status in Yardi. The next sync brings the change into ElevateOS.

 Requirements

> **Before you start**
> 
> Confirm with your Yardi representative that your Yardi contract includes the interfaces listed below. ElevateOS cannot see or confirm your Yardi licensing.

### On the Yardi side

- **An interface (vendor) user** in Voyager that ElevateOS will connect with. It must have access to every property you want to connect.
- **The Voyager web services URL** for your environment.
- **The Yardi server name** and **database name** for that environment.
- **Service Requests enabled** for each property that will use maintenance requests.
- **The Yardi property ID** of each building. For a group, the Yardi group ID.

#### Interfaces your Yardi account must have enabled

| Interface | Needed for | Required |
| --- | --- | --- |
| Resident data (Common Data) | Residents, units, leases, vehicles, checklist answers written to custom fields, inspection PDFs. | Yes |
| Service Requests | Work orders, categories, priorities, photos. | Yes, if you use maintenance requests |
| Resident transactions | Rent payments, autopay, reversals, amenity charges. | Only if you use in-app rent payments |

- For inspection PDFs, the attachment type **Inspection** must be configured for the interface in Voyager.
- If you want pet and vehicle information to sync, ask Yardi to allow the interface to read vehicle and pet data.
- Avoid the characters **\<** and **&** in the interface user's password. They can stop the connection from working.
- If your Yardi environment restricts incoming connections, contact your ElevateOS representative before setup.

### Resident data in Yardi

ElevateOS identifies each resident by email. These data rules decide whether a resident gets an account.

| Rule | Detail |
| --- | --- |
| Valid email | Residents without a valid email are skipped. Roommates need their own email to get their own account. |
| Valid name | Both first name and last name must be present. |
| One email, one profile | No other ElevateOS profile can use the same email. That includes outdated profiles of past residents and staff accounts. The same email in two buildings stays on the first building. |
| Current status with a move-in date | Active residents should have status Current and a move-in date, and no move-out date. |
| Applicants are not synced | Residents with status Applicant or Waitlist do not get accounts. |
| Phone numbers | A phone number from Yardi is only filled in when the ElevateOS profile has none. Existing numbers are never overwritten. |
| Consistent unit codes | Use one clean unit code per unit. Inspections are matched to Yardi units by this code. |

#### How Yardi statuses are treated

| Yardi status | In ElevateOS |
| --- | --- |
| Applicant, Waitlist | Not synced |
| Approved, Future, Future Lease, Applicant - Lease Signed, Former Applicant | Future |
| Current, Pending, Pending Transfer, Month to Month | Current |
| Notice, Notice to Vacate, Eviction, Evict, Under Eviction | On notice |
| Past, Former, Canceled, Cancelled | Past |
| Any other status text (for example Denied) | Not recognized, so the resident has no status in ElevateOS |

 Initial setup

Setup has three parts. Gather the Yardi details, create the connection in ElevateOS, then wait for the first sync and check the result.

> **Before you start**
> 
> Never send a password by email, ticket or chat message. Use the secure method your ElevateOS contact provides.

### Gather your Yardi information

| You need | Used for |
| --- | --- |
| Voyager web services URL | The **URL** field |
| Interface user name and password | The **Username** and **Password** fields |
| Yardi server name | The **Server Name** field |
| Yardi database name | The **Database** field |
| Property ID of each building | Choosing the **Property** |

### Create the connection

1. **Confirm the Yardi side is ready**  
   The interface user can see the property, and Service Requests is enabled for it.
2. **Open the building**  
   Go to **Dashboard** \> **Places**, then select the building from the list.
3. **Open the Integration tab**  
   Find the **Property Management System** section.
4. **Choose the integration type**  
   Set **Integration Type** to **Yardi**.
5. **Choose or add the management company**  
   If your Yardi connection already exists, pick it in **Property Management Company**. Otherwise click **Add New Property Management Company** and complete the form in the next step.
6. **Enter the company details**  
   All six fields are required. The **Add New Company** button stays unavailable until each one is filled in.
   
   | Field | What to enter |
   | --- | --- |
   | **Name (Internal)** | A name for your own reference. |
   | **Username** | The Voyager interface user. |
   | **Password** | The interface user's password. |
   | **Server Name** | Your Yardi server name. The form shows an example of the format. |
   | **Database** | Your Yardi database name. The form shows an example of the format. |
   | **URL** | Your Voyager web services URL. The form shows an example of the format. |
   
    On success you see *New Property Management Company was successfully added.* and the company is selected for you. Only one company record can exist per Voyager URL. If your URL is already listed, pick it from the dropdown instead.
7. **Pick the property**  
   Open **Property** and choose the building's Yardi property. The list shows properties for that company that are not yet linked to another building. If the list is empty, see [Troubleshooting](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#troubleshooting).
8. **Save**  
   Click **Save**. Then reload the page. The button should now read **Connected with Yardi**. The message *Changes saved successfully.* appears after you click Save, so use the reload to confirm the connection really saved.

> **Good to know**
> 
> - Once a building is connected, the type, company and property fields are locked. The only way to change them is **Disconnect**. Read [Changing your connection](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#changes) first.
> - ElevateOS does not test the credentials when you add a company. If the Property list does not load or stays empty, recheck the details with your Yardi administrator.
> - To connect a Yardi group of properties (a building with several phases), contact ElevateOS. A group cannot be set up from this screen.

### First sync

After you save, the building is included in the next scheduled sync (see [Sync schedule](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#sync)). Resident accounts are created at that sync and each new resident receives a welcome email. If you need the first sync sooner, ask ElevateOS Support. There is no sync button in the dashboard.

### Verify the setup

1. The building shows **Connected with Yardi** after a page reload.
2. After the next sync window, a resident you know is Current in Yardi appears in **Clients**, and their profile shows a **Yardi ID**.
3. Create a test maintenance request for a test unit. Check that it appears in Yardi, and that **Operations** \> **Maintenance** shows both an ElevateOS ID and a Yardi ID.
4. If the building has several phases, check that a phase dropdown appears when you create a request.
5. If rent payments are enabled, ask a test resident to open Payments and confirm the balance matches Yardi.

 Sync schedule

| What | When |
| --- | --- |
| Residents, units and leases | 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time |
| Work orders created or changed in Yardi | About every 15 minutes |
| Work orders created in ElevateOS | Sent to Yardi when the request is submitted |
| Vehicles | Once a day, early morning Central Time |
| Payment receipts | After the payment settles, with automatic retries if Yardi cannot accept it |
| Autopay | Days 1 to 5 of each month, morning Central Time |

> **Good to know**
> 
> - Resident sync is not real time. A move-in added in Yardi at 9:10 AM Central appears at the 12 PM sync.
> - If a sync fails for a building, the next scheduled run tries again.
> - The dashboard has no sync button, sync log or last-synced time. If you need a building synced sooner, or want to know how its last sync went, ask ElevateOS Support.

 Residents and accounts

### How residents get accounts

You do not enter residents in ElevateOS. At each sync, a resident who is valid in Yardi and has no ElevateOS account gets one. They receive a welcome email with a link to set their password.

Residents can also sign up in the app with your community code. Sign-up does not look the resident up in Yardi. For maintenance requests and payments to link to their Yardi record, the email they use must match the one in Yardi.

### What stays up to date

Name, unit, status, move-in and move-out dates, lease dates, unit type, pets and street are refreshed from Yardi at each sync. Phone number is filled in only when the ElevateOS profile has none. These fields appear read-only in the ElevateOS resident profile. Make changes in Yardi.

Roommates (other occupants) get their own accounts when they have their own email in Yardi. They share the household's **Yardi ID** and unit. Guarantors are not synced.

### Move-outs and deactivation

ElevateOS deactivates a resident when Yardi no longer returns them as a valid resident. It does not deactivate on a lease-end schedule. Deactivated accounts are not deleted. If the resident returns in Yardi, the next sync reactivates the account.

- Residents on notice stay active until Yardi stops returning them.
- Enter an actual move-out date in Yardi only when you mean it. A past move-out date or a Past status leads to deactivation.
- A deactivated resident who signs in sees: *User deactivated. Please contact your management team to activate your account.*
- A resident added by hand in ElevateOS to a Yardi-connected building is deactivated at the next sync if they are not in that Yardi property.

> **Good to know**
> 
> - Residents with a **Yardi ID** cannot delete their own account. They are asked to contact their administrator.
> - ElevateOS can turn off resident sync for a single building. Units and leases keep syncing. If residents stop updating for one building only, ask ElevateOS Support to check this setting.

 Maintenance and work orders

### Lifecycle

1. **A resident or staff member submits a request**  
   In the app or in the dashboard.
2. **ElevateOS sends it to Yardi first**  
   The request is confirmed in ElevateOS only if Yardi accepts it. If Yardi does not accept it, no request is created and the dashboard shows *Cannot create a Maintenance Request. Please try again.*
3. **Status and updates flow both ways**  
   Requests created in Yardi appear in ElevateOS in about 15 minutes. Status changes made in Yardi are picked up on the same cycle.

A request created in Yardi is matched to a resident by the requester's email within the building. If no resident matches, the request still appears, without a resident.

### Finding a request in Yardi

**Operations** \> **Maintenance** shows an ElevateOS ID and a Yardi work order ID for each request. In Yardi, search by the Yardi ID.

### Create form

Staff create requests from Maintenance in the dashboard. Residents use the request form in the app. A resident whose profile has a Yardi ID goes straight to the request form when opening the Maintenance tab.

| Field | Required | Notes |
| --- | --- | --- |
| **Select Request Type** | Staff, in the dashboard | **Unit** or **Common Area**. A unit request needs a resident or unit. |
| **Select Phase** | When the building has several phases | The Yardi property the request belongs to. |
| **Category** and **Subcategory** | No | Lists come from Yardi. |
| **Short Description** | Yes | 34 characters maximum. |
| **Request Description** | No | The dashboard allows up to 250 characters. |
| **Priority** | Yes | List comes from Yardi. |
| **Photos** | No | Up to 3 in the dashboard form. Sent to Yardi with the request. |
| **Permission to Enter** and **Pets** | No | Permission to Enter is on by default. |
| **Entry Note** | No | 244 characters maximum. Sent to Yardi as access notes. |

Categories and priorities come from your Yardi configuration and are refreshed periodically. A change in Yardi can take up to 12 hours to appear in ElevateOS.

> **Before you rely on priority**
> 
> The priority a resident selects may not carry through to Yardi as an emergency or urgent request. Confirm urgent requests by phone or through your emergency process. Do not rely on priority mapping.

### Status and changes

| Yardi status | Shown in ElevateOS as |
| --- | --- |
| Call, Assessment, Web, Awaiting Parts, Parts Pending, Pending Call Back, Pending Part Order, Request Reassignment, Vendor Scheduled, Waiting for Vendor, Warranty, Warranty Claim, Pending PTE, Vendor Needed, Need to Schedule Vendor | Pending |
| Work Order Follow Up | On Hold |
| Scheduled, Open | In Progress |
| Work Completed, Tech Completed, Completed and Closed | Finished |
| Any other status (for example Canceled) | Shown as it is in Yardi |

- **Finishing in ElevateOS** sets the Yardi request to Work Completed. A Job Summary is required and is sent to Yardi as technician notes. If the request is Finished in ElevateOS, ElevateOS keeps it Finished even if Yardi shows another status.
- **Cancelling in ElevateOS** asks you to **Select Cancellation Reason** from the reasons configured in Yardi. If Yardi has no cancel reasons, no reason is asked for. Confirm in Yardi that a cancelled request shows as cancelled there.
- **Photos** removed from a request in ElevateOS are removed from the Yardi request too.
- If Yardi rejects a change, ElevateOS shows an error and the change is not made.
- Staff can edit the short description, category and priority from the request details.

 Checklists, inspections and vehicles

### Writing checklist answers back to Yardi

In a custom checklist task, each question can be mapped to a Yardi custom field. When the resident completes or updates the task, the answer is written to that field on their Yardi record.

1. **Open the task**  
   Create or edit a custom task in Checklists.
2. **Choose Sync with Yardi field**  
   It appears on each question in a Yardi-connected building.
3. **Pick the field**  
   Use the **Residents** or **Other Occupants** tab. Search by field name, then click **Sync**.
4. **Save**  
   The question now shows *Syncing w/ Yardi* followed by the field name.

- Supported question types are short answer, long answer, file upload, single choice and multiple choice. Multiple-choice answers are sent as one value separated by semicolons.
- A question can map to one field per tab. A field already used by another question is unavailable.
- The Yardi field must accept the answer. If a Yardi field only accepts Cat or Dog, map it to a single-choice question with those two options.
- The resident is found in Yardi by email. If Yardi rejects a value, staff are not shown an error. Ask ElevateOS Support to check.
- The field list reflects the custom fields found on your Yardi residents at the last sync.

### Inspection templates

In Checklists settings, the inspections tab shows **Integrated with Yardi** for connected buildings. When you activate a template, ElevateOS asks you to match its unit types with your Yardi unit types.

### Inspection PDFs in Yardi

For buildings where ElevateOS has turned this on, the PDF of a completed unit inspection is attached to the unit in Yardi as an Inspection attachment. If the inspection needs review, the PDF is sent after the review.

- Only unit inspections are sent. Common-area inspections are not.
- Each inspection is sent once. Very large PDFs are skipped.
- The unit code in ElevateOS must match the unit code in Yardi.
- Failures are not shown in the dashboard. Ask ElevateOS Support if a PDF is missing.

### Vehicles

Once a day, vehicles with a license plate are imported from Yardi into Valet. The resident must have a phone number in ElevateOS. Plates marked NA or NONE and plates already in the building are skipped. Existing vehicles are not updated or removed by the import.

 Rent payments and charges

> **Before you start**
> 
> In-app rent payments are turned on per building by ElevateOS. They need the Resident transactions interface in Yardi and a payment account set up for the property. Ask your ElevateOS representative to review the settings with you: processing delay, autopay, charge selection, partial payment, prepaid charge code and amenity charges.

### What residents see in the app

1. **Payments**  
   Appears in the side menu when rent payments are available for the building. It shows **Your balance:**, the total of the open charges in Yardi.
2. **Pay now**  
   Residents can select charges if your property allows it, and edit the amount if your property allows partial payments.
3. **Review the fee**  
   A processing fee for card or bank (ACH) payment is added to the total and shown before the resident confirms.
4. **Confirm**  
   The app shows a success screen and asks the resident to allow up to 24 hours for the payment to show.

- **Pay now** is unavailable when the balance is zero, there are no open charges, or a payment is not allowed right now. In that case the app shows a message in red, for example *Your payment is currently being processed!*
- **Manage autopay** is available only when your property has autopay turned on. If autopay is already on, **Pay now** shows an information message instead.
- Autopay charges run in the first days of the month. Autopay is turned off automatically when a resident moves out or changes building.
- On the web, residents see **Pay Rent** in the Operations menu, with **Total Due** and **Pay Now**. Web payment is by card.

### Properties that use a Pay Rent link

If your property has a Pay Rent link set in Places, residents are sent to that external portal instead. Payments made there are outside ElevateOS and are not affected by changes to your Voyager connection.

### How payments reach Yardi

- When a payment settles, ElevateOS posts a receipt batch to Yardi, with one receipt for each charge code paid.
- If Yardi cannot accept the receipt, ElevateOS retries automatically, up to 7 attempts over about 3.5 hours. If every attempt fails, the building's managers are emailed.
- Disputed or refunded payments are reversed in Yardi the same way. Managers are emailed if a reversal fails.
- If a failure email says a batch may already be posted, check it in Voyager before entering anything again.
- **Amenity charges** are added to the resident ledger only when a charge code is configured and that code exists in Yardi. If the code is not found, the charge is skipped without a message. Ask ElevateOS to confirm the code.

 Phases and targeting

When a building's connection includes more than one Yardi property, phase options appear in these places. A building with a single property does not show them.

| Where | What the phase does |
| --- | --- |
| Dashboard: create maintenance request | **Select Phase** is required. The resident and unit search narrows to that phase. |
| Dashboard: maintenance list | **Phase** filter and a Priority filter. The address column shows the phase in brackets. The CSV export respects the filters. |
| Dashboard: internal inspections | **Select phase** narrows the units you can pick. |
| Dashboard: communications | **Select Phase** narrows recipients when one building is selected. |
| Dashboard: surveys | **Select Phase** narrows who receives the survey. |
| Mobile app, staff | Phase picker when creating a request or scheduling an inspection, a phase filter in the maintenance list, and a Yardi property filter for announcements. |

Staff can also use Yardi priorities for on-call escalation in the on-call schedule.

Extra phases cannot be added by customers. Contact ElevateOS.

 Changing your connection

> **Before you change anything**
> 
> Tell ElevateOS before any change in Yardi that affects the connection: a new URL, new credentials, a new database or a new property group. Do not wait until after cutover.

### Disconnecting a building

1. Go to **Dashboard** \> **Places**, select the building and open the **Integration** tab.
2. Click **Disconnect** and confirm in **Disconnect from PMS**.

Disconnecting removes the Yardi link from the building's residents and clears its units in ElevateOS. Resident accounts are not deleted. The building no longer sends requests to Yardi. Contact ElevateOS before disconnecting a building that is in use.

### New URL, new password or a new Yardi environment

- The company details cannot be edited after they are saved. Send the new details to your ElevateOS contact through the secure method they provide, and ElevateOS updates the connection.
- A building stays connected to the old Yardi environment until ElevateOS repoints it. Until then, new Yardi residents do not appear. Residents added by hand can be deactivated at the next sync because they are not in the connected Yardi. Work orders do not reach the new Yardi.
- Plan the cutover with ElevateOS. If requests cannot reach Yardi during the change, consider pausing maintenance requests for that period.
- If your Yardi property code changes, tell ElevateOS so the building can be updated.

### Adding properties to a group

When a building is connected to a Yardi group, every property in that group is part of the building. Adding a property to the group in Voyager can bring that property's residents into the building at the next sync. Talk to ElevateOS before you change group membership. Voyager changes must be made by someone with Voyager administrator access.

 Troubleshooting

> **What the dashboard does not show**
> 
> The ElevateOS dashboard does not currently show a sync log, a last-synced time, or the reason a particular resident or work order was skipped. It also has no sync button and no connection test. ElevateOS Support can check sync status for a building. See [what to send](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#support-checklist).

### A resident does not appear in ElevateOS

- Wait for the next sync window.
- In Yardi, check the resident has a valid email, a first and last name, and a status that is not Applicant or Waitlist.
- Check that no other ElevateOS profile uses the same email, including an older profile for a past resident or a staff account. Clear the email on the outdated profile.
- Check the email is not already used for the same resident in another building.
- Check the building shows **Connected with Yardi**.

### A resident was created, then deactivated

- Yardi no longer returned them as a valid resident. Check their status and whether a move-out date is set.
- If they were added by hand in ElevateOS, they are deactivated because they are not in the connected Yardi property.
- If your Yardi environment recently changed, the building may still point at the old one. Contact ElevateOS.

### A resident is Current in Yardi but not active in ElevateOS

- Check for a move-out date, a missing move-in date, or a duplicate email on another profile or building.
- Check the status text is one ElevateOS recognizes (see the status table under [Requirements](https://help.elevateos.com/how-does-the-elevated-living-yardi-integration-work#requirements)).
- Send ElevateOS Support the resident email and unit.

### A phone number is not updating

ElevateOS only fills in a phone number when the profile has none. It never overwrites a number the resident has. Residents can update their number in the app.

### A unit is not showing

- Units come from Yardi at each sync. A unit Yardi no longer returns is made inactive.
- Check the unit code is clean and consistent in Yardi.
- If the unit is in a phase, check the building's connection includes that phase.

### Residents landed in the wrong building after a group change

A property added to a connected Yardi group syncs its residents into the building. Contact ElevateOS right away. Voyager changes must be made by someone with Voyager administrator access.

### A work order is missing in Yardi

- A request is only confirmed in ElevateOS if Yardi accepted it. If you saw an error when creating it, it was not created.
- In **Operations** \> **Maintenance**, copy the Yardi ID and search for it in Yardi. It may already exist under that ID.
- Check Service Requests is enabled for the property in Yardi and that the interface user still has access.
- If the Yardi environment recently changed, requests may be going to the old one. Contact ElevateOS.

### A work order is missing in ElevateOS

- Requests created in Yardi arrive in about 15 minutes.
- Check the request is for the connected property or phase.
- Send ElevateOS Support the Yardi work order ID and the time it was created.

### Updates are slow

Residents, units and leases sync five times a day. Work orders from Yardi arrive about every 15 minutes. Yardi category and priority changes can take up to 12 hours to appear.

### Priority or emergency did not carry through to Yardi

Priority mapping may not carry an emergency into Yardi. Confirm urgent requests by phone or through your emergency process. Do not rely on priority mapping.

### A payment did not post in Yardi

- Posting is retried automatically for about 3.5 hours.
- If every attempt fails, the building's managers are emailed. Check Voyager before re-entering the payment, since a batch may already be posted.
- Send ElevateOS Support the resident, unit, amount and time.

### Credentials or the URL changed in Yardi

The connection stops working until ElevateOS updates it. Send the new details through the secure method your ElevateOS contact provides. Never put a password in an email, ticket or chat.

### The property is not in the Property list

- The Yardi interface user probably does not have access to that property. Your IT or Yardi administrator needs to add it in Yardi.
- The list also leaves out properties already linked to another building.

### A checklist answer did not reach Yardi

- Check the Yardi field accepts the value the resident entered.
- Check the resident's email in Yardi matches the one in ElevateOS.
- Staff are not shown an error for this. Ask ElevateOS Support to check.

### The dashboard says "saved" but the building is not connected

Reload the page. If the button does not read **Connected with Yardi**, the save did not go through. Try again, or contact ElevateOS.

### What to send ElevateOS Support

- Building name
- Resident email and unit (for resident issues)
- Yardi property ID
- Work order ID, from ElevateOS and from Yardi (for maintenance issues)
- The date and time it happened, with time zone
- A screenshot of what you see

*Do not include passwords.*

 FAQ

### How often does ElevateOS sync with Yardi?

Residents, units and leases sync at 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time. Work orders from Yardi come in about every 15 minutes.

### Do I need to create residents in ElevateOS?

No. Add them in Yardi with a valid email. Accounts are created at the next sync.

### Can I edit a resident's name or email in ElevateOS?

Those fields are read-only for Yardi-connected buildings. Change them in Yardi.

### When does a resident lose access at move-out?

When Yardi no longer returns them as a valid resident, not on a set lease-end time. Enter move-out dates in Yardi only for actual move-outs.

### Can one ElevateOS building cover several Yardi properties?

Yes, through a Yardi group. ElevateOS sets this up. Contact your representative.

### Does ElevateOS provide Yardi technical support?

No. ElevateOS supports the ElevateOS side of the connection. Questions about Voyager settings, users and licensing go to Yardi or your Yardi administrator.

 What is not covered

- Lease documents and notices are not shown in the app. The app also does not show lease terms or rent amounts beyond the list of charges.
- Signing up in the app uses a community code. There is no Yardi lookup at sign-up.
- Existing phone numbers are not overwritten from Yardi.
- Applicants are not synced.
- Birth date, gender and profile photo are not synced from Yardi.
- Customers cannot add extra phases. ElevateOS sets up groups.
- Late fees are not handled as a separate item in payments.
- The dashboard has no sync log, no sync button and no connection test.
- Web payment is by card only. The mobile app is the primary resident experience, and the web experience for residents is more limited.
- ElevateOS does not provide technical support for Yardi.

 Quick reference

### Glossary

| Term | Meaning |
| --- | --- |
| **Property ID** | The code Yardi uses for a property. You choose it when you connect a building. |
| **Group** | A Yardi group of properties that connects to a single ElevateOS building. ElevateOS sets this up. |
| **Phase** | One Yardi property within a building that has several. Shown as a dropdown or filter in ElevateOS. |
| **Yardi ID** | Shown on a resident profile. It identifies the household's record in Yardi. Roommates share it. |
| **Management company record** | The saved Yardi connection details in ElevateOS: name, username, password, server name, database and URL. |
| **Interface user** | The Voyager user ElevateOS connects with. |
| **Yardi work order ID** | The request number in Yardi. Search for it in Voyager. ElevateOS keeps its own ID for the same request. |
| **Sync with Yardi field** | The checklist option that maps a question to a Yardi custom field. |

### Setup checklist

#### In Yardi

- Confirmed licensing for the needed interfaces with your Yardi representative
- Interface user created, with access to each property
- Service Requests enabled for each property
- Voyager URL, server name, database name and property ID collected
- Resident emails, names, statuses, move-in and move-out dates checked

#### In ElevateOS

- Credentials shared by the secure method, or entered in Places
- Integration Type set to Yardi, company and property chosen, Save clicked
- Page reloaded and button reads Connected with Yardi
- Groups, phases, payments and inspection PDFs discussed with ElevateOS if needed

#### After the first sync

- A known Current resident appears with a Yardi ID
- A test work order reaches Yardi and shows both IDs in Operations › Maintenance
- Balance in the app matches Yardi (if payments are on)

*For questions about your setup, contact your ElevateOS representative or ElevateOS Support.*

- [Getting started](https://help.elevateos.com/getting-started?hsLang=en)
- [Integrations](https://help.elevateos.com/integrations?hsLang=en#main-content)

    - [Access Control - 2N](https://help.elevateos.com/integrations?hsLang=en#access-control-2n)
    - [Access Control - Brivo](https://help.elevateos.com/integrations?hsLang=en#access-control-brivo)
    - [Access Control - ButterflyMX](https://help.elevateos.com/integrations?hsLang=en#access-control-butterflymx)
    - [Access Control - iGloo](https://help.elevateos.com/integrations?hsLang=en#access-control-igloo)
    - [Access Control - Latch](https://help.elevateos.com/integrations?hsLang=en#access-control-latch)
    - [Access Control - OpenPath](https://help.elevateos.com/integrations?hsLang=en#access-control-openpath)
    - [Access Control - PointCentral](https://help.elevateos.com/integrations?hsLang=en#access-control-pointcentral)
    - [Access Control - Rently](https://help.elevateos.com/integrations?hsLang=en#access-control-rently)
    - [Access Control - Salto KS](https://help.elevateos.com/integrations?hsLang=en#access-control-salto-ks)
    - [Access Control - SALTO Space](https://help.elevateos.com/integrations?hsLang=en#access-control-salto-space)
    - [Access Control - Schlage](https://help.elevateos.com/integrations?hsLang=en#access-control-schlage)
    - [Access Control - Swiftlane](https://help.elevateos.com/integrations?hsLang=en#access-control-swiftlane)
    - [Package Lockers - Luxer One](https://help.elevateos.com/integrations?hsLang=en#package-lockers-luxer-one)
    - [Package Lockers - Parcel Pending](https://help.elevateos.com/integrations?hsLang=en#package-lockers-parcel-pending)
    - [PMS - Entrata](https://help.elevateos.com/integrations?hsLang=en#pms-entrata)
    - [PMS - Onesite / Realpage](https://help.elevateos.com/integrations?hsLang=en#pms-onesite-realpage)
    - [PMS - Resman](https://help.elevateos.com/integrations?hsLang=en#pms-resman)
    - [PMS - Yardi](https://help.elevateos.com/integrations?hsLang=en#pms-yardi)
- [Management Portal](https://help.elevateos.com/management-portal?hsLang=en#main-content)

    - [Dashboard](https://help.elevateos.com/management-portal?hsLang=en#dashboard)
    - [Calendar](https://help.elevateos.com/management-portal?hsLang=en#calendar)
    - [Contacts](https://help.elevateos.com/management-portal?hsLang=en#contacts)
    - [Marketing - Announcements & Surveys](https://help.elevateos.com/management-portal?hsLang=en#marketing-announcements-surveys)
    - [Marketing - Community Feed & Interest Groups](https://help.elevateos.com/management-portal?hsLang=en#marketing-community-feed-interest-groups)
    - [Marketing - Gift Cards](https://help.elevateos.com/management-portal?hsLang=en#marketing-gift-cards)
    - [Marketing - Rewards](https://help.elevateos.com/management-portal?hsLang=en#marketing-rewards)
    - [Marketing - Digital Signage](https://help.elevateos.com/management-portal?hsLang=en#marketing-digital-signage)
    - [Marketing - Reputation Management](https://help.elevateos.com/management-portal?hsLang=en#marketing-reputation-management)
    - [Marketing - Digital Displays](https://help.elevateos.com/management-portal?hsLang=en#marketing-digital-displays)
    - [Operations - Checklists](https://help.elevateos.com/management-portal?hsLang=en#operations-checklists)
    - [Operations - User Management](https://help.elevateos.com/management-portal?hsLang=en#operations-user-management)
    - [Operations - Amenities & Reservations](https://help.elevateos.com/management-portal?hsLang=en#operations-amenities-reservations)
    - [Operations - Maintenance](https://help.elevateos.com/management-portal?hsLang=en#operations-maintenance)
    - [Operations - Visitors](https://help.elevateos.com/management-portal?hsLang=en#operations-visitors)
    - [Operations - Packages](https://help.elevateos.com/management-portal?hsLang=en#operations-packages)
    - [Operations - Package Room](https://help.elevateos.com/management-portal?hsLang=en#operations-package-room)
    - [Operations - Shift & Action Log](https://help.elevateos.com/management-portal?hsLang=en#operations-shift-action-log)
    - [Operations - Community Essentials](https://help.elevateos.com/management-portal?hsLang=en#operations-community-essentials)
    - [Operations - Parking Management](https://help.elevateos.com/management-portal?hsLang=en#operations-parking-management)
    - [Operations - Valet CRM](https://help.elevateos.com/management-portal?hsLang=en#operations-valet-crm)
    - [Unified Inbox](https://help.elevateos.com/management-portal?hsLang=en#unified-inbox)
    - [Operations - Internal Inspections](https://help.elevateos.com/management-portal?hsLang=en#operations-internal-inspections)
    - [Operations - Escalations](https://help.elevateos.com/management-portal?hsLang=en#operations-escalations)
- [Front Desk & Concierge](https://help.elevateos.com/front-desk-concierge?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/front-desk-concierge?hsLang=en#getting-started)
    - [Packages](https://help.elevateos.com/front-desk-concierge?hsLang=en#packages)
    - [Shift & Action Log](https://help.elevateos.com/front-desk-concierge?hsLang=en#shift-action-log)
    - [Market Shop](https://help.elevateos.com/front-desk-concierge?hsLang=en#market-shop)
- [Resident App](https://help.elevateos.com/resident-app?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/resident-app?hsLang=en#getting-started)
    - [Engage - Neighborhood Perks](https://help.elevateos.com/resident-app?hsLang=en#engage-neighborhood-perks)
    - [Operate - Reservable Amenities](https://help.elevateos.com/resident-app?hsLang=en#operate-reservable-amenities)
    - [Operate - Maintenance](https://help.elevateos.com/resident-app?hsLang=en#operate-maintenance)
- [Portfolio Management](https://help.elevateos.com/portfolio-management?hsLang=en#main-content)

    - [Getting Started](https://help.elevateos.com/portfolio-management?hsLang=en#getting-started)

- [Default HubSpot Blog](http://blog.elevatedliving.com/blog)

[![Elevate OS Logo (2)](https://help.elevateos.com/hs-fs/hubfs/REBRAND/Elevate%20OS%20Logo%20(2).png?width=200&height=133&name=Elevate%20OS%20Logo%20(2).png "Elevate OS Logo (2)")](http://elevatedliving.com)

Help Center

Copyright © 2026, ElevateOS