Owner reporting / Evaluation guide
How should owners validate property data before investor reporting?
Check the reporting scope, source periods, account mapping and relevant control totals before a property package enters an investor report. Keep unresolved differences visible and name the reviewer who accepts the package for its intended use.
By CREx Software · Editorial review 2026-10-18
A received package still needs an acceptance decision.
A file arriving on time does not establish that its figures are comparable. Separate delivery status from review status. An accepted package can still carry a stated limitation; the limitation belongs beside the output that relies on it.
What to confirm before choosing the scope
| Requirement | What to confirm | What to retain |
|---|---|---|
| Coverage | Match the property and entity list to the reporting scope. | Record excluded or missing properties. |
| Period | Distinguish a month-end snapshot from activity during the month. | Keep source date, reporting period and receipt date. |
| Mapping | Review source account meaning and changes to the reporting chart. | Record unmapped accounts and the proposed treatment. |
| Control totals | Compare agreed totals to the supplied source. | Explain differences using the reviewer's agreed tolerance. |
| Acceptance | Name the reviewer and intended use of the package. | Record limitations and the next action. |
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 September trial balance includes a new repairs account. Leave its treatment open until the reviewer checks the underlying entries. Receiving the file does not settle whether an item belongs in operating expenses or capital expenditure.
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 describe automatic CREx checks?
What should happen to an unresolved difference?
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 ↗