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.

Where a renewal price starts: what the customer paid

The subscription’s verbatim price is what the customer paid for the line: its closed unit price, including a price the rep typed and any discount on the line or segment. Every renewal method starts from it. On a multi-dimensional (MDQ) product that holds for each dimension’s Renewal Behavior:

• Carry Forward continues from what the final segment paid, one uplift step per renewal segment.
• Same keeps each segment at what it paid.
• Uplift adds one uplift step to what each segment paid.

A renewal never restarts from the uplift ramp the segment was originally quoted on. That ramp is used only if a subscription has no recorded price at all. The discount is already inside the paid price, so the renewal does not apply it a second time.

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.

Bundles prorate exactly the same way. Adding an option to a bundle you keep, changing an option, removing an option, and changing a Roll-Up or Standard bundle’s parent all book only the share of the remaining term, counted from the effective date in each line’s own proration type. Component and Accessory options prorate alike.

Only subscription products prorate. A product whose Subscription box is unchecked is a one-time purchase, and it books its full price on every amendment, whether it is sold on its own or inside a bundle, and whether it is added, changed or removed. There is no separate “do not prorate” setting: a product that should not prorate is simply not marked as a subscription.

A recurring discount product must be a subscription too. The same rule applies to a discount product, including a discount option inside a bundle: it prorates on a mid-term amendment only when its own Subscription box is checked. If a recurring discount product is left unchecked, an amendment books its full discount while the charges it discounts are prorated, so the credit is larger than the share of the term that remains. Check Subscription on every discount product that recurs with the products it discounts.

The amendment effective date

Every amendment has one effective date, stored on the amendment opportunity’s Amendment Effective Date field. Every line on the amendment prices from it: added, changed and removed lines alike, standalone products and bundle options alike. There is no per-line date, and the server ignores any line-level date a client sends.

• Default. Pinion sets it to the day the amendment is created.
• Who changes it. The rep, in the Configurator’s amendment banner. The new date is saved with Save & sync (or Save amendment after a Quick save), in the same save as the line items it prices. Quick save does not save the date, but it evaluates approval rules at it, so an approval threshold is judged on the amount the amendment books at the rep’s date. Syncing a saved configuration from Product Display keeps the amendment’s current date.
• Backdating. Allowed, within the amended contract’s term: on or after the contract’s Start Date and on or before its End Date. A date outside that range is refused with a message naming the term. It is never adjusted to fit.
• Direct edits are refused. On an existing amendment the date can only be changed in the Configurator. Changing it anywhere else (the record page, a list view, the API, a data load or a Flow) is refused with the message Change the amendment effective date in the configurator so the line items re-price. An update that changes the date together with other fields is refused as a whole. Other edits to an amendment opportunity, such as Stage, Close Date or Description, save as usual, and the field on a non-amendment opportunity is not affected.
• Why. Every line on the amendment prices from this date, and only a Configurator save re-prices the lines when it moves. An edit made on the record would leave the opportunity showing one date while its line items were priced at another. Pinion enforces the rule itself, on the opportunity, rather than on a page. It holds on the Pinion Opportunity Record Page that ships with the package, on your org’s own page layouts and Lightning pages, and on edits that use no page at all (the API, data loads, Flows). You do not need to make the field read-only on a layout.
• Your own validation rules still apply. Validation rules your org adds to Amendment Effective Date still run when the Configurator saves the date, and a rule that fails stops that save.
• A split part that bills nothing has no line. An MDQ segment the date falls inside is split into the part before the date and the part after it. Under Quarterly proration, a part shorter than one completed month bills 0, so it gets no line and the segment carries on from (or up to) the date. The split uses the proration type it resolves for the line, which today is the org Default Proration Type rather than the product’s own. See Proration.
• Close-won. Each amendment line carries the date as its effective date, so a removed subscription ends, and a changed one takes its new terms, on the same day its amount is measured from.

Reps who can edit amendments need edit access to Amendment Effective Date, because the Configurator saves it with the rep’s own permissions. The Pinion User, Pinion Account Manager, Pinion RevOps Manager and Pinion Administrator permission sets grant it.

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 removal under Allow Credit credits only the part of the subscription the customer has not used yet, counted from the amendment’s effective date (see The amendment effective date). A line removed halfway through a three-year term credits the remaining eighteen months, not all three years. A multi-year line with a price per year credits each year by where it sits on that date: a year that has not started credits in full, the year in progress credits its remaining share, and a year already over credits nothing. The remaining share is counted in the product’s proration type (the same way the line was billed), and the configurator’s Net impact banner shows the same credit the saved amendment books. Removing an option from a bundle you keep follows the same rule: the option credits only its unused share (on a multi-year bundle, each year by where it sits), and a one-time option credits its full value.

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.

When you total a contract’s subscriptions yourself, count each bundle once. An Itemized bundle’s value is its options: the parent subscription’s Unit Price is $0, on new business and after an amendment alike, because the options carry the dollars. For Standard and Roll-Up bundles the parent carries the value and its options are $0. The subscription’s Bundle Pricing Model tells you which is which. Assets (one-time purchases) are worth Price × Quantity, because Price is the price of one unit. The account overview’s Total Contract Value, its ARR and MRR, the renewal forecast and the Contracts tab’s totals all apply both rules for you. The Contracts tab lists the Assets that contract’s own deals sold, so two contracts on one account each show only their own.

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.

An option added to a multi-year (segmented) bundle on an amendment also books segment by segment. A subscription option is added to every segment, priced with that segment’s uplift and prorated over the segment’s own window from the amendment effective date: a segment not yet started books its whole value, the one in progress its remaining share, one already over $0. A one-time option (its product’s Subscription box unchecked, and not a discount option) is charged once:

• in the segment whose window holds the amendment effective date (the first segment not yet over on that date);
• at its full catalog value, not prorated and without the segment’s uplift.

On an Itemized bundle the one-time option’s own line carries that charge. On a Roll-Up bundle the option line saves at $0 and its value is added once to that segment’s parent line, never folded into the parent’s recurring per-unit price. On a Standard bundle the parent’s own price is the bundle price, so a one-time option adds nothing to it.

A Percent segment discount reduces the one-time charge, and on Roll-Up so does a Percent bundle-header discount. An Amount segment discount doesn’t (on Itemized it never applies to option lines; on Roll-Up the parent’s recurring per-unit price has already taken it), and on Roll-Up neither does an Amount header discount. On Itemized, the bundle-header discount reaches the one-time option’s line the same way it reaches every other option line, as on new business. Closing the amendment won creates one Asset for the one-time option.

Product Display lists the bundle’s options from its first segment. An option that only a later segment holds, such as a one-time option charged in the segment in progress, is listed once, labelled with the segment that carries it.

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.