Billing Domain¶
Why This Exists¶
The Billing Domain is responsible for subscription plans, trials, billing accounts, invoices, payments, payment failures, subscription status, plan limits, usage limits, entitlements, renewals, cancellations, and billing notifications.
Algosure is an AI Digital Procurement Company. Customers need clear access to the capabilities they have subscribed to, predictable billing, transparent invoices, governed entitlements, and reliable handling of renewals, cancellations, trials, limits, and payment failures.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Billing owns subscription, billing account, invoice, payment, entitlement, usage limit, renewal, cancellation, and payment failure state.
Business Value¶
Billing converts commercial packaging into operational access. It protects revenue, supports subscription lifecycle management, enables plan-based entitlements, and gives customers confidence that subscription status and invoices are transparent.
Domain Definition¶
The Billing Domain manages:
- Subscription plans.
- Trials.
- Billing accounts.
- Subscriptions.
- Subscription status.
- Invoices.
- Payments.
- Payment failures.
- Plan limits.
- Usage limits.
- Entitlements.
- Renewals.
- Cancellations.
- Billing notifications as Billing-owned facts requested through Notification.
Plan Catalogue¶
| Plan | Purpose |
|---|---|
| Free | Entry-level access for exploration, onboarding, or limited usage. |
| Starter | Basic paid access for small organizations beginning procurement work. |
| Professional | Expanded access for active tendering and structured procurement workflows. |
| Business | Higher-capacity access for teams, collaboration, reporting, and broader capability use. |
| Enterprise | Contracted access for advanced requirements, governance, support, integrations, and negotiated limits. |
Ownership Boundaries¶
| Concept | Owning domain |
|---|---|
| Subscription, billing account, invoice, payment, payment failure, entitlement, usage limit, renewal, cancellation | Billing |
| Customer organization identity and business profile | Organization |
| Billing notification delivery state | Notification |
| Revenue and subscription reporting metrics | Analytics |
| Plan explanations and upgrade recommendations | Intelligence |
| Product capability definitions | Owning product/domain capability areas |
Domain Relationship Overview¶
flowchart TD
Organization[Organization]
Billing[Billing Domain]
Notification[Notification]
Analytics[Analytics]
Intelligence[Intelligence]
Platform[Platform Access]
PaymentProvider[Payment Provider]
Organization -->|OrganizationId and billing contacts| Billing
Billing -->|billing notification requests| Notification
Billing -->|subscription and revenue events| Analytics
Intelligence -->|plan explanation and upgrade recommendation| Billing
Billing -->|entitlements and limits| Platform
PaymentProvider -->|payment status callbacks| Billing
Domain-Driven Design Position¶
Billing is a supporting domain with direct commercial importance. It does not own customer organization identity, platform capability definitions, notification delivery, analytics reporting, or AI reasoning. It owns the accepted subscription state and all billing lifecycle records.
What This Domain Does Not Own¶
Billing does not own tender data, compliance state, bid workspaces, contract delivery, supplier records, learning progress, or notification delivery state. Billing may restrict access through entitlements and limits, but the operational facts remain in their owning domains.