Discovery
Confirm MRI products, environments, asset structures and the target business process.
Partner & resellerConnect short-term leasing with MRI PMX.
The Crenex integration with MRI PMX connects short-term leasing operations with property and finance workflows. Crenex manages spaces, bookings and agreements; the agreed integration maps the data your MRI environment needs.
Clear responsibilities
Each system does the job it was built for.
Crenex connects the operational booking record with the property and finance processes managed in MRI PMX.
| 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. |
Crenex is listed in MRI Software’s official partner directory. View Crenex on MRI Software.
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
What data connects Crenex and MRI PMX?
The mapping connects the information needed for the customer’s property and finance process. The booking remains the operational record in Crenex.
Property and lease references
Property, lease and other identifiers associate booking data with the records required by the agreed MRI mapping.
Income categories and transactions
Mapped income categories and transaction details prepare the booking information for the customer’s finance workflow.
Booking context
Space, dates, tenant and agreement details remain available in Crenex. The integration passes the fields agreed for the deployment.
Direction and validation
The integration design specifies which system provides each field, where it goes and which validation rules apply.
Deployment approach
How the integration is prepared.
Start with your MRI product, version, asset structure and finance process. Agree the scope and test representative bookings before rollout.
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.
MRI integration questions
Define the scope before rollout.
Which data can Crenex exchange with MRI PMX?
The configured mapping can include property and lease references, income categories and booking transaction data. The exact fields, direction and validation rules depend on the customer’s MRI environment and agreed integration scope.
Is the integration the same for every MRI customer?
Each deployment is scoped around the customer’s MRI product, version, asset structure and finance process. Supported fields and integration behaviour are confirmed during technical discovery.
Which system handles accounting?
MRI PMX remains the property and finance system. Crenex manages the short-term leasing workflow, keeping spaces, bookings, approvals and agreements together and preparing the information required for the finance handoff.
What does a rollout involve?
Confirm the MRI environment and business process, agree the field mappings, and test representative bookings and validation rules. Rollout then follows the agreed portfolio scope and operational responsibilities.