The customer would authorise the connection
The customer would connect their account through an approved authorisation process.
Operent would receive only the access and data permitted for that customer and integration.
TECHNOLOGY PARTNERSHIPS
Connect reservation data to the financial work around it.
Operent handles the financial side of short-term rentals: each property's result, the owner payout and the month-end close. With the customer's permission, we want to receive the properties and bookings already in your platform, so nobody types them twice.
No partner integration is live yet. We're choosing the first ones.
Production platform · Controlled pre-launch · Real users
- Booking platforms
- PMS
- Channel managers
- Financial platforms
Operent Financial operations
WHAT WE PROPOSE
A read-only pilot.
Start small, with low risk on both sides.
- What Operent would read
- Properties and reservations.
- Whose data
- Only shared customers who authorise the connection.
- What we don't do
- No writes to your system. No pricing, calendar, guest messaging or payments.
- On your side
- Read access through an API or export, for those customers.
- What you get
- Shared customers with their month-end close handled, without you building that financial layer.
- Size and duration
- A few shared customers over a short period, agreed with you before we start.
- How we measure it
- Reservations arriving with no manual entry and no duplicates, and those customers closing their month in Operent.
Other paths, if they fit you better: a booking platform connection, a channel manager connection, financial interoperability, or starting with a technical conversation.
A NARROW, PRACTICAL CONNECTION
How a connection would work, in four steps.
It works with a booking platform, a PMS, a channel manager or a mix, each connected on its own.
Properties would be matched or initialised
The customer would select which properties should be connected.
Where the partner allows it, the property's basic data (listed in the table below) is used to identify, match or create the matching property in Operent.
Reservations would stay synchronised
When supported by an approved integration, a new source reservation would create the corresponding reservation in Operent:
- a new reservation would create a linked record
- a reservation change would update the linked record
- a cancellation would update the reservation status
- repeated synchronisation would not create duplicate reservations
Operent handles its financial domain
Once the reservation exists in Operent, it can support the customer's financial workflows. Depending on the customer's configuration, this may include:
- revenue organisation
- channel fees
- management fees
- property-level financial activity
- owner balances
- expenses
- reconciliation
- closing
- reporting
See a connection example
Without connection
- Source reservation
- Manual property setup
- Manual reservation entry
- Manual updates and cancellations
With connection
- Source reservation
- Authorized synchronisation
- Operent
Operent property
- Internal name
- Port Marlin 101
- Owner relationship
- Configured in Operent
- Management fee
- Configured in Operent
- Allocation centre
- Configured in Operent
- Business time zone
- Confirmed by the customer
Linked external record
- Provider
- Booking platform
- External listing name
- Ocean View Apartment Near the Beach
- External listing ID
- 987654321
- Sync status
- Example
The external commercial name can remain different from the internal name used by the customer. The relationship is preserved by the external identifier, not by matching names manually.
Integration availability depends on each approved partnership, technical implementation and authorised data scope.
MINIMUM DATA. DEFINED PURPOSE.
Request only what the connected workflow requires.
The exact data scope must be agreed with each partner.
For a property and reservation synchronisation use case, the initial request should be read-only and limited to the fields required to identify, create and keep records aligned.
See the fields and purposes table
| Data | Potential fields | Purpose |
|---|---|---|
| Property information |
|
|
| Reservation information |
|
|
| Synchronization metadata |
|
|
Data not required for the initial use case
Operent does not need generic access to platform data.
The initial connection does not require:
- guest messages
- private message history
- reviews
- search or browsing behaviour
- market-wide pricing data
- competitor pricing
- identity documents
- payment-card information
- full guest profiles
- listing publication controls
- pricing write access
- availability write access
- reservation write access
- guest communication access
Least privilege by default.
- User-authorised The connection would be established on behalf of a customer authorised to access the source account.
- Read-only first The initial property and reservation use case does not require Operent to modify the source platform.
- Data minimisation Only information required for the connected functionality should be processed.
- Tenant isolation Imported information must remain associated with the correct Operent company and authorised users.
- Traceability Each synchronised record would retain its provider, external identifiers and synchronisation history.
- Idempotency Repeated delivery or retrieval of the same source record must not create duplicate properties, reservations or financial records.
- Controlled updates Changes would be applied according to explicit field ownership and synchronisation rules.
- Revocable access Connections must support authorisation revocation and controlled handling of retained data.
Operent does not treat web scraping as a production partnership integration model.
WHERE EACH SYSTEM ENDS
Each platform remains authoritative in its own domain.
A financial operations platform for short-term rental businesses.
Operent connects properties, reservations, owners and the management company to a structured financial base.
Not a PMS
Where a customer already runs a PMS, that system stays the record of the stay and of distribution. Operent is designed to connect to it, not to replace it.
Not a channel manager
Operent does not distribute inventory between booking channels.
Not a marketplace
Operent does not sell accommodation or compete for bookings.
Not a pricing engine
Operent does not use partner data to compare or determine market pricing.
Not a listing manager
Operent does not need to publish or manage listing content for the initial synchronisation use case.
Not a data reseller
Operent does not request partner data to create a generic external database or redistribute it to unrelated third parties.
Frequently asked questions
The questions partner and integration teams usually raise first, about scope, permissions and product boundaries.
No. Operent is designed to support different technology stacks. Where an approved integration is available, a booking platform, PMS, channel manager or other source could each connect directly to Operent. A PMS or channel manager is an option, not a requirement.
Not for the initial property and reservation synchronisation model. The proposed initial scope is read-only. Operent would receive the authorised information required to initialise or match properties and keep reservations aligned. Any future write functionality would require a separate use case, explicit partner approval and its own permission scope.
No. Operent only needs the fields required to identify or initialise the corresponding property and associate reservations with it. It does not need to reproduce or republish the complete listing.
Yes, the model is designed for that. The same real-world property can have different external identities in a booking platform, PMS, channel manager or other system. Operent would maintain the internal property while preserving each authorised external relationship independently.
PARTNER WITH OPERENT
Let's define one useful connection.
Tell us which customer workflow your platform and Operent could improve together.
We will start with the smallest responsible scope that can deliver measurable value to shared customers.
Partnership contact [email protected]