Skip to content

11.2 Inputs for Billing

Sprint: Sprint 11 - Billing
Feature ID: 11.2
Subtasks: 11.2.1

Objective

Deliver "Inputs for Billing" within Sprint 11 - Billing.

Dependencies

Aggregated from the subtasks below (prerequisite task IDs and enablers):

  • 11.1.2
  • 9.3.2
  • 10.4.3
  • 7.4.2

Subtasks

11.2.1 Maintain billing inputs from events

  • ID: 11.2.1
  • Title: Consume subscription and usage events into billing read models
  • Description: Idempotent consumers of subscription.activated.v1 / subscription.suspended.v1 / subscription.terminated.v1 (active subscriber set and bill cycle) and usage.aggregated.v1 (period overage) and tariff.price-changed.v1 (current pricing), maintaining local read models so the bill-run needs no synchronous cross-service calls.
  • Business Purpose: Loose-coupled, replayable billing inputs (FR-21, FR-22, NFR-11).
  • Inputs: event-catalog, FR-21, FR-22.
  • Outputs: Event consumers + billing read models.
  • Acceptance Criteria:
  • Active subscribers, their tariff/addons, and aggregated overage are available locally for a period without calling other services; consumers are idempotent.
  • Dependencies: 11.1.2, 9.3.2, 10.4.3, 7.4.2
  • Complexity: L

Acceptance Criteria

Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.

Deliverables

  • Event consumers + billing read models.

Definition of Done

  • All subtasks (11.2.1) completed and their acceptance criteria verified.
  • All listed dependencies satisfied.
  • Build and tests green per the global conventions in ../README.md (Section 3).