What makes an amendment
Only an order reprices a contract, so only an Order Execution amendment has
lines and a Payable Impact. The others record that something happened to the
contract, and when.
For now the sync sends the amendments an order made and a cancellation. An
Import amendment stays in Veles: a contract that was imported, or entered in
Veles and activated, has no amendment in Salesforce until an order amends it,
and its Amendment Numbers in Salesforce have a gap wherever an import happened.
A renewal order creates a new contract rather than amending the old one, so its
Order Execution amendment is the new contract’s Initial Contract.
The money on an amendment
Payable Impact is how much the amendment changes what the customer pays, from its Effective On date to the end of each line’s window: the sum of its lines’ Payable Impact, positive when the customer pays more. On the Initial Contract every line is new, so the Payable Impact is each line’s value over its whole window. On a later amendment it is the change alone: taking a line from 10 to 20 seats at $1,200 a seat per year, halfway through a one-year term, reads about $6,000. Report expansion and contraction on the Contract Amendment Line, which carries the same Payable Impact per line along with its Impact Type, Billing Type and product.The amendment page
An amendment’s record page shows what it did to each contract line, phase by phase. Where a quantity, unit price or amount changed, the old value is struck through above the new one, and each line shows its Payable Impact. The page opens on the lines that changed; All lines adds the ones the amendment kept. Beside the lines, the summary gives the amendment’s Payable Impact and the contract’s TCV before and after it (Old TCV and New TCV): an order amendment has a line for every contract line, so these are the sums of its lines’ Prior Contribution and Contribution. Below the figures, the summary links the contract’s Account, the contract and the order. The Initial Contract shows its lines and TCV as signed. A cancellation has no lines.Fields at a glance
Field details
Amendment Name — The amendment’s name in Veles (e.g. Initial Contract,
Amendment 2, Contract Cancelled).
Veles External ID — The Veles contract amendment ID. All sync writes
upsert on this field; never edit.
Contract — The Veles contract this amendment changed. Master-detail: a
contract’s amendments, by Amendment Number, are its change history.
Amendment Number — The amendment’s sequence number within its contract:
the contract’s first amendment is 1, its next 2, and so on.
Amendment Type — What made the amendment. Empty for an amendment recorded
through the Veles API without a type. Unrestricted so new Veles amendment
types never break the sync.Values:
Order Execution (an executed order created or amended the
contract), Import (Veles imported the contract or a change to it, or a
contract entered in Veles was activated), Cancellation (the contract was
cancelled).Effective On — When the amendment takes effect. For one an order made,
the order’s Effective On: on an amendment order, the amendment date inside the
contract’s window. For a cancellation, the effective date picked when the
contract was cancelled. For an import or activation, the day Veles recorded
it. Each amendment takes effect on or after the one before it.
Order — The Veles order whose execution made this amendment: the order
that created the contract, or one that amended it. Empty for an import,
activation or cancellation, and until the order is in Salesforce: the sync
fills it in once the order lands. Gives the
Order a Contract Amendments related
list.
Payable Impact — The sum of this amendment’s lines’ Payable Impact: how
much the amendment changes what the customer pays from its Effective On date
to the end of each line’s window. Positive when the customer pays more. Zero
on an amendment with no lines: an import, activation or cancellation.
Description — A short account of what the amendment did, as Veles wrote
it (e.g. Amendment 2 created from order).