Why it is versioned
Commercial relationships change mid-term, and the changes don’t all apply to the same activity. An amendment changes the terms for the activity it covers; an invoice already issued keeps the terms it was issued under. Treating every action as if it happened under the latest agreement would re-bill the past; treating the agreement as fixed would block the change. Each subscription in Alguna therefore carries versions with effective dates. Usage is rated against the version in force when it occurred. Entitlements update on the effective date of the version that grants them. Revenue schedules derive from the agreement and its amendments. A receivable stays attached to the terms and approved adjustments that apply to it, even while a later amendment waits for approval.One change, six teams
A customer on a $120k annual usage commitment adds a product and raises the commitment midway through the term. Usage keeps accruing, and an earlier invoice is still unpaid. One commercial decision creates six connected pieces of work:
These activities overlap in time. The revenue object connects them without forcing every action onto the same version of the agreement: effective dates, calculation logic, and approvals decide which terms apply to each.