Financial Reporting

Pride’s financial reporting is currently fragmented and untrustworthy. Leadership lacks the P&L visibility needed for daily decision-making, and Xero data quality issues prevent informed strategic planning.

Current State

What Exists

• Xero accounting system: General ledger and reconciliation
• Square POS: Transaction records (bar revenue and tickets)
• TryBooking: Attendance and ticket pre-sale data
• Deputy: Rostering and labour data

What’s Missing

• Event-level P&L: No report showing revenue and costs per event
• Weekly P&L: No consolidated P&L summary delivered to leadership
• Cash forecasts: No projection of next 30 days’ cash position
• Trusted reporting: Xero P&L/Balance Sheet “not trusted by leadership” (per financial snapshot)
• Real-time visibility: Financial snapshot available only at month-end; decisions made without current data

Breakdown by Reporting Type

Report	Current	Needed	User	Frequency
Event P&L	None	Automated, 24h post-event	Emily, Mat	Per-event
Weekly P&L	None	Automated, Monday morning	Mat, Monique, Emily	Weekly
Monthly P&L	Xero month-end	Trusted and verified	Mat, stakeholders	Monthly
Cash forecast	None	Rolling 30-day projection	Mat, Monique	Daily/weekly
Supplier status	Manual invoice tracking	Automated from Xero	Monique, Tom	Weekly
Labour reporting	Deputy rosters (not P&L)	Integrated Deputy→Xero P&L	Mat, Monique	Weekly

Data Quality Issues

Xero Problems

• Unreconciled accounts: Uncleared items blocking trust in P&L
• Account code inconsistency: Transactions coded to wrong accounts; manual reclassification required
• Clearing account chaos: Cash movement between accounts not properly coded; difficult to trace
• Payroll integration: Deputy rosters manually transcribed to Xero; error-prone and delayed

Square Integration Gaps

• Event tagging: POS transactions not tagged to specific events; impossible to calculate event-level revenue
• Stock cost tracking: Alcohol costs not linked to events or nights
• Margin analysis: Revenue per event available, but costs unavailable for comparison

TryBooking Data Loss

• Attendance data: Printed and discarded; historical attendance patterns not retained
• Pre-sales tracking: Ticket pipeline data available but not integrated with forecasting
• Customer segmentation: No tracking of repeat customers or acquisition channels

Deputy Payroll Leak

• Rosters → Xero manual: Complex due to six different bartender pay rates
• Spreadsheet bridge: Tom may have built automation; unverified and undocumented
• Timing lag: Payroll data available Tuesday; P&L reporting available 15+ days later

Impact on Decision-Making

Operational Level (Venue Manager)

Monique lacks visibility to make autonomous decisions:

• Cannot see weekly P&L to identify cost overruns (performer fees, stock, labour)
• Cannot approve supplier invoices without CEO review (no budget visibility)
• Cannot adjust staffing or stock ordering based on sales trends
• Cannot diagnose why Saturday revenue underperformed until reconciliation (3 weeks later)

Programming Level (Head of Programming)

Emily cannot analyse event performance:

• No P&L per event; cannot determine which event types (DJ, drag, kakaoke) are profitable
• No attendance trend analysis; cannot optimise programming mix
• Cannot identify seasonal patterns or competitor impact
• Cannot forecast impact of schedule changes on revenue

Strategic Level (CEO)

Mat lacks visibility for strategic decisions:

• Cannot model capital raise scenario (“What if we reduce performer cost 10%?”)
• Cannot determine if licence reclassification ROI justifies investment
• Cannot assess multi-venue expansion feasibility
• Cannot detect Saturday collapse in real-time; response delayed 3+ weeks

Gaps Blocking Strategic Initiatives

Kitchen Opening Decision

Insufficient data to model impact:

• No baseline of current food revenue (external pizza supplier volumes unknown)
• No staffing cost estimate for kitchen operation
• No forecast of weekday afternoon or Sunday market revenue potential
• Cannot calculate ROI of licence reclassification savings

Licence Reclassification

Missing data:

• Security cost baseline ($2,000/week claimed, but unverified against supplier contracts)
• Insurance premium impact of licence change unknown
• Food-primary operational model costs unmodelled

Capital Raise

Insufficient trusted financials to present to investors:

• 8 years of historical data in Xero unverified
• Monthly P&L not trusted by leadership
• No multi-year trend analysis or benchmarking
• Forecasts impossible due to reporting gaps

Multi-Venue Expansion

Cannot model three-venue P&L:

• Cannot isolate venue-level profitability (Footscray only venue currently)
• Cannot determine if expansion would improve fixed-cost leverage
• Cannot forecast break-even for new venues

Enabling Solution: Humphrey Intelligence App

Humphrey Intelligence App addresses all gaps through integrated reporting:

Phase 1: MVP (Weeks 1–2)

• Event P&L dashboard (Square + TryBooking data)
• Event list with revenue and attendance
• Historical event comparison

Phase 2: Financial (Weeks 3–4)

• Weekly P&L consolidated view
• Cash forecast dashboard (30-day rolling projection)
• Xero integration (post-cleanup of account coding)

Phase 3: Operations (Weeks 5–6)

• Labour cost integration (Deputy→Xero bridge)
• Customer segmentation (repeat attendees, acquisition channels)

Phase 4: Intelligence (Weeks 7+)

• Scenario planning (“What if Saturday +20%?”)
• Supplier performance and payment tracking
• Multi-venue P&L (future expansion)

Prerequisites for Success

Data Quality

1. Xero cleanup: Verify and reclassify unreconciled accounts before Phase 2
2. Account code consistency: Define standard coding for performers, security, stock, labour
3. Square event tagging: Implement transaction tags for each event/night
4. Deputy→Xero bridge: Verify Tom’s spreadsheet; document rate logic; automate integration

Reporting Discipline

1. Weekly P&L ownership: Shae (bookkeeper) delivers Monday morning snapshot; automated via Humphrey Intelligence App when ready
2. Event P&L SLA: 24-hour delivery post-event close (Shae or automated via Humphrey dashboard)
3. Forecast review cadence: Tuesday morning (pre-Saturday) and Friday evening (post-event)

Stakeholder Adoption

1. Weekly P&L email: Automated delivery to Mat, Monique, Emily (Monday)
2. Alert system: Red flags when revenue <$25k threshold or cost >budget
3. Dashboard onboarding: Training for Mat and Monique on dashboard navigation

Key Facts

• Current reporting: Month-end Xero snapshots only; 15–20 day lag
• Missing data: No event P&L, weekly P&L, cash forecasts, or trusted trend analysis
• Data quality: Xero has unreconciled accounts, inconsistent coding; not trusted by leadership
• Decision impact: Leadership making strategic decisions without current financial data
• Bottleneck: CEO manually extracting ad-hoc reports due to no standard reporting framework
• Integration gaps: Square, TryBooking, Deputy data isolated; no unified view

Related Pages

• Humphrey Intelligence App — technical implementation and phases
• Cash Forecasting — weekly cash projection needs
• CEO Bottleneck — reporting requirements for delegation
• Automation Opportunities — Priority 2 automation for P&L and cash reporting
• Strategic Plan — capital raise and multi-venue expansion dependent on trusted financials