Site-Level Profit and Loss Reporting
How a multi-location restoration company built one profit and loss view in Zoho Analytics, joining Bills, Expenses, Invoices, and Journal Entries and segmenting by site and class.
Client details generalized to protect confidentiality.
Multi-location operators who can see company-level financials but cannot answer which locations are actually profitable.
The Challenge
Financial reporting existed at the company level and nowhere else. Bills, expenses, invoices, and journal entries all carried the information needed to segment by location, but no report brought them together. Determining whether a specific site was profitable meant exporting four reports and joining them in a spreadsheet, which happened rarely enough that underperforming locations went unexamined for months.
The Solution
Unified Query Table
A query table joins Bills, Expenses, Invoices, and Journal Entries into one dataset that can be reported on together.
- Query table across four Books sources
- Common site and class dimensions
- Consistent date and period handling
- Sign normalization across sources
Site and Class Segmentation
Every line resolves to a site and a class, which is what makes location-level profit and loss possible.
- Site dimension applied across sources
- Class mapping validated
- Unassigned lines reported separately
- Roll up from site to region
Profit and Loss View per Site
Each location reports its own revenue, cost, and margin in the same format as the company view.
- Standard P and L layout per site
- Period comparison against prior
- Margin percentage by site
- Drill-through to source transactions
Exception and Data Quality Reporting
Transactions missing site or class assignment are surfaced, since they are what makes a location view wrong.
- Unassigned transaction report
- Count and value of exceptions
- Trend on assignment completeness
- Owner notification for cleanup
Apps in This Solution
Zoho Analytics
Zoho Books
Under the Hood Technical detail
- Join Design
- The four sources are unioned into a single query table with normalized signs and a common dimension set, rather than reported side by side. Side-by-side reporting cannot produce a margin figure, which was the whole point.
- Dimension Discipline
- Site and class must be present on every transaction for the view to be correct. Rather than assume compliance, the build includes an exceptions report showing unassigned value, so the reader knows how much of the picture is missing.
- Sign Normalization
- Bills, expenses, invoices, and journal entries express direction differently. Normalizing at the query table means every downstream report inherits the correct treatment rather than each report handling it separately and inconsistently.
- Drill-Through
- Site-level figures drill through to source transactions, because the first reaction to an unexpected location number is disbelief. Being able to open the underlying transactions is what makes the report usable in a management meeting.
- Notable Constraint
- Shared overhead does not belong to a single site. Allocation rules are applied explicitly and shown as an allocation line rather than blended into site costs, so a site manager can see what was allocated and on what basis.
The Results
- Every location has a profit and loss view in the same format as the company view.
- Unassigned transactions are visible, so the report states its own completeness.
- Site numbers drill through to source transactions during review meetings.
Company Financials but No Site Detail?
We have built segmented financial reporting in Zoho Analytics for multi-location operators. Tell us how your locations are tracked.