How to compare draft and executed versions for Reseller Agreements

Compare the executed reseller agreement against the last approved draft as a complete contract package, not just a master agreement. Establish which files were approved and signed, compare text and page images, and trace substantive differences through product schedules, pricing tables, incorporated policies, and customer terms. From the reseller’s perspective, prioritize changes affecting margin, sales eligibility, customer access, support commitments, and exit rights. The deliverable is a cited version-comparison checklist showing each difference, its commercial consequence, approval evidence, and required correction or escalation.

When to use this workflow

Use this workflow when reseller-side counsel receives a signed agreement, inherits uncertain version history, or discovers that operations is using terms different from those approved. It also suits in-house teams reconciling signature packages before releasing contract data to sales, finance, and support.

The scope is reconciliation: determine what changed, whether it was authorized, and what remains unresolved before relying on the package. It is not a fresh negotiation of every clause. The guide uses a US commercial-contract orientation; governing-law, state dealer or franchise, restrictive-covenant, and cross-border questions require matter-specific analysis. An unexplained difference is an issue to investigate, not an enforceability conclusion.

What you need

Collect these inputs before comparing:

• The last approved draft, its native file where available, and the approval email or decision record.
• The executed master, signature pages, execution correspondence, and available signing record.
• Product and territory schedules, discount tables, deal-registration rules, support schedules, customer-license terms, and incorporated policies in the relevant versions.
• Side letters, amendments, and evidence identifying which attachments accompanied execution.
• The reseller’s negotiation checklist: preferred terms, accepted fallbacks, approval owners, and documented exceptions.
• A representative transaction showing the supplier’s pricing base, resale revenue, discount eligibility, support responsibility, and renewal or direct-sale compensation.

Preserve originals. Assign stable document IDs to working copies and distinguish receipt dates from document dates. If the approved draft or an incorporated policy is unavailable, record that limitation rather than substituting the newest file without explanation.

Use the template

The Reseller Agreements — Version comparison checklist is the working record. You can copy this table into your working document or spreadsheet. Use one row per substantive difference or unresolved package defect; group harmless formatting changes only after checking them.

Citations should combine document ID, section, and page; for pricing tables, add the row label or cell reference. Record the actual change, not merely “pricing revised.” Distinguish verified wording, missing material, unreadable or redacted text, and unresolved approval. Identify the decision-maker and approval evidence in the final column.

Keep commercial acceptance separate from legal interpretation. Approval of reduced margin does not answer whether the change followed the relevant amendment provision. Where the same change affects several provisions, link their row IDs rather than duplicating the finding.

Step by step

1. Establish the approved baseline and execution package

Identify the draft the reseller actually approved for signature. A later timestamp does not prove approval: the file may contain unreviewed edits or only signature formatting. Match approval correspondence to the filename, attachment, and material terms.

Inventory the executed package against the draft’s attachment list. Check entity names, signature-page references, effective-date fields, product scope, and schedule identifiers. Separate later amendments from the original execution comparison, then record whether they address any identified difference.

Record: a baseline row identifying the approved draft, executed files, approval reference, and uncertainty about completeness. Keep the supporting file inventory with the checklist.

2. Map hierarchy and incorporated material

Read precedence and incorporation provisions before deciding which difference controls. An unchanged master may sit above a changed product appendix that determines renewal discounts or customer-license obligations.

The SEC-filed Avaya agreement generally prioritizes Product Appendices over Product Group Attachments and those attachments over the master terms, subject to express overrides. It also specifies amendments in a writing signed by both parties. These are example-specific provisions, not universal rules (Avaya, §§20.4–20.5).

For incorporated web policies, seek the version associated with execution and examine language permitting later changes. A current webpage does not establish the execution-date wording. Identify whether the changed term appears in a controlling schedule or only in a subordinate document.

Record: rows for changed hierarchy, incorporated versions, and missing attachments, with affected provisions and retrieval requests.

3. Run text comparison, then inspect the pages

Use text comparison to identify additions, deletions, substitutions, and moved passages. Where scans require text recognition, check extracted wording against page images before treating it as evidence. Tables, footnotes, symbols, and words such as “not” deserve particular attention.

Visually inspect pricing schedules, signature pages, handwritten changes, blank fields, and attachment boundaries. Confirm that moved clauses retain their definitions and cross-references. A detached signature page does not, without further evidence, identify every schedule included in the signed package.

Record: paired draft and executed citations for each substantive difference, with a brief visual-verification note. Label unreadable wording as unreadable; do not reconstruct it from the draft.

4. Test changes to reseller economics and sales eligibility

Compare discounts separately from commissions, rebates, and referral payments. Check eligible products, revenue bases, tier mechanics, returns, taxes, payment triggers, renewals, direct sales, and post-termination compensation. A percentage can stay constant while its eligible base shrinks.

The historical Agilent agreement excludes compensation on direct end-user purchases and conditions certain add-on or upgrade discounts on the reseller’s original sale and continuing support. This illustrates eligibility wording, not customary terms (Agilent, §§3(c)–(d)).

Test representative transactions under both versions, documenting assumptions. For changed resale-pricing language, distinguish recommendations, advertised-price conditions, and binding minimum resale prices. FTC guidance describes federal rule-of-reason analysis for manufacturer-imposed vertical minimum-price arrangements and notes different state and international treatment; it does not approve a particular clause (FTC guidance).

Record: the changed input, modeled consequence, assumptions, and commercial or legal approval needed.

5. Trace changes through customer and operational commitments

