Contract

Overview

A Contract records an agreement with a client — an SOW, an MSA, an amendment — at any stage from draft, through out for signature, to signed, together with the commercial terms that matter to billing: when the committed term starts, how many months it runs, what happens when it ends, and what leaving early costs. Its whole job is the commitment boundary. Price, cadence and invoices stay with the Subscription, and attaching a contract never moves a subscription's service or invoice dates. The field the entity exists for is the term length, because term length is not billing cadence: an annual commitment paid monthly is a twelve-month term on a monthly subscription. A contract with no term is evergreen, which is the honest shape for an MSA. One contract may cover several subscriptions; a subscription takes its committed term from exactly one, so the boundary always has a single source. When the boundary arrives, the contract's renewal terms decide: an auto-renewing commitment rolls into its next term (the signing date never moves — the term count goes up and the end is re-derived from it), one that ends does not renew past the boundary, and one that renews unless notice is given raises a single item in the renewal approval queue as soon as the notice window opens and blocks the boundary until it is decided. A contract narrows a renewal rather than forcing one.

How it connects

This concept highlighted in context. Click a peer to navigate.

• Belongs to one Client
• Covers one or more Subscriptions, each taking its committed term from exactly one contract
• Consulted by the renewal boundary when a period end reaches the committed end
• Supplies the default early-termination policy a cancellation inherits

Key fields

What you’ll see when creating or editing a Contract.

Example