Renewals and amendments

Renewals

When a contract approaches the end of its term, Pinion’s RenewalService creates a renewal opportunity from the contracted subscriptions. Every carried-forward line is re-priced on the renewal effective date — the customer’s active contracted price and discount schedule are applied (falling back to the subscription’s verbatim price only when neither matches), not the snapshot from the original deal. Re-pricing is always on; there is no org-wide opt-out.

A renewal is saved the way new business is saved

Pinion builds the renewal as a configuration — the same saved configuration a rep would build in the configurator — and adds its products to the renewal opportunity through Save & Sync. Two things follow from that:

• Product rules, pricing rules and approvals apply to renewals. A Save-event validation rule that would block the configuration blocks the renewal; a locked pricing rule re-prices the renewal line the way it would re-price a new line; an approval rule the renewal trips holds the renewal for approval. Nothing carries forward around the rules you have authored.
• The renewal opportunity always carries a saved configuration. Open the configurator on the renewal and it reopens exactly what was renewed; the Products tab and the Configuration Options tab reconcile to the same total.

When a rule rejects the configuration, or an approval is required, the renewal opportunity is still created — with a Draft configuration and no products. The reason is written to the opportunity’s Renewal Change Notes. Open the configurator, resolve the block (submit for approval, fix what the rule rejected), then Save & Sync.

Automatic renewals that need attention

The auto-renewal schedule, the renewal created when a contract closes, and mass renewal all run without a person watching. When one of those renewals is created but its products are withheld — an approval is required, or a product rule rejected the configuration — Pinion checks Renewal Review Required on the opportunity and writes the reason to Renewal Review Reason. Those renewals surface with a Needs review badge on the renewal forecast, the account overview’s in-flight activity, and the account’s Renewals tab, so they do not sit silent with an empty opportunity. Uncheck the flag once the renewal has been handled.

A renewal a person creates with the Renew button is not flagged: the Draft configuration and its notes are already in front of them.

Non-subscription options on a subscription bundle

A subscription bundle can carry options that are not subscriptions — a laptop and a monitor under a workspace subscription, an onboarding kit under a platform licence. Those options become Assets when the deal closes, and the bundle option’s Non-Subscription Renewal Behavior decides what happens to each of them when the subscription renews:

• Replay — the option is added to the renewal at the same quantity and at the price the customer paid, then re-priced the way every option of the bundle is (the bundle’s Renewal Pricing Method, the account’s contracted price applied once).
• Prompt — as Replay, and the renewal line is flagged Review Required so a rep confirms the item should re-bill. An automatic renewal that replays a Prompt option is also flagged Renewal Review Required.
• Drop (the default) — the option is left off the renewal.

One exception to Drop: an option marked Required on the bundle is always carried, whatever its renewal behavior says. A bundle cannot be saved without its required options, so leaving one off would leave the renewal with no products at all. Instead the option is carried like a Prompt option — its line is flagged Review Required, the Renewal Change Notes name it, and an automatic renewal is flagged Renewal Review Required — so a person decides whether the hardware re-bills. If a required option should not renew, remove it from the renewal in the configurator; if it should never be carried, it should not be marked Required.

The carried option keeps its contracted economics. A customer who bought the monitor at a contracted 20% off renews it at that same 20% off list, not at 20% off the price they already paid.

The renewal term is the contract’s term

A renewal spans the renewed contract’s Contract Term, applied from the renewal’s start. A 12-month contract renews for 12 months and a 36-month contract renews for 36; change the contract’s term before renewing and the renewal spans the new term, with every quantity derived at that term — a subscription bundle’s quantity is its bundle quantity times the renewal term, exactly as a new deal of that length would be quoted.

Two details are worth knowing because month-end contracts make them visible:

• The renewal begins the day after coverage ends. Under the default Last Covered Day convention, a term ending 31 August renews starting 1 September. There is no gap and no day of double coverage. Under the Anniversary convention the stored end date is already the roll-off day, so the renewal starts on it.
• A partial month does not round up to a whole one. If a subscription’s stored dates span twelve months and a few extra days — which happens with records imported from another system, or terms that were shortened by an amendment — the renewal carries the twelve whole months the term covers. The customer is never renewed for a month they did not buy.

Because the renewal’s date window is also what drives its term-scaled quantity, the renewal’s Amount, ACV and quote all follow from these dates. If a renewal’s length looks wrong, check the renewed contract’s Contract Term and the source subscription’s End Date first — the term comes from the former, the start from the latter.

Amendments

