Lifecycle Defaults

When Pinion creates a renewal or amendment opportunity, or closes a deal to a contract, it stamps a set of standard values you configure once on Configurator Settings. These make the generated opps land in the right stage, record type, and opportunity type for your sales process.

New business & close

Field	What it sets
`NewBusinessType__c`	The Opportunity Type value stamped on new-business deals.
`ClosedWonStage__c`	The Opportunity stage Pinion treats as Closed-Won for lifecycle logic (contract + subscription creation fires here).

Opportunity Type and contract creation

When an Opportunity moves to your Closed-Won stage, Pinion reads its Type to decide what to do. The three Type settings on Configurator Settings are the values Pinion recognizes:

Opportunity Type equals	What Pinion does at Closed Won
`NewBusinessType__c` (default `New Business`)	Creates a Contract, one Subscription per recurring line, and one Asset per one-time line.
`RenewalType__c` (default `Renewal`)	The same, and expires the contract the renewal replaces.
`AmendmentType__c` (default `Amendment`), with an amended contract	Applies the amendment’s changes to the existing contract.

For an Opportunity whose lines were built in the Pinion configurator (it has an Accepted configuration option behind its lines):

Type left blank. Pinion treats the deal as new business and creates the Contract, Subscriptions, and Assets. Reps don’t have to pick a Type for a Pinion deal to contract.
Type set to a value none of the three settings name. Pinion blocks the Closed-Won stage change and shows an error naming the Type value and the Configurator Settings fields. Nothing is saved: the Opportunity stays in its previous stage, and no Contract, Subscription, or Asset is created. To resolve it, an admin sets NewBusinessType__c (or RenewalType__c / AmendmentType__c) to that value, or the rep clears the Type and closes the deal again.

An Opportunity with no Accepted configuration option (for example, a deal your team tracks outside Pinion) closes normally, whatever its Type. Pinion creates nothing for it and shows no error.

Closing won is blocked, not silently skipped, so a Pinion deal can’t be marked won without also getting the contract its renewals and amendments depend on. Trigger Bypass turns this check off along with the rest of Pinion’s Opportunity automation.

Renewals

Field	What it sets
`RenewalStage__c`	Stage for a generated renewal opportunity.
`RenewalType__c`	Opportunity Type for renewals.
`RenewalRecordType__c`	Record type (developer name) for renewal opps.
`DefaultRenewalUpliftPercent__c`	Default percentage uplift applied when a renewal re-prices.
`RenewalContactRolesToCopy__c`	Comma-separated contact roles copied from the source deal onto the renewal.

Amendments

Field	What it sets
`AmendmentStage__c`	Stage for a generated amendment opportunity.
`AmendmentType__c`	Opportunity Type for amendments.
`AmendmentRecordType__c`	Record type for amendment opps.
`PrePopulateAmendmentLines__c`	(default on) Whether an amendment opens pre-loaded with the existing subscription lines.
`AmendmentCreditBehavior__c`	`No Credit` or `Allow Credit` — whether an amendment may generate a credit line.

Proration & contract dates

Field	What it sets
`DefaultProrationType__c`	The org-wide fallback proration method (Daily / Weekly / Monthly / Quarterly) used when a product leaves `ProrationType__c` blank.
`ContractEndDateConvention__c`	(default `Last Covered Day`) Whether the stored contract end date is the last covered day or the roll-off day. See below — this changes the stored date, not the length of the term.

What the two contract-end conventions mean

A contract window is always the start date plus the term in whole months (ContractDurationInMonths__c, labelled Contract Term (Months)). The contract end date is calculated from them on every Opportunity and Quote save and cannot be edited on its own, so pricing, multi-year segments, close-won contracts and renewals all read the same window. A configuration with subscription products cannot be saved until the start date and term are set.

The setting controls only which date gets stored in the contract end field for a given term length. Both describe the same coverage.

For a 36-month contract starting 29 May 2025:

Convention	Stored contract end	Meaning
`Last Covered Day` (default)	`2028-05-28`	The last day the customer is covered.
`Anniversary`	`2028-05-29`	The roll-off day — the first day the customer is no longer covered.

Field Propagation — which pricing, quantity, date, and configuration fields carry from the line items onto the Contract, Subscription, and Asset when this close-won fires.
Renewals & Amendments — how re-pricing works on the lines these settings stamp.
Proration — the per-type proration behavior DefaultProrationType__c feeds.
Scheduled Jobs — the auto-renewal / contract-expiration jobs that create these opps.