The portfolio structure should answer the business question
A group may need to see performance by entity, property, building, unit or management contract. Those are related views, but they are not interchangeable. If the structure is unclear, teams end up rebuilding reports from separate operational and financial records.
We work through the ownership and management relationships before selecting the structure. A property can belong to one entity, be managed by another and contain several units with different agreements. The reporting design needs to preserve those distinctions while letting teams trace a charge or service request to the right place.
Connect the records that change together
| Connected records | Relationship to preserve |
|---|---|
| Property and unit | Establish durable identifiers, hierarchies and attributes. Agree how units, shared areas and assets relate to the financial and service view. |
| Customer and agreement | Trace an enquiry into approved terms and an active agreement. Define amendments, renewals, handovers and exits as explicit events. |
| Charges and collections | Specify the source of billing schedules and approved adjustments. Reconcile receipts and outstanding balances to the correct parties and agreements. |
| Facilities and service | Map requests, assignments and completion evidence to the relevant location or asset. Determine which specialist tools and service providers remain involved. |
Evaluate the application layer separately
CuriousRubik’s property material describes property and facilities management, including unit structures, commercial availability and agreement-related workflows. That offers a starting point for an application discussion, not a reason to assume every portfolio model fits the same package.
A review should establish what belongs in NetSuite, what belongs in the property application and what remains in a specialist system. Confirm current product identity, availability, licensing and integration requirements before planning around the application.
Migration must preserve the relationships
The difficult part is often connecting a unit to the correct customer, agreement, opening balance and unresolved service history. Agree the authoritative record and stable identifier for each. Decide which historic documents must remain accessible and which data needs to become active system records.
Use a representative set of property types and agreement patterns to test the proposed model. Include a change in terms, a partial receipt, a disputed charge and an outstanding service request. Have commercial, operational and finance owners review the same scenarios.
Make a charge traceable to its agreement.
A property manager and finance should be able to follow a charge back to the relevant unit, agreement version and approved event. An amendment, disputed charge or partial receipt then has a place in the same history, rather than a separate explanation in email.
Your advisers approve the legal, tax and accounting treatment. The implementation translates that treatment into records, permissions and checks that operational users can follow.