Review differences in territory, permitted channels, reserved accounts, deal registration, reporting, support allocation, warranties, indemnities, liability limitations, and customer-license flow-downs. Follow dependent definitions: adding prospects to a protected customer category may broaden a solicitation restriction even if its operative clause is unchanged. Escalate enforceability separately from the wording comparison.

Ask what the reseller has already promised downstream. A new supplier warranty exclusion may leave an unmatched customer commitment. A narrower support entitlement may affect implementation work or renewal pricing.

Examine termination differences separately for invoice acceleration, inventory treatment, existing licenses, renewals, and support. Avaya’s filed wording preserves properly granted existing end-user licenses on termination of the reseller’s license, while a separate clause accelerates invoices on agreement termination. Neither provision establishes continuing support or renewal compensation (Avaya, §§7.7 and 17.4).

Record: the affected downstream commitment, dependent provision, operational owner, and unresolved interpretation.

6. Reconcile material differences with approval evidence

Classify differences as approved, unapproved, approval unresolved, or requiring interpretation. Link approval to the specific change rather than a general instruction to “proceed.” Check whether an economic approval also covered changed product scope, reporting duties, or termination exposure.

Where correction is needed, prepare proposed wording against the executed text and identify the relevant amendment provision. Do not edit the signed file in place or present a corrected draft as the executed agreement. Determine the appropriate corrective instrument and approvals from the actual contract, governing law, and circumstances. Internal acceptance alone should not be recorded as a bilateral correction.

Record: disposition, approval reference, proposed correction, responsible decision-maker, and any explicit interim operating instruction.

7. Close the comparison and release qualified findings

Perform a second pass over high-impact differences and every row marked missing, ambiguous, redacted, or unreadable. Confirm that proposed corrections address dependent definitions, cross-references, and schedules. Preserve the comparison report alongside unaltered source files.

Issue a short summary separating accepted changes, corrections awaiting agreement, and unresolved evidence gaps. Update downstream records with verified terms and explicit qualifications. For a changed notice period, verify its trigger, delivery method, recipient, and day-counting language before recording a deadline; an unavailable schedule remains a gap, not an assumed period.

Record: final disposition and evidence for closed rows; an owner, next action, and target follow-up date for open rows. A completed review may still contain clearly assigned unresolved issues.

Worked example

Fictional scenario: Cedar Quay Systems LLC resells inventory software supplied by Meridian Arc Software Inc. Counsel approved draft D-04 with a 24% discount on initial subscriptions and renewals. Executed package E-01 contains a revised pricing appendix reducing renewal discounts to 12%, while leaving initial-subscription discounts unchanged.

A proposed renewal has a $50,000 eligible supplier list-price base; the supplier order has not been submitted. The signed master also references a support schedule absent from the received package. All parties, documents, terms, and amounts are fictional.

Row 01 assumes the same $50,000 eligible base in both versions: supplier cost rises from $38,000 to $44,000 before other adjustments. It does not establish lost profit without the customer’s resale price and other costs. Finance must confirm the pricing base before relying on the model.

The immediate decision changes from routine handoff to targeted escalation before order submission. Row 02 requires additional material, not an invented replacement entitlement. Row 03 prevents treating the negotiated draft schedule as executed without supporting evidence. Neither evidence gap should obscure the independently verified renewal-price change.

Common mistakes

• Comparing only the master. Reconcile incorporated schedules; unchanged master text can conceal changed renewal economics.
• Treating signatures as package confirmation. Match attachment identities and execution correspondence instead of assuming every received file was signed together.
• Checking percentages but not eligibility. Test direct sales, renewals, upgrades, returns, and registration conditions separately.
• Calling an unavailable attachment deleted. Distinguish missing evidence from verified omission and assign retrieval.
• Fixing the signed file in place. Preserve it and prepare a separate proposed correction under the relevant amendment framework.

Final quality check

• The baseline is tied to actual approval evidence, not just a filename.
• Referenced schedules are present or explicitly listed as missing.
• Material differences have draft and executed citations, with source wording verified.
• Extracted text and pricing tables have been checked against page images.
• Economic calculations disclose bases, eligibility conditions, and assumptions.
• Customer, support, and termination dependencies are addressed where affected.
• Every issue is resolved with evidence or assigned a decision-maker and next action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support review and redlining. In Word, choose the represented party—or neither—and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across multiple documents; execution-package verification, approval reconciliation, and legal judgment remain with counsel. Book a demo to discuss this reseller-agreement workflow.

Frequently asked questions

Which draft should be the comparison baseline?

Use the version actually approved for signature. If approval cannot be established, compare plausible candidates separately and label the baseline unresolved rather than silently selecting one.

Should every formatting difference enter the checklist?

No. Group verified cosmetic changes. Record differences individually when they could alter pricing-table alignment, attachment identity, numbering, cross-references, or interpretation.

What if the executed version includes an unapproved concession?

Preserve the evidence, identify the approval gap, and escalate the consequence. Prepare corrective wording separately. Lack of internal approval does not itself resolve the concession’s legal effect; assess the actual contract and circumstances.

Can operations use the approved draft while correction is pending?

Do not present it as executed text. Counsel and the responsible business owner should issue explicit interim instructions identifying disputed terms and affected orders, renewals, or support commitments. Record any agreed correction separately.

Sources

• FTC — Manufacturer-imposed Requirements
• SEC — Agilent LSCA Value Added Reseller Program Agreement
• SEC — Avaya Reseller Agreement

This general workflow guide separates practical recommendations from legal requirements. Filed agreements illustrate wording, not market standards; rights depend on actual language, governing law, facts, and deal context.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.