Multi-Venue Consolidated Reporting
This use case describes how to build consolidated reporting for restaurants, cafés and bars operating across multiple venues.
You will use branches to represent venues, shared reporting structures for P&L and Cashflow, and dashboards that show both venue-level and group-level performance.
If your venues sit in multiple legal entities, combine this pattern with Multi Entity Group Model or Multi Entity Consolidation (QBO/Xero).
When to use this pattern
Use this pattern when:
You run more than one venue and want a single consolidated view.
You need to compare venues side by side in a consistent format.
You report group performance to owners, investors or lenders.
This pattern assumes that venue operations are similar enough that a shared reporting layout makes sense.
Architecture overview
The consolidated reporting structure includes:
Branch tree
One branch per venue.
Optional regional branches if the network is large.
Head office branch for shared costs.
Shared P&L structure
Same revenue, COGS and Opex categories in each venue.
Consistent mapping from data sources into categories.
Reports and dashboards
Group P&L, Cashflow and Cash Waterfall.
Venue comparison views.
Drilldowns from group totals to individual venues.
Decide the reporting structure
Define a standard P&L layout for all venues, for example:
Revenue: food, beverage, other.
COGS: food, beverage.
Gross profit and gross margin.
Staff: front of house, back of house, managers.
Other Opex: rent, utilities, marketing, repairs, licences.
Venue EBITDA.
Document this structure so that every venue follows it.
Build the branch tree for venues
Create a model with branches such as:
GroupVenue - City CentreVenue - Suburb AVenue - Suburb BHead Office
If you have many venues, consider grouping them under regional branches, for example Region North, Region South, with venues as children.
Branches will roll up automatically into the group branch for consolidated output.
Map data into each venue branch
Populate each venue branch with its own:
Revenue variables (food, beverage, other income).
COGS variables.
Staff and Opex variables.
Data can come from:
PDF or Excel exports from accounting or POS systems.
Xero or QuickBooks, if the chart of accounts is set up to segment venues.
CSV imports where you maintain venue splits manually.
Apply the same category mapping for each venue so that reports align across the network.
Separate head office and shared costs
Use a dedicated branch such as Head Office or Central for:
Executive salaries.
Central marketing.
Administration and finance.
System licences and group insurances.
This ensures venue branches reflect local economics, while the group branch includes both venue and central costs.
If you need allocated views, see Build Cross Branch Drivers and Dependencies to allocate central costs back to venues using revenue or other keys.
Build group and venue report views
Use Model Reef reports and dashboards to provide:
Group level P&L and Cashflow.
Venue level P&L views.
Comparisons such as:
Revenue per venue.
Gross margin per venue.
Staff cost as a percentage of revenue per venue.
Venue EBITDA and contribution.
You can create:
Group reports that include breakdowns by branch.
Venue specific reports for local managers that only show their venue branch if you plan to apply branch-level permissions in future.
Use scenarios for network planning
For planning and budgeting, clone the base model into separate models representing scenarios such as:
Base trading plan.
Downside trading plan.
Expansion with additional venues.
Rationalisation with planned closures.
For each scenario model, adjust venue assumptions and compare:
Group revenue and EBITDA.
Cash requirements and funding needs.
Venue profitability and potential closure candidates.
Because scenarios are separate models, you can modify them independently while preserving the original structure.
Standardise across the hospitality group or portfolio
To use this pattern across a portfolio of hospitality clients or venues:
Keep the branch and category layout as consistent as possible.
Use naming conventions for venue branches and key variables.
Maintain a central assumption library for shared assumptions, such as wage escalation or general cost inflation.
This makes it easier to train staff and reuse patterns across different models.
Check your work
All venue branches follow the same category structure.
Head office costs are clearly separated but included in group results.
Group P&L matches the sum of venues plus central costs.
Dashboards and reports allow users to move quickly between group and venue perspectives.
Troubleshooting
Related guides
Last updated