Order Phase - Veles Docs

A Veles Order Phase is one time-segmented window within an Order — a ramp year, a pilot period, any stretch of months with its own pricing. Phases are ordered by sequence and each carries its own precomputed totals. See Order Phases for how phases behave in Veles. Phases are master-detail children of their order. Their totals are synced rather than rolled up in Salesforce, because Order Lines relate to phases via lookup and native rollup summaries require master-detail — so the phase totals arrive precomputed by the Veles pricing engine instead. Dynamic user-defined inputs carried into the order are exposed as child Order Phase Attribute Values, listed under Attribute Values on the phase’s Related tab. Unit of Measure inputs use the uom namespace and contain normalized values. Order phases carry no discount pair and no uplift. Those are quote-side concepts: by the time an order exists the negotiation is settled, and an order line records only its agreed price.

Fields at a glance

Field	API Name	Type
Phase Name	`Name`	Text (standard name field, e.g. “Phase 1”)
Veles External ID	`Veles__External_Id__c`	Text(255), unique, external ID
Order	`Veles__Order__c`	Master-Detail(Veles Order)
Sequence	`Veles__Sequence__c`	Number(3, 0)
Months	`Veles__Months__c`	Number(4, 0)
Start Date	`Veles__Start_Date__c`	Date
End Date	`Veles__End_Date__c`	Date
Phase Contract Value	`Veles__Phase_Contract_Value__c`	Currency(16, 2)
ARR	`Veles__ARR__c`	Currency(16, 2)
Recurring Revenue Prorated	`Veles__Recurring_Revenue_Prorated__c`	Currency(16, 2)
One-Time Revenue	`Veles__One_Time_Revenue__c`	Currency(16, 2)
Synced At	`Veles__Synced_At__c`	DateTime

Field details

Text (standard name field)

Phase Name — “Phase” and the phase’s sequence, e.g. Phase 1.

Text(255), unique, external ID

Veles External ID — The Veles order phase ID. All sync writes upsert on this field; never edit.

Master-Detail(Veles Order)

Order — The Veles order this phase belongs to. Master-detail: phases are owned by their order and are deleted with it.

Number(3, 0)

Sequence — The phase’s 1-based order within the order. Phase 1 is the first time window. Also denormalized onto each order line (Phase Sequence) so line-level rollup filters work without joins.

Number(4, 0)

Months — How many months this phase spans, derived from its effective window. Phases can be any length, not just whole years.

Date

Start Date — The first day of the phase’s effective period.

Date

End Date — The last day of the phase’s effective period.

Currency(16, 2)

Phase Contract Value — Recurring Revenue Prorated + One-Time Revenue: everything the customer pays for this phase’s actual window. Phase Contract Values sum to the order’s TCV. Precomputed by Veles, since line-to-phase is a lookup and Salesforce cannot roll this up natively.

Currency(16, 2)

ARR — Annual Recurring Revenue for this phase: the sum of its recurring lines, annualized (run-rate lens, proration-independent). Compare with Recurring Revenue Prorated to see the proration effect; on a ramp, per-phase ARR is the “Year N run-rate” story.

Currency(16, 2)

Recurring Revenue Prorated — The sum of this phase’s recurring lines, prorated to the phase’s actual window. Equals ARR when the phase covers its full nominal term. Phase values sum to the order’s Recurring TCV.

Currency(16, 2)

One-Time Revenue — The sum of this phase’s one-time fees. Phase values sum to the order’s One-Time TCV. Recurring Revenue Prorated + One-Time Revenue = the Phase Contract Value.

DateTime

Synced At — When the Veles sync last wrote this record. The order mirror updates at each step of the order’s lifecycle: created, edited in draft, finalized, sent for signature, signed, executed and cancelled.