Owner reporting / Evaluation guide
What should a lease-to-ledger review compare?
Compare the relevant executed lease and amendments with the authorized charge and reporting records for the agreed period. Keep the source page, effective date and unresolved interpretation with each proposed difference. The responsible team confirms any correction or tenant communication.
By CREx Software · Editorial review 2026-10-18
Agree the document set and review boundary first.
An incomplete lease library can leave a question unresolved even when a ledger is available. Identify which executed documents are present, the property and space identifiers, and the reviewer responsible for interpreting terms. Discuss collection, extraction or ongoing review requirements as a defined engagement.
What to confirm before choosing the scope
| Requirement | What to confirm | What to retain |
|---|---|---|
| Document set | Identify executed leases, amendments and relevant schedules. | Record missing pages and document versions. |
| Charge period | Confirm the period and charge records being compared. | Keep effective dates and concessions distinct. |
| Source match | Match the property, unit or space across records. | Flag uncertain matches for review. |
| Proposed difference | Link the term to the relevant ledger entry. | Record the source page and question. |
| Correction | Confirm interpretation and authorization with the responsible team. | Agree who may change records or communicate externally. |
These are buyer and reviewer questions. They do not claim that the checks run automatically in CREx or establish a missing capability in another product.
Review example
A source question to work through
A parking amendment begins after the ledger period under review. Retain its effective date rather than treating the missing earlier charge as a confirmed billing error.
Record the source, affected output, person responsible and next review date. Keep an unanswered item open until the appropriate reviewer accepts its treatment.
Where CREx fits
CREx OS is the portfolio data and reporting foundation beneath CREx Intelligence. Agree source coverage, reporting definitions, delivery expectations and review responsibilities for your account. Confirm the specific AI environment and available capabilities in the proposal. Your team reviews the evidence and makes the decision.
Eligible CREx OS accounts include support from the CREx team. Work with a named CREx operator to agree reporting responsibilities, shared capacity and coverage for your account.
Core is separately scoped Consulting for bespoke data projects. It is separate from the data foundation included in OS.
Questions to bring to the discussion
Does this promise every lease term will be found or every charge recovered?
Does the review update the property-management system automatically?
Continue with the relevant guide
Discuss your requirements
Bring the source question.
Start with the manager roster, reporting purpose and open questions. We can discuss the relevant CREx scope and what needs confirmation.
Book a demo ↗