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
Getting data from JVs.
Ready for your 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
How do you get reliable data from JV partners?
To get data from JVs, agree what each joint venture partner will provide, when it is due and who owns the handoff. Map the source accounts to your reporting chart, check entity and period coverage, and flag missing information before consolidating. CREx data services organize this work around the reporting your investment team needs.
Start with the source
A data service built around the partner handoff.
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
What data should you request from a JV?
Define a package for the questions your team actually needs to answer. Scope the required detail and access with each partner.
Financial package
Agree financial statements, trial balance or supporting ledger, budget and variance reports. Record the accounting basis and period.
Property operations
Request the rent roll, leasing, occupancy or receivables information needed for your review, within the permitted source scope.
Debt and capital
Identify the debt schedule, capital budget and project reporting required. Keep source dates and missing documents visible.
Investor-level activity
Request relevant contribution, distribution and investor statements. Preserve their reporting basis separately from property operating results.
Plan and commentary
Include the business plan, partner commentary and explanations your reviewers need to interpret the reporting.
Collection / Account mapping / Review
From partner reports to a common reporting basis.
Agree the source and calendar.
Identify the authorized provider, expected files, reporting periods, due dates and delivery method. Record where partner approval or source access is still pending.
Map to your reporting chart.
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.
Review the package and gaps.
Check expected entities, periods and available control totals. Keep revised files, missing schedules and unresolved mapping questions attached to the review.
Prepare the agreed reporting output.
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
Keep property, JV and investor views clear.
Property view
What happened at the asset?
Keep the property's operating results, source accounts and reporting period together.
JV entity view
What belongs to the venture?
Identify the entity-level balances and activity needed to understand the JV reporting.
Investor view
What is being reported to you?
Use the agreed investor statements and finance-team-approved reporting basis. Do not assume the property result is 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
Make the missing information visible.
| JV package | Period supplied | Open item | Reporting treatment |
|---|---|---|---|
| JV North | September financials | New maintenance account | Account treatment pending review. |
| JV South | Quarter ending September | September monthly detail not supplied | Retain the quarterly label; monthly result unavailable. |
| JV West | September property package | Investor statement missing | Property view available; investor view incomplete. |
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
Agree what your team receives.
A JV data-service scope should identify the records your team will use after each reporting cycle:
- A source inventory showing partners, entities, expected packages and delivery contacts.
- An account crosswalk with the reporting definitions and mapping questions to resolve.
- A collection register showing received, late, revised and missing inputs.
- An agreed reporting output with period, entity, version and remaining limitations.
Assign a named CREx operator and partner contact for the agreed work. Define responsibilities for collection, mapping review, corrections and acceptance before delivery starts.
Data services / Portfolio review
Put JV data where your team needs it.
Data services
A defined reporting handoff
Scope the reports, mappings and delivery your team needs. Discuss bespoke reporting or warehouse requirements through CREx Core.
Discuss a data project ↗Portfolio foundation
JV data in CREx OS
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
Context for the next review
Explore how Intelligence sits above OS. Confirm available workflows and AI access for your team; service scope determines the supported path.
Explore Intelligence ↗Joint venture data / Questions
Questions about getting data from JVs.
How do we get data from our JV partners?
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.
Can CREx work with JV data when we do not control the property-management system?
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.
What financial data should we request from a real estate JV?
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.
What happens when JV partners use different charts of accounts?
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.
Can a quarterly JV report be treated as current monthly data?
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.
Is property-level reporting the same as our investor-level JV position?
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.
Is this linked to CREx data services?
Yes. The starting scope is data collection, account mapping, checks and reporting delivery. Discuss bespoke requirements through CREx Core, 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
A common basis for the reporting conversation.
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 the JV roster.
Show us the reporting gap.
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