Integration overview
Summit Sherpa (tenant/renters insurance compliance tool) connects compliance workflows to your property management system so resident rosters stay current and verification results can be operationalized. Compliance tracking is Canada-wide.
Quebec note: Summit doesn’t place tenant insurance in Quebec. If you have Quebec properties, we can coordinate placement through partner brokers/carriers while still supporting compliance tracking.
Direct PMS integrations supported today: Yardi and Entrata. For other systems, connectivity is typically handled via exports/webhooks where supported (see existing technical references below).
Who this is for
-
IT and property-ops teams implementing tenant insurance compliance at scale
-
Data owners responsible for PMS exports, SFTP, and webhook endpoints
-
Operations leaders who need clear “what data moves where” documentation
What you can do
-
Bring resident/unit/lease rosters into Sherpa for compliance tracking
-
Keep move-ins/move-outs aligned so verification status reflects occupancy
-
Push/share compliance outcomes for operational follow-up and reporting
-
Use exports and event notifications to integrate with downstream tools
Data flows (high level)
Inbound to Sherpa (from Yardi / Entrata)
Common inbound objects:
-
Properties/buildings (IDs, names, addresses)
-
Units (unit codes, occupancy status)
-
Leases (start/end dates, status)
-
Residents (name, contact information, lease linkage)
Outbound from Sherpa (to your ecosystem)
Common outbound artifacts:
-
Compliance status by unit/lease/resident (verified / in review / rejected / lapsed)
-
Exception reasons and timestamps
-
Audit trail exports for internal controls
For webhook and CSV formats, use the detailed references:
Verification and status lifecycle (operational)
A typical lifecycle looks like:
-
Roster sync brings in a resident/lease record
-
Proof is collected and reviewed against your standards
-
Status changes are recorded (e.g., submitted → verified, or submitted → rejected)
-
Ongoing monitoring flags lapses/expiries
-
Exports/webhooks share changes with downstream systems when configured
For enforcement model context, see Turnkey enforcement.
Exports: when they’re useful
Exports are often used for:
-
Nightly reconciliation to keep compliance status aligned with occupancy
-
Owner/lender reporting packages
-
Exception aging reviews and monthly governance
Implementation notes (what to confirm early)
-
Your “source of truth” fields for unit and lease identifiers
-
Refresh frequency (daily/weekly) and how to handle mid-day move-ins
-
How you want to represent co-tenants (one record per lease vs. per resident)
-
Which roles can configure integrations vs. only view/export data
FAQ
Do you integrate directly with systems other than Yardi and Entrata? Direct integrations supported today are Yardi and Entrata. Other systems are typically supported via exports/webhooks where available (see Tenant insurance webhooks & CSV).
Can we start with exports and add deeper integration later? Yes—many teams start with roster exports to launch a pilot, then add event-driven updates and automation.
Is Quebec supported? Yes—compliance tracking is supported. (See the Quebec note above.)
Book a demo
Review your data flow with a Sherpa walkthrough.