In real projects...

Multi-property consolidation needs one chart logic and local statutory adapters—otherwise “group view” is fiction. Compare outlet operations in F&B and banqueting.

A common issue we see...

Properties post to different revenue buckets; corporate forecasting becomes reconciliation hell.

For example...

  1. Define brand standards for POS codes and service charges.
  2. Automate intercompany eliminations for shared services.
  3. FX policies for fees received in non-functional currency.
  4. Segment reporting by property, brand, and owner structure.
  5. Monthly bridge from operational stats (RevPAR) to GL.

Common mistakes (and how to avoid them)

  • Letting management contracts vary without system support.
  • Ignoring inventory valuation across transfers between sites.
  • Weak access between franchisee and brand reporting.
  • Underestimating tip pooling and payroll complexity.

Note: Representative scenarios for education; validate with hospitality finance advisors.

Methodology: This article is an educational guide built from public ERP documentation and widely used implementation patterns. Any mini “scenario walkthroughs” are illustrative and not client-specific.

Multi-property consolidation in hospitality ERP requires consistent chart of accounts usage, aligned close timing, and clean intercompany eliminations. This walkthrough creates the process that makes group reporting reliable.

  1. Confirm that all properties use a shared chart of accounts with property-specific cost centres rather than property-specific account codes.
  2. Publish a group close calendar with deadlines for each property to complete local close and submit data for consolidation.
  3. Run intercompany transaction reports at each property before consolidation to identify all transactions that need elimination at group level.
  4. Post elimination entries for intercompany management fees, shared service recharges, and intercompany loans at the group level.
  5. Reconcile the consolidated balance sheet and income statement to the sum of property results after eliminations.
  6. Produce the group management accounts with property-level drill-down and distribute to leadership within the agreed reporting deadline.

Artifacts to expect:

  • Group close calendar with property submission deadlines.
  • Intercompany transaction schedule per property.
  • Elimination journal entries with supporting documentation.
  • Consolidated trial balance reconciled to property totals.
  • Group management accounts with property comparison.

What usually goes wrong (failure modes)

  • Properties use different account codes for the same expense, requiring manual mapping before consolidation
    Each property has customised its chart of accounts independently, and consolidation requires manual account code mapping every period.
    Mitigation: Enforce a shared chart of accounts structure across all properties, with property-level differentiation achieved through cost centres rather than different account codes.
  • Intercompany eliminations are missed, inflating group revenue and costs
    Management fees and shared service recharges between entities are not consistently identified and eliminated at group level.
    Mitigation: Maintain an intercompany transaction schedule in the ERP listing all regular intercompany flows. Run an intercompany report before consolidation and reconcile to the schedule.
  • Consolidation is delayed because properties close on different schedules
    Some properties complete local close two weeks after others, creating a consolidation bottleneck and delaying group reporting.
    Mitigation: Publish a group close calendar at the start of the year with firm deadlines for property close and data submission. Escalate non-compliance to group finance leadership.

Controls and evidence checklist

  • Enforce a shared chart of accounts with property-level cost centres across all entities.
  • Publish and enforce a group close calendar with deadlines per property.
  • Maintain an intercompany transaction schedule and reconcile before each consolidation.
  • Require elimination documentation for all intercompany entries at group level.
  • Reconcile consolidated results to the sum of property results after eliminations.
  • Audit a sample of intercompany transactions each quarter to confirm eliminations are complete.

Implementation checklist

  1. Standardise the chart of accounts across all properties before configuring consolidation reporting.
  2. Document all regular intercompany transaction types and build an elimination schedule.
  3. Configure the consolidation module to roll up property data using consistent account codes.
  4. Test the consolidation with one full period of data from all properties.
  5. Publish the group close calendar and communicate property submission deadlines.
  6. Run the first consolidated management accounts and review with group finance before distribution.

Frequently asked questions

Where do teams usually lose time in multi-property ERP consolidation?

Most time is lost when properties use different account codes for the same expense category, requiring manual mapping before consolidation reports can be produced. Enforcing a shared chart of accounts across all properties—with property-specific cost centres rather than property-specific account codes—is the most effective structural fix for this. A two-week account standardisation project before the next financial year start eliminates the most common consolidation bottleneck.

What intercompany transactions should we prioritise in eliminations?

Review the intercompany elimination schedule at the end of the first full consolidation cycle to confirm all intercompany transactions are correctly identified and eliminated. Missed eliminations—particularly intercompany management fees and shared service recharges—are among the most common audit findings in multi-entity hospitality groups. A documented intercompany transaction schedule, reviewed and signed off by each property finance manager, is the most reliable control.

How should we manage consolidation when a new property is acquired?

Adjust the consolidation timetable when new properties are acquired or when a property changes its local accounting period. The consolidation process requires all entities to close on the same schedule—a mismatch in close timing between properties causes significant manual effort at each period-end until the discrepancy is resolved. Plan a six to eight week integration project for each new acquisition to align the chart of accounts, close calendar, and intercompany transaction setup before the first consolidation.

Sources

Conclusion and next steps

Multi-property consolidation in ERP depends on a shared account structure, a enforced close calendar, and a documented intercompany elimination schedule.

Start by standardising the chart of accounts and publishing a group close calendar. These two structural changes eliminate the most common consolidation delays before any system changes are needed.