Fulfillment-Based Revenue Dashboards
How an organization separated upcoming revenue from revenue actually earned in Zoho Analytics, rolling up task billable amounts by fulfillment status.
Client details generalized to protect confidentiality.
Organizations whose revenue depends on work delivered, where a single revenue figure blends what is scheduled with what is complete.
The Challenge
Revenue reporting showed one number that mixed scheduled work, delivered work, invoiced work, and collected cash. Leadership read it as revenue and finance read it as pipeline, and both were partly right. Because delivery status lived on tasks and revenue reporting was built at the project level, separating the four states required manual work nobody had time for during a reporting cycle.
The Solution
Status-Based Revenue Rollup
Billable amounts roll up by fulfillment status, so each state reports as its own figure.
- Task billable amounts as the base
- Status dimension across Scheduled, Delivered, Invoiced, Paid
- Rollup to project and programme
- Period assignment by status date
Upcoming Versus Earned Separation
Scheduled and delivered report separately, which is the distinction leadership needed.
- Upcoming revenue from scheduled tasks
- Earned revenue from delivered tasks
- Invoiced and collected as further states
- Movement between states over time
Composite Dashboards
One dashboard shows all four states together, so the relationship between them is visible.
- Four-state summary view
- Trend per state by month
- Conversion rate between states
- Drill-through to underlying tasks
Aging and Bottleneck Visibility
Work sitting too long in one state is flagged, since the gap between delivered and invoiced is usually where cash is stuck.
- Aging within each state
- Delivered but not invoiced report
- Invoiced but not paid aging
- Owner notification on aged items
Apps in This Solution
Zoho CRM
Zoho Projects
Zoho Analytics
Under the Hood Technical detail
- Base Grain
- The rollup is built on task billable amounts rather than project totals, because status lives at task level. Reporting at project level and inferring status is what made the original number ambiguous.
- Status Dating
- Each state carries its own date, so a task delivered in one month and invoiced in the next reports correctly in both views. A single date field would force a choice about which month the revenue belongs to and be wrong for one of the two audiences.
- State Conversion
- Movement between states is reported as a conversion rate, which surfaced that delivered-to-invoiced was the slowest transition by a wide margin. That was the finding with the largest cash impact and it was previously invisible.
- Definition Ownership
- Upcoming and earned are defined once in Analytics rather than in each report. The prior disagreement between leadership and finance was a definitional problem, not a data problem.
- Notable Constraint
- Task billable amounts depend on tasks being maintained. The dashboard shows the count of billable tasks with no amount set, so the data quality gap is visible next to the figures rather than silently understating revenue.
The Results
- Upcoming and earned revenue report as separate figures.
- Delivered but not invoiced work is visible as an aging report.
- Leadership and finance work from one set of definitions.
One Revenue Number Meaning Four Things?
We have built revenue recognition and fulfillment reporting in Zoho Analytics. Tell us how your revenue is currently reported.