A customer signed a 12-month contract for 100 seats of the platform 6 months ago. They now want to add 25 more seats. The Account Executive opens the existing Order, runs the amendment, adds the 25 seats. The next invoice comes out wrong: prorate amount looks off, the renewal date for the added seats does not align with the original contract, finance has to manually adjust.
The amendment is one of the most common operations in subscription revenue and one of the most frequently misconfigured. Three decisions shape whether amendments produce clean billing or recurring cleanup work.
Decision 1: How to prorate the new line
The customer signed for 100 seats at $50/seat/month for 12 months. 6 months in, they add 25 more seats. What should the customer pay?
Three options:
Option A: Prorate from amendment date through end of original term. The 25 added seats run from amendment date (month 6) to original contract end (month 12). The customer pays 6 months of $50 x 25 = $7,500 plus any partial-month proration for amendment day to next bill cycle.
This is the most common and the most intuitive. The customer's overall contract end date stays the same. The added seats expire when the original contract expires. Renewal handles both together.
Option B: New term starts at amendment date. The 25 added seats get their own 12-month term starting at amendment. Original contract: months 1 to 12. New seats: months 6 to 18. The customer now has two renewal dates.
Two renewal dates is operationally awkward. Most subscription businesses use Option A and only fall back to Option B in specific contractual situations.
Option C: Co-terming with extended original. The original contract extends to match the new seats' term, so all seats expire together at a new end date (e.g., month 18 instead of month 12). The customer effectively re-signs for the full 18-month commitment.
This is used when the customer is willing to commit longer. Often paired with a discount for the extended term.
Each option has different prorate logic. The amendment configuration should specify which option is the default and how to override for specific deals.
Decision 2: How to handle partial-month proration
The amendment happens mid-month. The customer's billing cycle is the 1st of each month. The added seats start on the 15th. The first invoice for the added seats covers the 15th to the end of the month (about half a month).
Standard practice: prorate by day count. Days in partial period / Days in full month, applied to the per-seat monthly rate.
But the math has edge cases:
- February vs December: different day counts. Whether to use actual days or assume 30 days per month is a policy decision.
- Daily vs hourly proration: most subscriptions prorate by day, but some usage-sensitive products want hour-level resolution.
- Free trial periods: if the added seats are in a trial window, proration should not run for the trial duration.
Document the proration policy explicitly. Configure the platform to match. Test with edge case dates (Feb 28 add, Feb 29 in a leap year, end-of-month add) to confirm.
Decision 3: Renewal alignment
When the contract reaches renewal, what gets renewed?
If the amendment used Option A (added seats expire with original), renewal is straightforward: renew the full 125 seats.
If the amendment used Option B (separate term for added seats), the renewal has 2 phases: renew the original 100 seats at month 12, renew the 25 added seats at month 18. The customer experiences two renewal conversations and two invoices.
If the amendment used Option C (co-termed), renewal is at the new aligned end date with the full 125 seats.
The renewal flow has to know which amendment option was used and handle the renewal accordingly. RLM's native Renewal Flow Template supports this; CPQ Classic's Renewal Manager handles it with more manual configuration.
Decision 4: Pricing changes during amendment
The original contract had per-seat price $50. The amendment is happening today, when the current published price is $55. What price applies to the added seats?
Three approaches:
Honor original price. Added seats use the contracted $50, not the current $55. Treats the contract as a price-lock.
Current price. Added seats use $55, the price as of amendment date.
Hybrid. Existing seats keep $50; added seats use $55. Customer's effective per-seat rate becomes a blend.
The choice is a contractual decision (often documented in the original MSA) and a commercial decision. The platform should be configured to match the contractual norm, with override capability for specific deals.
For SaaS subscription businesses, "honor original price" is the most customer-friendly default. "Current price" is operationally easier but is sometimes contractually disallowed.
Decision 5: Quote and Order representation
Amendments can be represented in CPQ and RLM as:
A new amendment Quote. A fresh Quote that references the original. The amendment Quote shows only the changes (the added 25 seats), priced and approved separately.
A revised Order. The original Order gets new lines added. The Order shows the cumulative state (125 seats total).
Both. An amendment Quote becomes a new Order document that references the original.
Each pattern has trade-offs. The amendment Quote is cleaner for the sales motion but harder to reconcile in reporting. The revised Order is operationally simple but loses the discrete amendment event from the audit trail.
Most production implementations use the amendment Quote pattern with the resulting Order showing both original and amendment lines. Reporting can roll up by Order for current state and by Quote for amendment history.
Common amendment mistakes
Five patterns Sapota sees:
- Default prorate option not documented. Each rep handles amendments differently. Some prorate to end of term, some create new terms. Customers see inconsistent treatment.
- Bill cycle misalignment. Added seats get their own Invoice Schedule on a different cycle than the original. Customer gets multiple invoices per month.
- Renewal does not pick up amendments. The renewal cycle renews only the original lines, missing the added seats. Customer's renewal quote is incomplete.
- Pricing policy not configured. Reps manually pick the price for added seats. Inconsistent treatment of comparable customers.
- No audit trail. Amendment changes the Order in place with no record of who changed what. Finance and legal cannot reconstruct the contract history.
What good amendment handling looks like
A Salesforce Revenue Cloud amendment flow that holds up:
- Default prorate option documented and configured (Option A for most B2B SaaS).
- Partial-month proration policy explicit (day count, leap year handling).
- Renewal flow aware of amendment history.
- Pricing policy enforced (honor original by default, override with explicit approval).
- Amendment Quote + revised Order pattern with full audit trail.
- Quarterly review of amendment-driven invoices for anomaly detection.
The amendment is where the subscription model meets operational reality. The platform supports it, but the supporting configuration decides whether amendments are routine or are a source of recurring finance work. Sapota's Salesforce team designs amendment handling as a deliberate workstream during implementation rather than leaving it to default behavior.
Designing subscription amendment flows in Salesforce Revenue Cloud? Sapota's Salesforce team holds the Revenue Cloud Consultant credential and handles amendment and renewal configuration on production engagements. Get in touch ->
See our full platform services for the stack we cover.
