Overview
When you approve an application in RentEngine, applicant data and documents are automatically pushed into Rentvine, so your team does not have to re-enter anything.
When it runs
The writeback fires automatically the moment an application group is marked Approved — no manual step needed. You can also re-run it on demand using Force push to PMS in the application's actions menu, useful if you fixed something and want to re-sync.
For each approved group, RentEngine:
Creates each applicant as an individual application in Rentvine
Merges co-applicants into a single application group (the primary applicant is the destination)
Sets the Rentvine application status to Approved — no applicant emails are sent from Rentvine
Uploads the supporting documents to the Rentvine application
If Rentvine rejects a field (for example, a required dropdown value), RentEngine automatically retries once with a safe default, so a single bad field does not block the whole sync.
What applicant data is synced
For every applicant on the approved group:
Personal info: first name, middle name, last name, email, cell phone, date of birth, SSN
Applying for (the unit): unit street address, unit number, city, state, postal code, country, and monthly rent (the unit's target rental rate)
Lease info: desired move-in date
Current address: street, city, state, postal code, country (from the applicant's address history)
Employment or income: employer name, supervisor phone, position or title, monthly salary, and start date — one entry per income source
Occupants: name and date of birth of each additional occupant
Pets: name, type or breed, weight, and whether it is an assistance animal or ESA
Vehicles: make, model, year, and color
Note: Fields left blank by the applicant are sent empty or with a safe placeholder. Rent only defaults to a placeholder if the unit has no target rental rate on file.
What documents are synced
All four categories are included by default:
Rental application PDF — the full application report
ID verification documents — each applicant's ID front, ID back, and selfie
Applicant-uploaded documents — anything the applicant attached (pay stubs, bank statements, offer letters, etc.)
Screening reports — SingleKey and TransUnion credit, criminal, and eviction reports, when available
If a document does not exist for an applicant, it is skipped — it will not fail the rest of the sync.
Recommended: use Rentvine's default application template
Applicant data is matched to Rentvine by field name. To make sure every field lands correctly, we strongly recommend keeping your Rentvine application template on the default. If you customize it (renaming fields, or changing or removing built-in dropdown options), some data may not map cleanly and could land in the wrong field, be dropped, or fall back to a default value.
What happens if something fails
The writeback is best-effort and resilient:
If one applicant, field, or document cannot be synced, it is logged and the rest of the sync continues.
A required-field rejection triggers one automatic retry with a safe default.
If an approved application does not appear in Rentvine as expected, reach out to RentEngine support and we can review the sync logs for that application.
Force push notes
Force push is a one-time action, not a continuous or ongoing sync. If you force push a pending application and then make changes or add documents afterward, those updates will not sync automatically. You will need to trigger Force push again to send the updated version over.
Approving an application later re-runs the same underlying writeback rather than creating a duplicate. It updates or re-syncs the existing Rentvine application.
Force push works on applications in any status. A rejected application can be pushed manually if you want a record of it in Rentvine.
When you trigger Force push, allow up to 60 seconds to compile all the documents.