Property Management & Accounting integration
Yardi Voyager COI compliance integration
Keep vendor insurance in Yardi Voyager current without retyping a single expiration date. Pikorua Security verifies each vendor's certificate and endorsements against your property-level requirements, then writes the Vendor Insurance records and compliance flag back to Voyager on a schedule, so expired or deficient vendors stop at the check run.
Yardi Voyager, Lakeview Commons (lakev)
Vendor cascland
Check run hold: insurance not compliant
GL 6612-0457-19 expired 10/15/2026. Written in the 2:00 AM ETL import.
- Vendor name
- Cascade Landscape Services LLC
- Insurance type
- General Liability
- Expiration date
- 10/15/2026
- Compliant
- No
- Unpaid payables
- 2, $12,480.00
Written by Pikorua Security Oct 16, 2026, 02:00 AM ET
- Setup time
- 3 to 4 hours
- Connection
- SFTP + Voyager ETL import files
- Fields synced
- 7 fields, 5 trigger events
- Included on
- Professional and Enterprise
Sync fields
What Pikorua Security reads from and writes to Yardi Voyager.
| Field | Direction | What happens |
|---|---|---|
| Vendor code and name | Yardi Voyager to Pikorua Security | Voyager vendor codes become the match key, so a vendor renamed in Pikorua Security never splits from its payables. |
| Properties and vendor assignments | Yardi Voyager to Pikorua Security | Lets Pikorua Security apply each property's requirements; a Class A office tower and a garden-style community rarely share limits. |
| Vendor Insurance: type and expiration date | Pikorua Security to Yardi Voyager | Written per coverage line (general liability, workers compensation, auto, umbrella) from the verified certificate and policy pages. |
| Vendor Insurance: Compliant | Pikorua Security to Yardi Voyager | Set to No when any rule fails and Yes when every rule passes. The reason lives in Pikorua Security and in the user-defined field below. |
| Liability and workers' comp expiration on the vendor | Pikorua Security to Yardi Voyager | Kept in step with the Vendor Insurance rows, for reports that read the vendor header. |
| Unpaid payables | Yardi Voyager to Pikorua Security | Read before each check run so AP sees how many dollars each deficiency is holding. |
| User-defined field: Pikorua Security status | Pikorua Security to Yardi Voyager | A short reason and a link to the vendor's Pikorua Security record, so AP can open the deficiency list from Voyager. |
Trigger events
When the certificate changes, Yardi Voyager changes with it.
- Hold
General liability or workers compensation expires
Then: The expiration is written to Vendor Insurance with Compliant set to No in the next import, and the vendor drops out of the check run wherever your Voyager AP setup enforces vendor insurance.
- Hold
Owner entity not named as additional insured
Then: Vendor marked not compliant for that coverage line with the missing entity named in the user-defined field; the property manager is notified.
- Warn
Policy expiring in 30 days
Then: Expiration refreshed and the vendor's broker receives the day-30 request. Voyager's compliant flag is unchanged, so AP is not blocked early.
- Release
Renewal verified
Then: New expiration dates and Compliant set to Yes in the next import; held payables are eligible for the following check run.
- Hold
New vendor created in Voyager
Then: Pikorua Security sends a compliance request to the vendor and its broker the next morning, using the property's requirement template.
Setup
Live in 3 to 4 hours.
5 steps, done by your Yardi Voyager administrator and a Pikorua Security Admin together. Nothing to install on your servers beyond the file drop you already control.
SFTP + Voyager ETL import files- 1
Set up the ETL exchange
Your Yardi administrator creates the vendor and vendor insurance ETL imports Pikorua Security will supply and schedules the vendor, property and payables exports to a Pikorua Security SFTP folder.
- 2
Match vendors
Pikorua Security matches Voyager vendors to certificates by tax ID and legal name and flags duplicates for review.
- 3
Map requirements to properties
Assign each property or property group a requirement template, such as office tower, retail center or multifamily, with its limits, endorsements and named insureds.
- 4
Approve a test import
Pikorua Security produces the first Vendor Insurance file in the column layout your administrator approves. Load it to a test database first if you have one.
- 5
Schedule the cycle
Most portfolios import nightly at 2:00 AM local time, plus an extra run before each check run. Choose who receives the exception report.
Voyager's own insurance fields carry the verdict
Yardi Voyager already has a place for vendor insurance: Vendor Insurance rows with a type, an expiration date and a compliant flag, plus liability and workers' comp expiration dates on the vendor itself. Depending on how your AP is configured, Voyager can keep checks from processing for a vendor whose insurance is expired. The control exists. The data feeding it is typed by hand from the front page of an ACORD 25.
Pikorua Security fills those fields from verified coverage. A certificate that says "additional insured: Y" is not proof; the endorsement on the policy is. Pikorua Security checks that the owner entity and your management company are named, that the form is CG 20 10 or CG 20 26 at an acceptable edition, and that primary and non-contributory and waiver of subrogation wording is attached, before Voyager ever sees Compliant = Yes.
No interface license required
The connector runs on Voyager's ETL imports and scheduled exports, which your own Yardi administrator controls. Nothing is installed in your Voyager database and no separate Yardi interface is needed. The tradeoff is timing: verdicts reach Voyager on the import schedule rather than within seconds. Most operators run nightly plus an on-demand import before each check run, and Pikorua Security's hold report covers the hours in between.
Multi-entity portfolios
Third-party managers and REITs often manage one vendor across dozens of properties with different owners, joint venture partners and lenders, each of whom must be named as an additional insured. Pikorua Security checks the endorsement for every required entity by name, so a landscaper who names the management company but not "Lakeview Commons Owner LLC" is flagged for that property only.
More property management & accounting connectors
Teams that connect this usually connect these too.
FAQ
Yardi Voyager connector questions.
Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.
Do we need a Yardi interface license?
Does this replace VENDORCafé or VendorShield?
How fast does a verdict reach Voyager?
Which coverage types does it write?
14-day free production trial
Connect Yardi Voyager during your 14-day trial.
Upload your current certificates, authorize Yardi Voyager, and see which vendors would be on hold today before you switch a single rule on.