Overview
This guide describes how to configure and use Subscription History, Version Control, and Audit Tracking within the LISA Subscription Cockpit. These features allow organizations to maintain a controlled, auditable, and transparent record of subscription plan changes throughout their lifecycle, including publication events, pricing changes, cancellations, and system-driven updates.
Business Value
Subscription History and Version Control provide strong governance and operational transparency across the subscription lifecycle. By enabling these features, organizations gain a reliable audit trail of all subscription changes, reducing risk during billing disputes, compliance reviews, and customer escalations. Version comparison improves operational efficiency by allowing users to quickly identify what changed, when, and why, without relying on manual investigation. Automated cleanup ensures long-term system performance and data hygiene, while audit tracking linked to sales orders and CoPilot interactions strengthens accountability across sales and operations teams.
Subscription History and Version Control Configuration
Configuration is performed from the Subscription Parameters page. A dedicated section named Subscription History and Version Control contains all relevant settings.
Enable History and Version Control controls whether the system creates historical versions of subscription plans. When enabled, the system captures snapshots of subscription plans whenever qualifying events occur. When disabled, no versions or history records are generated.
Version Control Cleanup (in days) defines how long subscription plan versions are retained. A positive integer instructs the system to delete versions older than the specified number of days. A value of zero disables cleanup entirely.
History Cleanup (in days) defines how long subscription history records are retained. A positive integer deletes history records older than the specified number of days. A value of zero means no cleanup is performed.
Subscription Plan Versioning Behavior
When Version Control is enabled and a subscription plan is published for the first time, the system creates an initial version representing the exact state of the plan at publish time. This version is stored separately from the live plan and assigned a version identifier starting at one for each subscription plan.
On subsequent publishes, the system evaluates whether any header or line-level fields have changed. If no changes are detected, no new version is created. If changes exist, a new version is generated with the next sequential version identifier, capturing the full snapshot of the plan at that moment.
In addition to manual publishes, the system automatically creates new versions when subscriptions are cancelled, cancelled with reversal, cancelled due to future cancellation, cancelled due to expired contract terms, cancelled via credit note, or updated through price indexing.
Version Comparison
Each subscription plan version can be compared with another version of the same plan. A comparison selector labeled Compare version with is available on the subscription plan version page. By default, the system selects the immediately preceding version when available.
The comparison highlights the total number of differences between the current version and the selected version. Differences include modified header fields, modified line fields, newly created lines, removed lines, and lines that were cancelled or made inactive. The visual representation of differences is flexible, but all changes are clearly identifiable.
Subscription History Events
Subscription History records lifecycle events associated with subscriptions and makes them accessible directly from the LISA Subscription Cockpit. Recorded events include first publication, repeated publication, cancellation, unpublishing, price changes, billed consumption units, and upcoming cancellations.
These history entries provide users with a chronological view of how a subscription evolved over time, aligned with the same configuration parameters that control version control behavior.
Subscription Audit Tracking for Contract Copilot Agent
Audit Tracking provides traceability between subscriptions, sales orders, and automated copilot agent activity. From the subscription plan header in the cockpit, users can access a list showing sales orders that led to the creation or modification of the subscription.
At line level, the system displays entries from the CoPilot Agent Task Log, including received emails and subsequent interactions that resulted in subscription creation or changes. If a subscription was created or modified without involvement from the Sales Order CoPilot Agent, no line-level audit entries are shown.
Automated Cleanup Jobs
Two scheduled cleanup processes maintain data hygiene and system performance. Subscription Plan Version Cleanup removes version records and their related lines once they exceed the configured retention period. Subscription History Cleanup removes subscription history records older than the configured number of days.
Both cleanup jobs respect a zero-day configuration as a no-cleanup setting and run without impacting active or recent subscription data.
Operational Notes
Enabling Version Control does not retroactively create versions for previously published subscriptions. Versions are only created from the point at which the feature is enabled. Disabling Version Control stops the creation of new versions but does not remove existing ones. Cleanup behavior is always governed by the configured retention values.