A mid-term seat add and a shorter module term on a co-terminated contract

Co-termination and the requested 24-month term are in direct conflict. The existing contract ends after 36 months from March 1. A module added effective September 1 with an aligned end date runs 30 months, not 24. Something has to give, and it should be an explicit decision rather than a side effect of configuration.

Options:

• Co-terminate at 30 months (recommended). Satisfies the single renewal date and single invoice request, and 30 months clears the 12-month minimum. The customer pays for six more months than asked, so the commercial team should be prepared with a price concession or an explicit justification.
• Start the module later, so a 24-month term reaches the same end date. This works only if the customer can defer the start; a start date in March of year two gives 24 months aligned to the existing end. This is often the cleanest answer and is frequently overlooked.
• Separate contract with its own 24-month term. Meets the literal ask but breaks the single-invoice and single-renewal requirements and creates a second renewal event to manage.

Recommendation: propose the deferred start first, fall back to 30-month co-termination with a concession.

Two mechanics must not be conflated.

Proration covers the partial first period. Forty seats from September 1 to the next anniversary at the year-one rate of $90: six monthly periods, billed at the amended quantity for the days in each billing period. Under daily proration, a mid-month start means the first invoice carries only the remaining days of September. The clean implementation is to set the added line's start date to September 1 and let the billing schedule generate from that date - not to add forty to the existing line's quantity, which would age the new quantity back to March 1. That is precisely the error finance already saw.

Uplift is a separate event and applies to the total quantity in force at the anniversary. At the next March 1, all 160 seats move to $93.60. The uplift must be driven by the contract or subscription term anniversary, not by the amendment date, or the added seats get their own anniversary and the price list fragments.

Also confirm how the six-month stub is displayed: one prorated line or a separate stub period. Either is acceptable if the customer can reconcile it against the quoted amount.

• Subscription line start and end date. Missing or defaulted to contract start produces six months of overbilling, as already happened.
• Quantity and price book entry. Missing a price book entry for the added quantity in the contract currency causes a zero or failed invoice line, and the failure surfaces at invoice generation, not at quote.
• Co-terminus indicator on the line. If absent, renewal generation will split the renewal into separate events and the single-renewal promise breaks silently until renewal season.
• Billing frequency on the new line. If it inherits nothing, the line may not produce a schedule at all.
• Amendment effective date as distinct from line start date. Without both, you cannot separate when the change was agreed from when it is billed, which is what an auditor will ask.

The pattern: every one of these failures appears downstream, in billing or renewal, weeks after the quote looked correct. Validation belongs on the amendment.