Billing Relationships

Why This Exists

This document explains how Billing relates to other Algosure domains and external providers.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity prevents billing facts from being duplicated while allowing subscription state to drive access, communication, reporting, and plan recommendations.

Relationship Diagram

flowchart TD
    Organization[Organization]
    Billing[Billing]
    Notification[Notification]
    Analytics[Analytics]
    Intelligence[Intelligence]
    Platform[Platform Access]
    Identity[Identity]
    PaymentProvider[Payment Provider]
    Domains[Operational Domains]

    Organization -->|organization identity and contacts| Billing
    Identity -->|user references for billing access| Billing
    PaymentProvider -->|payment callbacks| Billing
    Billing -->|entitlements and limits| Platform
    Platform -->|usage records| Billing
    Billing -->|billing notification requests| Notification
    Billing -->|subscription and revenue events| Analytics
    Intelligence -->|plan explanation and upgrade recommendation| Billing
    Billing -->|access decisions| Domains

Relationship Catalogue

Domain or system	Relationship	Data ownership rule
Organization	Provides organization identity and business profile reference.	Organization owns identity; Billing owns billing account.
Identity	Provides user references for billing administration permissions.	Identity owns users; Billing owns billing authorization records only where needed.
Platform Access	Consumes entitlements and limits.	Billing owns entitlements; Platform enforces access.
Operational Domains	May check entitlement before feature use.	Operational domains do not own billing state.
Notification	Delivers billing notifications.	Notification owns delivery state; Billing owns billing facts.
Analytics	Reports revenue, subscription, churn, usage, and payment trends.	Analytics owns reporting views; Billing owns facts.
Intelligence	Explains plan differences and recommends upgrades.	Intelligence owns reasoning; Billing owns accepted subscription changes.
Payment Provider	Processes external payment interactions.	Provider supplies callbacks; Billing owns accepted payment state.

Boundary Rule

Billing may affect access through entitlements, but it does not own the product capability definitions or operational records created within those capabilities.