OwnerRez Integration

RentReel is bookkeeping and tax-reporting software for short-term rental operators: Schedule E automation, REPS/§469 material-participation tracking, and CPA-ready exports. The OwnerRez integration lets operators pull their properties and bookings directly from OwnerRez into their RentReel books, so gross rents land on Schedule E Line 3 without CSV exports or manual entry.

The integration is read-only: RentReel reads from OwnerRez and never writes anything back.

• Steps for integration
• What you see once connected
• Sync mechanics
• What Data is Transmitted
• Webhooks
• Disconnecting
• Support

Steps for integration

1. Sign in to RentReel at app.rentreel.co (or create an account).
2. Open the Upload page from the sidebar.
3. Under 🔗 Direct PMS Connections, click Connect OwnerRez.
4. A popup opens on OwnerRez's authorization page. The requested access is read-only (GET requests only). Click Authorize.
5. The popup confirms the connection and closes itself. The card on the Data & Connections page flips to OwnerRez · connected, and the first sync starts automatically.
6. Click ↻ Refresh now on the card any time to pull the latest bookings. Re-syncing never creates duplicates. Each OwnerRez booking is imported at most once, keyed by its booking ID.

What you see once connected

• Each OwnerRez booking is imported as a Revenue transaction dated by check-in, labeled OwnerRez <booking id> · <listing name>.
• Bookings are matched to RentReel properties by listing name. If a listing doesn't match a configured property, the transaction imports unassigned and can be attributed to a property in one click (RentReel's property-learning then remembers the mapping).
• Cancelled bookings and owner blocks are skipped. They aren't revenue.
• Imported bookings flow through the rest of RentReel like any other revenue: P&L, per-property reports, Schedule E export, and average-stay / §469 eligibility badges.

Sync mechanics

• Sync window: each refresh pulls bookings for the current tax year (January 1 to December 31), in pages of 100, up to 2,000 bookings per refresh, which comfortably covers even large portfolios.
• Property matching: case-insensitive name matching in both directions (an OwnerRez listing called "Lakeview Lodge, Unit B" matches a RentReel property named "Lakeview Lodge"), checked against both the property's full name and its short name.
• What each transaction carries: the booking's total amount as revenue, night count derived from arrival → departure, and the aggregate guest count (adults + children). Nights feed the average-stay calculation behind the §469 STR/MTR/LTR badges.
• The expense side stays yours: this feed imports booking revenue. Channel fees, cleaning costs, and other expense detail enter RentReel from your bank/card imports or an OwnerRez CSV export, on their own Schedule E lines. Nothing is silently netted.
• Expired sessions fail loudly: if the OwnerRez authorization lapses, the sync stops with a clear "click Connect to re-link" prompt. Nothing is retried silently and no stale data is written.

What Data is Transmitted

All data flows one direction: OwnerRez → RentReel, over read-only GET requests, only when the operator connects or clicks refresh. RentReel makes no writes, updates, or deletes to any OwnerRez account.

• Guest personal information (names, emails, phone numbers) is not stored in RentReel's books: only aggregate guest counts per booking.
• Access uses OAuth 2.0 (authorization-code flow). The operator's access token is stored in their own RentReel workspace (protected by row-level security, readable only by that signed-in operator) and is presented per-request. Revoking access in OwnerRez or clicking Disconnect in RentReel ends all data flow immediately.
• RentReel's proxy layer forwards each operator's own token to the OwnerRez API and holds no shared credentials for operator accounts.

Webhooks

Yes. RentReel registers a webhook receiver for OwnerRez booking, property, and message event notifications. The receiver is HTTPS with HTTP Basic authentication, and events are used as change signals only: actual data always enters RentReel through the read-only API pulls described above, never from webhook payloads.

Disconnecting

1. On the Data & Connections page, click Disconnect on the OwnerRez card.
2. The stored access token is deleted and future syncs stop immediately.
3. Bookings already imported remain in the operator's books (that's their financial record) and can be deleted like any other transactions.

Support

Questions about the integration: [email protected] · General support: [email protected]

RentReel is built and operated by RentReel LLC (Wyoming), founded by a 5-property short-term-rental operator.