At a glance
Generates, signs, stores and renews customer contracts.
Key data
Receives from
- Order management
- Template management
Sends to
- Document management
- Billing (fees)
- Notifications
How it works
The main steps, end to end.
- 1Generate the contract from the order
- 2Present for signature
- 3Seal and store the signed version
- 4Track terms and renewal dates
- 5Amend or terminate when the service changes
Core Capabilities
What Contract Management provides across the contract lifecycle
Contract Generation
- Generates contract document based on order details at fulfilment time
- Applies correct legal template per product type, channel and jurisdiction
- Populates contract with subscriber details, plan, price and terms
- Triggered by Order Fulfillment (COM) after order confirmation
Contract Signing
- Presents contract to subscriber for digital signature
- Supports electronic signature capture via self-care and assisted channels
- Records signature timestamp and agent identity for audit
- Unsigned contracts block fulfilment from proceeding
Contract Activation
- Activates contract after successful signing
- Links active contract to subscription and billing account
- Sets contract start date and term duration
- Triggers service provisioning once contract is active
Contract Printing
- Generates printable PDF contract via document generation service
- Delivers contract to subscriber via notification channel
- Stores contract PDF in document management for future retrieval
- Supports reprint on subscriber request
Contract Termination
- Terminates contract on service disconnection or port-out
- Records termination date, reason and agent identity
- Triggers downstream billing finalisation on termination
- Supports early termination penalty calculation where applicable
Contract Update
- Updates contract terms on plan change or renewal
- Re-generates contract document when material terms change
- Links updated contract version to existing subscription
- Supports contract re-signing when required by updated terms
Storage & Persistence
How and where ContractManagement stores its data
Document Data Store
- Contract documents: terms, subscriber, plan, price
- Signing records: timestamp, agent, digital signature reference
- Contract lifecycle state and version history
- Termination records: date, reason, executing agent
Document File Store
- Generated PDF contract files per subscriber
- Versioned for reprint and reissue
- Retained permanently for compliance
Async Event Bus
- Contract generated event — triggers signing flow
- Contract signed event — triggers service activation
- Contract terminated event — triggers billing finalisation
Design Principles
Key architectural decisions behind Contract Management
Sign-gate on Fulfilment
Service provisioning cannot proceed until the contract is signed. The Order Fulfillment layer checks contract signing status as a prerequisite gate, ensuring no subscriber is activated on a service without having agreed to the terms.
Template-driven Generation
Contract documents are generated from configurable legal templates, not hardcoded content. This allows legal teams to update terms, add product-specific clauses and adapt language without requiring a code change.
Immutable Termination Record
Once terminated, a contract record is never deleted. The termination date, reason and executing agent are stored permanently, providing a complete audit trail for regulatory and dispute-resolution purposes.
Generative AI explains key terms to customers in plain language.
Predict which contracts are unlikely to renew and why.
More in 30 AI & ML use cases and AIOps for BSS.