Open the contract you want to finalize. Click the Finalize button in the contract record header. The button appears when the contract is in a finalizable state (Draft, In Negotiation, or In Review).

After weeks of negotiation, you have an agreed version of the contract. Before it can go to approval or signature, you need to lock in the final version and close the negotiation. If the counterparty made last-minute changes you did not catch, those could slip through to execution.
Finalization closes negotiation and marks the contract as ready for the next stage. When you upload a final version, Pactly automatically compares it against the last negotiated version and flags any discrepancies, so nothing slips through unnoticed.
Open the contract you want to finalize. Click the Finalize button in the contract record header. The button appears when the contract is in a finalizable state (Draft, In Negotiation, or In Review).

Upload a new version (Word .docx or PDF) for discrepancy checking against the last negotiated version, or continue with the latest version already in the system. Choose "Upload" when the counterparty sent a final clean version. Choose "Continue" when no changes were made outside of Pactly.

After confirming, the contract moves to the next stage: Pending Approval if approvers are configured, or Pending Signature if no approval is required. The finalization event is recorded on the contract timeline.
Your organization may have rules that check the contract before finalization is allowed, for example requiring certain fields to be filled in. If a check fails, Pactly shows which conditions were not met.
To resolve a block, update the contract to fix the issue (fill in missing fields, verify parties, etc.) and try again. If you believe the block doesn’t apply, ask your administrator to override it.
The sections below cover configuration, advanced options, and troubleshooting that most users won’t need day-to-day.
Finalization is available for Template Contracts and Playbook Contracts only. External Contracts follow a different flow and do not require this step (they start at Pending Approval).
The contract must be in a finalizable state: Draft or In Negotiation for Template Contracts, In Review for Playbook Contracts.
When uploading a new version, the file format affects discrepancy checking:
| Format | Discrepancy Check | When to use |
|---|---|---|
| Word (.docx) | Pactly extracts the text and compares it against the last negotiated version, flagging any differences. | Recommended. Use whenever a Word version is available. |
| Text is extracted from the PDF for comparison, but results may be less precise due to PDF text extraction limitations. | Use when a Word version is not available. |
The discrepancy check runs asynchronously after finalization completes. Results appear on the contract record within a few seconds and are stored for later review.
Administrators can configure proactive evaluation rules that check the contract before finalization is allowed. These rules enforce data completeness and compliance requirements.
When a user clicks Finalize, Pactly evaluates all active blocking configurations for your company. Rules can check:
If the contract fails one or more checks, finalization is blocked and an explanation is shown listing which conditions were not met. Administrators can manually override a block for a specific contract when the business context justifies it. The override is logged on the timeline as an audit event.
Once a contract is finalized:
If a contract was finalized by mistake, or further negotiation is needed: