Entity and partner register
List the JV, operating partner, underlying properties and reporting entities. Keep partner and property identifiers consistent.
Data services / Joint venture reporting
Get financial and property data from your joint venture partners into a consistent reporting basis. CREx data services bring collection, account mapping and review into an agreed delivery scope.
The short answer
To get data from JVs, agree what each partner will provide, when it is due and who owns the handoff. Map source accounts to your reporting chart, check entity and period coverage, and flag gaps before consolidation. CREx data services can organize the work around your agreed reporting requirements.
Start with the source
Your JV operating partner may prepare the reporting package while a separate property manager holds the operating records. Your team needs to understand what arrived, which entity it describes and what is still missing.
Start with the partner's permitted reporting package. Agree whether additional reports, files or direct source access are available. Define the reporting calendar and a contact for follow-up.
CREx data services bring collection, chart-of-accounts mapping and review into an agreed scope. The destination may be a reporting pack, an existing reporting environment or the CREx OS portfolio foundation.
Explore our data-services scope · Working directly with property managers?
Define the package
Define a package for the questions your team actually needs to answer. Scope the required detail and access with each partner.
List the JV, operating partner, underlying properties and reporting entities. Keep partner and property identifiers consistent.
Agree financial statements, trial balance or supporting ledger, budget and variance reports. Record the accounting basis and period.
Request the rent roll, leasing, occupancy or receivables information needed for your review, within the permitted source scope.
Identify the debt schedule, capital budget and project reporting required. Keep source dates and missing documents visible.
Request relevant contribution, distribution and investor statements. Preserve their reporting basis separately from property operating results.
Include the business plan, partner commentary and explanations your reviewers need to interpret the reporting.
Collection / Account mapping / Review
Identify the authorized provider, expected files, reporting periods, due dates and delivery method. Record where partner approval or source access is still pending.
Translate source accounts into your reporting definitions. Retain the source label and agree treatment of new accounts, reclassifications and capital items with the appropriate reviewer. See a worked account mapping example.
Check expected entities, periods and available control totals. Keep revised files, missing schedules and unresolved mapping questions attached to the review.
Define the pack or delivery destination, accepted version and reviewer. Agree who follows up with the partner when a package is incomplete.
Collection methods, supported sources, refresh cadence, review duties and delivery outputs are agreed for the engagement. Direct APIs, daily feeds and automatic approvals are confirmed only where supported in scope.
Define what each number represents
Property view
Keep the property's operating results, source accounts, reporting period and accounting basis together. Record whether the figures describe the whole property.
JV entity view
Identify the venture, the entities included and the balances or activity the package covers. Keep its reporting period and any entity exclusions visible.
Investor view
Record the investor, ownership interest, effective date and the reporting treatment approved by your finance team. Retain the investor statement; a property result alone does not establish the investor result.
Agree the relationships between these views before combining them. Label the entity, period and basis in the output so similar-looking numbers are not treated as equivalent.
Collection register
| JV package | Period supplied | Open item | Reporting treatment | Next action and owner |
|---|---|---|---|---|
| JV North | September financials | New maintenance account | Account treatment pending review. | Partner finance contact: explain the account. Owner accounting reviewer: approve the reporting treatment. |
| JV South | Quarter ending September | September monthly detail not supplied | Retain the quarterly label; monthly result unavailable. | Partner contact: provide the requested monthly detail. Owner analyst: keep the period limitation in the review. |
| JV West | September property package | Investor statement missing | Property view available; investor view incomplete. | Partner contact: supply the investor statement. Owner finance reviewer: confirm ownership basis and completeness. |
A missing statement or unresolved mapping remains an open item. Agree the source contact, next action and reviewer before accepting the final reporting pack.
The delivery scope
A JV data-service scope should identify the records your team will use after each reporting cycle:
Where CREx operator support is included in the engagement, agree a named CREx operator and partner contact, with shared capacity, coverage and collection, mapping review, correction and acceptance responsibilities defined in scope.
Keep the authorized source, reporting entity, period, expected file, mapping version, unresolved item and acceptance owner together. Use the worksheet to agree who follows up and what remains open before accepting the package. Record the approved ownership basis and effective date in the accompanying reporting notes; the worksheet does not calculate an investor share.
This is a manual review template. The separate example uses fictional information to show how to record an open item. Neither file demonstrates a live CREx workflow or confirms an integration, approval or delivery feature.
Data services / Portfolio review
Separately scoped projects
Agree the reports, mappings and delivery needed for a bespoke reporting or warehouse project through CREx Core consulting. This is separate from the data foundation within OS.
Discuss a data project ↗Portfolio foundation
When the destination is your CREx OS portfolio review, agree the entity context and reporting inputs. The data foundation is included in OS.
Explore CREx OS ↗Asset-management work
CREx Intelligence builds on the OS portfolio foundation for asset-management questions and reviews. Confirm available records, workflows and AI access for your team.
Explore Intelligence ↗Joint venture data / Questions
Agree the reporting package, source contact, permitted access and delivery calendar with each joint venture partner. Map the received accounts to your reporting chart, check the period and entity coverage, and keep missing or unresolved items visible. CREx data services scope this collection and reporting work around your portfolio.
Start with the data your partner is authorized to provide. An agreed report or file package can be a starting point. Any direct system access, source formats and recurring delivery arrangements must be confirmed with the relevant parties.
Start with the reports your review requires: financial statements, trial balance or supporting ledger, budget comparison and relevant property schedules. Add debt, capital and investor statements where needed. Confirm the entity, reporting period, accounting basis and permitted detail with your finance team and partner.
Create a source-to-reporting crosswalk for each partner. Review account meaning, sign conventions and treatment of operating and capital items. Agree who reviews new accounts and changes before the mapped results enter your reporting pack. Use the chart-of-accounts mapping guide to plan those decisions.
Keep the reported period and receipt date separate. A quarterly package does not establish a current monthly result. Identify the missing period and obtain the required source rather than filling the gap with an older figure.
They answer different questions. Label property, JV entity and investor views separately. Your finance team confirms the ownership basis and reporting treatment; a property result alone does not establish the investor-level figure.
Yes. The starting scope is data collection, account mapping, checks and reporting delivery. Discuss bespoke requirements through CREx Core consulting, or explore CREx OS when the data will support ongoing portfolio review. The OS data foundation is included in OS; Core is a separate engagement.
Reporting references
INREV's reporting guidance emphasizes comparable, transparent information and consistency between reports and financial statements. The NCREIF PREA Reporting Standards support consistent real estate investment reporting, and their 2025 edition added recommended asset- and investment-level reporting.
INREV reporting guidance · PREA reporting standards · NCREIF PREA asset-level reporting update
Prepared by CREx Software. Sources reviewed October 18, 2026. These references inform the reporting discussion; they do not certify or endorse CREx. Requirements and data access are agreed for the specific venture and engagement.
Start with the partner list
Bring your partner list, the reporting chart and an example of the package you receive. We will use those requirements to scope data collection, mapping, review and delivery.
Discuss JV data services