Use this guide to create the owner contract, build its revenue SOV, prepare contract documents for approval and e-signature, download a PDF, and understand deletion and accounting-sync consequences.
Start here
- Create the owner contract: Create a Prime Contract.
- Build the billing structure: Build and lock the Prime SOV.
- Send the contract for signature: Prepare the contract for e-signature.
- Bill or change the owner: Use the Prime Contract with invoices and changes.
- Download or delete: Use Prime Contract actions.
- Something is blocked: Troubleshoot Prime Contract.
Create and administer
Create a Prime Contract
- Open Prime Contract.
- Select Add Prime Contract.
- Choose the owner company.
- Enter the contract number, title, dates, and other agreement details.
- Save, then build the Prime SOV.
The Prime Contract tracks owner revenue. Vendor and subcontractor costs belong on Commitments or Purchase Orders.
A project can have more than one Prime Contract. Use the Prime Contract switcher to select the agreement you intend to review, invoice, change, download, or delete.
Build and lock the Prime SOV
The Prime SOV is the line-item structure used by Owner invoices and Prime Change Orders. Add lines manually or import a CSV on desktop web. Confirm for each line:
- Description
- Revenue code, when enabled
- Subproject, when used
- Amount
- Retention
- Billing Type for progress billing or time-and-material billing
Revenue codes organize owner revenue. Cost codes and cost types organize vendor cost, so don't use the Prime SOV as if it were a subcontractor Commitment.
Lock the SOV after approval. Use Unlock the SOV for editing on a commitment only to correct the approved structure. A later owner scope change belongs on a Prime Change Order so its value and history remain separate.
Note: Once an SOV line has invoice activity, recoding it splits billing history. A line created by a Prime Change Order should be corrected through that change.
Prepare the contract for e-signature
- Finish the Draft contract and Prime SOV.
- Select Actions → Prepare for Esigning.
- Upload the contract document.
- Configure recipients, approvers, signers, and signature fields.
- Confirm and send.
When approvers are configured, they review in order while the contract is Awaiting Approval. It then moves to Out for Signing, Ready to Countersign, and Fully Executed as signatures are completed.
While an active e-signature flow controls the record, status can't be changed manually. Editing after execution requires Edit commitments and change orders after they have been executed and can require a separate accounting correction.
Understand approvals, status, and notifications
The contract document workflow notifies the configured approver or signer when their action is due. Its normal sequence is:
Draft → Awaiting Approval, when configured → Out for Signing → Ready to Countersign → Fully Executed
Void keeps a contract in project history without treating it as active. Use Void instead of deletion when the agreement should remain visible for audit or explanation.
Approvals and signatures apply to the contract document flow. They don't approve an Owner invoice or Prime Change Order; each has its own status and actions.
Connected owner workflows
Use the Prime Contract with invoices and changes
- Owner invoices bill progress against Prime SOV lines. See How to use Invoices.
- Prime Change Orders change owner revenue and can add lines to the Prime SOV when executed. See How to use Change Events.
- A Prime Change Order's Billable On date controls when its value counts as billable and when its Budget Modification is created or updated.
- Fully Executed records the document lifecycle. It is separate from Billable On.
Don't create a new Prime Contract for a monthly billing cycle or scope change. Use an Owner invoice or Prime Change Order against the existing agreement.
Use Prime Contract actions
From Actions:
- Prepare for Esigning appears on a Draft without an active contract signing flow.
- Download PDF compiles the current contract PDF.
- Delete Prime Contract opens a destructive confirmation.
Deleting a Prime Contract removes its Owner invoices, SOV lines, Change Orders, attachments, and contract documents. The dialog lists the affected records before confirmation. This can't be undone in the app.
Correct an erroneous field or use Void when history should remain. Delete only when the entire record and every dependent owner-financial record should be removed.
Accounting and troubleshooting
Understand Prime Contract accounting sync
Sage Intacct can exchange Prime Contracts, SOV lines, Prime Change Orders, and owner invoices according to the organization's configured mappings. Some outbound flows create the accounting document but don't send later edits. Confirm the configured direction before changing an executed record.
QuickBooks owner billing is invoice-driven: an eligible Approved or Paid Owner invoice can become a QuickBooks Invoice, while a negative one can become a Credit Memo.
An integration icon or status describes the link to accounting. Fix and retry an existing failed link; don't recreate the Prime Contract or invoice.
Troubleshoot Prime Contract
Prime Contract is missing
Confirm the Financial package and View prime contracts. Also confirm the intended project and, when several Prime Contracts exist, select the correct record in the switcher.
Add Prime Contract is missing
The user needs Create new commitments, make changes to existing commitments.
An SOV line is read-only
Check whether the SOV is locked, the contract is executed, the line came from a Prime Change Order, or invoice activity exists. Correct the source record instead of rewriting established billing history.
Prepare for Esigning is missing
The contract must be Draft, the user needs financial write access, and no active contract signing flow can already exist.
Status can't be changed
An active e-signature flow controls status. Complete or resolve that flow rather than forcing the contract ahead manually.
Delete would remove owner billing history
Cancel the deletion. Correct the contract or use Void unless every listed dependent record should be removed.