Creating vendor Change Orders and Prime Change Orders

A vendor CO changes a Commitment. A PCO changes the Prime Contract.

Best for: Project managers coordinating cost and revenue · Requires: Access to the affected contracts and changes.

Within a Change Event:

1. Add a vendor Change Order for each affected Commitment.
2. Add line items with cost code, cost type, amount, retention, and subproject as applicable.
3. Add a PCO when the owner-side contract should change.
4. Review the PCO amount and its budget impact.
5. Complete the appropriate approval or e-signature lifecycle.

One Change Event can include multiple vendor COs and a PCO. Their amounts do not have to be identical; margin, allowance, and non-billable cost decisions can make cost differ from owner billing.

For Sage-connected projects included in accounting integrations, PCO creation is blocked while the Budget has no line items. The Sage estimate is the expected source for many customers, but the product gate checks for budget lines rather than a specific estimate link.

If that happens, see A Prime Change Order cannot be created.

When vendor pricing is the starting point, continue with Copying vendor change costs to the Prime Contract.

Back to Financials Help