RealPage Connector (Roadmap — Not Built)
Design intent for property-management ingestion: leases, ledger, maintenance, and unit data governed with source authority and lineage across the portfolio. This connector is ROADMAP — not built, and no third-party integration is live in operator production today.
Capabilities
- Lease and resident agreement records
- General ledger and AR / AP signals
- Unit bed board and occupancy
- Maintenance work order tracking
- Vendor and procurement records
- Multi-property rollups
- Resident statement reconciliation
- Portfolio-level reporting
How it works
- RealPage API + credentials — Design intent: confirm API entitlement with the vendor and obtain credentials. This step is ROADMAP — not built.
- Property + unit hierarchy mapping — Map RealPage properties and units into the canonical Entity and Property hierarchy.
- Ledger + maintenance bridge — Wire ledger and work-order events into the canonical Ledger and Property records.
- Portfolio dashboard activation — Roadmap design intent: expand only after operator-approved source, reconciliation, security, and acceptance gates are met.
Integration facts
- Interface basis — Vendor-documented design
- Current connection — Roadmap · not operator production
- Timing — Determined after validation scope
- Records surfaced — Lease · Ledger · Unit · WO
Frequently asked questions
- Does SeniorCRE replace RealPage?
- Not by default. The operator may keep RealPage authoritative for property records; the SeniorCRE interface is roadmap design intent and not live in operator production.
- Is multi-community supported?
- Yes. Multi-property rollups operate over the canonical Entity hierarchy.
- How is unit / bed reconciliation handled?
- Roadmap design intent: map property state to governed entities while preserving alternate valid values; no production sync or elimination claim is made.
https://seniorcre.com/integrations/realpage