Discovery
Confirm MRI products, environments, asset structures and the target business process.
Partner & resellerConnect short-term leasing with MRI PMX.
Crenex manages the request-to-booking workflow. MRI remains the property and finance backbone. The configured integration connects the structured data required between them.
Clear responsibilities
Each system does the job it was built for.
The integration avoids turning MRI into a short-term leasing front end or turning Crenex into the accounting system.
| Operational need | Crenex | MRI PMX |
|---|---|---|
| Flexible leasing workflow | Requests, bookings, spaces, dates, approvals and agreements. | Receives or references the approved property and finance data required by the configured process. |
| Commercial context | Keeps the tenant, use, rate, documents and booking history together. | Remains the core property-management and accounting environment. |
| Finance handoff | Validates mapped fields before the booking moves forward. | Processes the resulting finance workflow according to the client configuration. |
| Reporting | Short-term leasing, demand, bookings and portfolio performance. | Property and financial reporting within the MRI estate. |
Connected flow
From approved booking to mapped data.
The exact direction, fields and validation rules are agreed for the customer’s MRI environment.
Map
Confirm assets, identifiers, categories and required fields.
Book
Run the short-term leasing process in Crenex.
Validate
Check the commercial and finance data required for handoff.
Connect
Send or synchronise the agreed fields through the integration.
Process
Continue the property or finance workflow in MRI PMX.
Review
Retain traceable context for operational follow-up.
Data in context
Finance fields stay connected to the booking.
Crenex keeps the operational record behind the finance information, so teams can return to the space, dates, tenant and agreement when they need to investigate.
Identifiers
Property, lease and other master-data references used by the deployment.
Income categories
Mapped categories required to prepare the transaction correctly.
Booking context
The commercial record that explains where each transaction came from.
Deployment approach
Start with the real MRI environment.
Product names alone are not enough. The integration design must reflect the customer’s MRI product, version, data model and finance process.
Mapping & testing
Agree fields and rules, then test representative bookings before rollout.
Controlled rollout
Launch with a defined portfolio scope and validate operational ownership.
MRI modules and integration scope vary by customer. Final capability is confirmed during technical discovery.