When a customer modifies an active contract (adds licenses, removes seats, swaps tiers), Pinion’s AmendmentService creates an amendment opportunity from the contract’s subscriptions. Carried-forward lines are re-priced against the customer’s active contracted price and discount schedule as of the amendment’s effective date (falling back to the subscription’s verbatim price only when neither matches). Re-pricing is always on; there is no org-wide opt-out.

A mid-term price change is prorated for the remaining contract term from the effective date, using the product’s Proration Type — the same granularity floor the segment-quantity path uses, so quoting and amendments prorate consistently.

An amendment’s Amount is the DELTA, not the full contract value

This is the single most important thing to know when you report on amendments.

An amendment opportunity’s Amount is the incremental value of the change — what the amendment adds to (or gives back from) the customer’s existing commitment. It is not the post-amendment contract value.

The reason is that the original revenue was already captured and recognised on the originating opportunity. If the amendment also totalled the full priced products, that revenue would be counted twice, and pipeline, forecast and quota would all inflate.

So on an amendment opportunity:

Two consequences worth setting expectations on:

• A freshly created amendment shows an Amount of $0 until the rep changes something. That is correct — nothing has changed yet, so nothing new has been sold. It is not an empty or broken amendment; the lines are all there.
• Untouched carried lines show a price of $0 on the amendment — bundles included, whatever their pricing model. The line is still present, and the customer’s real contracted price is still tracked on it (Pinion keeps it on the line’s New Sales Price, which is what writes back to the subscription when the amendment closes). Only the booked value is zero: an untouched Roll-Up or Standard bundle parent books $0 on both its unit price and its bundle price, exactly like an untouched Itemized child. Untouched lines also carry no change type — the Change Type field is set only on a line the amendment actually moved (Modify), added (Add) or removed (Remove), so closing the amendment leaves an untouched subscription exactly as it was: no new change date, no amendment history entry. If you would rather those lines not appear at all, see PrePopulateAmendmentLines__c in Lifecycle defaults — though leaving it on is recommended, because the pre-loaded lines are what let a rep amend a bundle without rebuilding it.
• A removed line reads $0 × 0. Its New Sales Price and New Quantity are both zero — the customer no longer holds any units of it — while the line keeps the contracted quantity it is removing, so the diff shows what went away.

Whether a decrease gives money back is controlled per product by Amendment Credit Behavior. The default is No Credit — a decrease books $0 rather than a negative amount. Set it to Allow Credit on products where a downgrade or removal should reduce the amendment’s Amount. A bundle’s options follow the bundle parent’s setting, with one exception: a discount option is already a credit, so its changes always book signed whatever the setting.

A discount a rep applies to a carried bundle option on an amendment (the option’s Additional Discount) nets the option’s price exactly as it does on new business: the discounted price becomes the option’s New Sales Price, the amendment books the decrease under the credit rules above, and the discount is recorded on the line.

Reporting on the full post-amendment value instead. If you need the whole configured value rather than the delta, report on the amendment’s line items using New Sales Price × New Quantity, or on the contract’s subscriptions after the amendment closes. Customer-facing documents are a separate question: what a quote shows for an unchanged line is a template decision, and the quote template builder lets you suppress unchanged lines, badge them “no change”, or show the contracted value as a reference column.

This applies to multi-dimensional (MDQ) segmented products too. Each segment line books only what changed in that segment — an untouched segment books $0 — and carries its contracted per-segment price in New Sales Price. Opening a segment’s Price Waterfall on an amendment shows that contracted price as the segment’s unit, with the amendment’s impact for the segment listed beneath the segment total.

Multi-instance bundles across the lifecycle

Bundles configured as multiple instances (the same bundle fanned into per-site / per-region copies, each with its own price, quantity, and dates) carry forward through both renewals and amendments — each instance renews / amends independently, keeping its own InstanceName__c, price, and child quantities. Multi-instance authoring is a Plus-tier feature; see the dedicated Multi-Instance Bundles guide.

Precedence

Re-pricing precedence (most → least specific): active contracted price → discount schedule → subscription verbatim price. On a renewal the product’s Renewal Pricing Method (Same / Uplift / List) is applied first, and a bundle’s children take their parent bundle’s method — an Uplift bundle uplifts each of its options, a bundle discount included, so an itemized bundle’s children still add up to its total. Custom logic (Apex extensions, flows) does not run inside the renewal or amendment kernel.

Related

• Contract Lifecycle Actions — the Amend / Renew buttons that start these flows, and the layout assignment they need.
• MDQ — Multi-Dimensional Quoting — re-pricing on the effective date resets the uplift schedule.
• Multi-Instance Bundles guide — the Plus-tier authoring feature.
• Troubleshooting — chasing a surprising re-priced total.