Separate recurring contract value from collected cash
A late payment makes the recurring-revenue chart dip even though no subscription changed.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Metric design · Data semantics
Estimated field mix
- Data engineering100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional SaaS analyst reports expansion revenue differently from finance because snapshots, refunds and contract changes are joined at incompatible grains.
Setup prerequisites
- Create a synthetic source schema and local transformation project.
- Use integer minor units and distinct reporting currencies.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Define contract value and cash collection as separate measures.
- Document refund and unpaid-invoice treatment.
- Keep currency amounts separate without implicit conversion.
Implementation constraints
- Use named business definitions in model metadata.
Verification to include
- Delay a payment and keep contracted recurring value unchanged.
- Mix currencies and reject an unsupported combined total.
Deliverables
- Metric definitions and contrasting examples
Rollout and recovery
Publish separate metric names; retire ambiguous aliases after consumer review.
Value of the work
For the engineer: Practice analytical modeling and explainable transformation contracts.
For the team: Review trustworthy reporting definitions and the cost of correcting historical reports.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.