# Negotiation-to-contract record chain and keys | SourceX

Canonical: https://refer.sourcex.si/guides/negotiation-to-contract-record-linkage
Last updated: 2026-11-04

A company connects negotiation-to-contract records with three keys: the opportunity ID, the draft number and the e-signature package ID. The opportunity ID ties the customer's request and the sign-off to one deal. The draft number ties the approved terms to a specific order form. The package ID, plus a deal ID stored on that package, ties the signed document back to the deal. When all three are present, a commercial exception can be followed from first request to signature without guesswork.

This record chain is part of the [negotiation-to-contract guide](/guides/chain-negotiation-to-contract), which covers the metadata a partner can collect. Here the job is narrower: name each hop, its key and where it snaps.

## Step, record, key, system

One Illustrative deal shows the chain end to end. A fictional 340-person fleet telematics vendor renews a three-year order. The customer asks for a 9% discount and net-75 payment terms instead of the standard net 30.

| Step | Record | Key that carries it forward | System |
|---|---|---|---|
| 1. Customer asks for terms outside policy | Email thread with the request | Opportunity ID, if the thread is logged to the deal | Outlook |
| 2. Exception entered on the deal | Discount and payment-term field changes | Opportunity record, with field history | Salesforce |
| 3. Exception sent for sign-off | Approval history entry | Opportunity record; actual approver named | Salesforce |
| 4. Approved terms written up | Order form, draft 3 | Draft number, attached to the approval request | Salesforce file or shared drive |
| 5. Order form sent for signature | Signing package carrying draft 3 | Package ID; draft number in the document name | DocuSign |
| 6. Signed package tied back to the deal | Custom field on the package | Opportunity ID stored there | DocuSign |
| 7. Any change after sending | Certificate of Completion | Package ID; Envelope Updated entry | DocuSign |

Illustrative. The keys describe how a join would be made, not a tested export from any company.

## What each key has to carry

**Opportunity ID (steps 1 to 3).** A customer's message reaches the deal only if someone logs it or uses a subject convention with the deal name. Inside the CRM, the field changes and the sign-off share one record, so that join is strong; the approval history list names each step's status and the person who actually approved. Field history is the limit: without Field Audit Trail it is kept for up to 18 months, and up to 24 months through the API, so original exception values on older deals may be gone even though the sign-off survives.

**Draft number (steps 4 and 5).** The approval says yes to something; the draft number says to what. If the draft is attached to the approval request, the approved terms are provable. If it is only described in a comment ("approved per call"), the join between approval and order form is a person's memory.

**Package ID and the deal field (steps 5 to 7).** The e-signature platform lets a sender attach hidden text or list fields to each package for finding and tracking it later. That is where a deal ID belongs. Whether the team populated it, and from which year, is a question for the company's administrator.

## Where the chain usually snaps

| Hop | Common break | What the record looks like afterward |
|---|---|---|
| Email to deal | Request never logged; account executive's mailbox only | An exception appears on the deal with no visible cause |
| Field to history | History window passed; Field Audit Trail off | The approval exists, the original discount value does not |
| Approval to draft | Draft described, not attached | Nobody can prove which terms were approved |
| Draft to signing package | File renamed or redrafted outside the system | Signed document cannot be matched to a draft number |
| Signed package to deal | Sent from a personal account with no deal field | Signed contracts float free of the deals they close |

In the Illustrative vendor, every hop held from 2022 onward. Before 2022 the last hop broke: packages sent from individual e-signature accounts carried no deal ID.

## Repairing the signed-order link

There are two repairs, and they produce different kinds of evidence.

1. **Going forward: a real key.** Fill the opportunity ID custom field at send time, by hand or through whatever CRM integration the administrator has set up. From that date, the join is exact.
2. **Looking back: an inferred join.** For older envelopes, a match on account name, envelope date and draft number in the file name can recover many links. It is still an inference. Label it as one, with the share of envelopes it covers if the company knows it.

A partner does neither repair. The point is to learn which kind of link exists for which years, so the introduction says "exact from 2022, inferred before" rather than "fully linked."

## A late redline seen through the keys

Keys do more than join records; they expose drift. Suppose the customer returns draft 4 by email four days after draft 3 was approved, adding a dedicated support contact, and the account executive accepts it in a reply. The approval history still points at draft 3. The envelope carries draft 4. Both join to the same opportunity ID, so the mismatch is visible to anyone comparing draft numbers, and the Certificate of Completion will show an Envelope Updated entry if the document was corrected after sending.

Without draft numbers, the same deal reads as one clean approval and one signature. The [missing-context comparison](/guides/negotiation-to-contract-missing-context) reads a deal like this with and without its surrounding records, and the [completeness checklist](/resources/negotiation-to-contract-completeness-checklist) scores how often the drift can be detected.

## Owners of each key, and what stays unknown

The VP of Revenue Operations or the Salesforce administrator owns the opportunity and approval keys. Whoever administers DocuSign owns the envelope field. IT owns mailbox retention. None of them can authorize a licensing discussion; the CEO can, with the general counsel reviewing customer contracts, because signed orders carry customer terms. The [customer contract restrictions guide](/guides/customer-contract-data-use-restrictions) explains what counsel will look for.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: what customer contracts permit, how much field history still exists, and how many envelopes join exactly. Partners never ask for or handle raw records, and they sign the Channel Partner Agreement before introducing. For the systems themselves, see [Outlook](/systems/microsoft-outlook), [bulk-downloading DocuSign envelopes](/systems/docusign-bulk-download-envelopes) and [Salesforce data archiving](/guides/salesforce-data-archiving); for why these records matter, see [negotiation data for AI training](/data-types/negotiation-data-ai-training).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client can name its three keys and the year each one became reliable, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [terms](/terms) before introducing its sponsor.

## Sources

- https://help.salesforce.com/s/articleView?language=en_US&id=platform.approvals_approval_history.htm&type=5
- https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5
- https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopecustomfields/
- https://support.docusign.com/s/document-item?language=en_US&bundleId=oeq1643226594604&topicId=gpa1578456339545.html
- https://refer.sourcex.si/terms
