How to extract obligations with source references for Reseller Agreements

Extract reseller obligations from the executed agreement, applicable schedules, amendments, and incorporated policies, then translate each requirement into an actor–action–trigger–deadline record. Preserve conditions and exceptions, give every record a clause-level source reference, and assign an internal owner and completion evidence. The resulting obligations register should distinguish binding duties from conditions for discounts or other benefits, expose missing sources, and allow counsel to verify each operational instruction against the controlling language before business teams rely on it.

When to use this workflow

Use this workflow when a reseller signs or amends an agreement, adds a product line, changes support responsibilities, or inherits contracts through an acquisition. It serves commercial counsel, legal operations, channel sales, finance, and support teams translating contractual requirements into accountable work.

The scope is extraction and verification, not a complete contract risk review. Keep reseller responsibilities central, including customer-license flow-downs, reporting, training, payment, support, audit cooperation, and rebate claims. Include supplier duties where they affect reseller performance.

This is a US-oriented professional workflow guide. Contract rights depend on the language, governing law, facts, and deal context. Competition, franchise, dealer, and restrictive-covenant questions require separate analysis; recording a restriction does not establish its enforceability.

What you need

Assemble the executed master and signature pages, amendments, product and territory schedules, discount tables, incorporated program policies, support requirements, and applicable end-user terms. Obtain relevant historical versions rather than assuming today’s online policy governed an earlier transaction.

Collect trigger and performance evidence: accepted orders, invoices, customer-license records, training certificates, submitted reports, rebate claims, and notices. These documents may establish that an event occurred; they do not replace the agreement as authority for the requirement.

Create a document index with stable IDs, titles, dates, execution status, and relationships to the master. Obtain the internal responsibility map for finance, sales operations, support, and legal. Identify missing attachments, disputed effective dates, and uncertain policy versions before translating them into operational instructions.

Use the template

Use the Reseller Agreements — Obligations register below. You can copy this table into your working document or spreadsheet. Create one row for each independently actionable duty, restriction, or benefit condition.

In Source / wording, enter the document ID and version, section, printed page or labeled PDF page, and a short operative excerpt. Include cross-references supplying definitions or exceptions. A document link alone is insufficient; retain a stable copy in the document index.

Actor / action identifies the contracting party separately from the internal owner. Trigger / dependency captures prerequisites such as order acceptance, deployment, or receipt of notice. Due / recurrence preserves the contractual formula; add a calculated date only after verifying its inputs.

Use Completion evidence for the required proof and its location. Use Status / next action to distinguish verified requirements, incomplete performance, ambiguous wording, and missing evidence. Assign unresolved issues to a person or role. If wording is unavailable, identify the missing source rather than supplying an invented excerpt.

Step by step

1. Establish the controlling document set

Read incorporation, precedence, and amendment provisions first. Map schedules to products, territories, and customer categories. Determine whether an amendment changes the master generally or only a named program or transaction.

The SEC-filed Avaya agreement generally prioritizes Product Appendices over Product Group Attachments and those attachments over the agreement, subject to express overrides. It also specifies signed written amendments. This is example-specific wording, not a hierarchy applicable to other agreements (Avaya, §§20.4–20.5).

Record: Enter controlling source IDs and cross-references. Mark affected rows blocked if an incorporated attachment is unavailable; do not treat its absence as proof that no requirement exists.

2. Distinguish duties, restrictions, and benefit conditions

Review by commercial subject, not just searches for “shall” or “must.” Requirements can appear in eligibility rules, order procedures, customer-license provisions, and product schedules. Include negative duties, such as restrictions on sales outside an authorized territory.

Separate required performance from conditions for a discount, rebate, or commission. The historical Agilent agreement excludes compensation for direct end-user purchases and conditions certain add-on or upgrade discounts on the reseller’s original sale and continuing support. Those provisions establish specific economics, not general reseller entitlements (Agilent, §§3(c)–(d)).

Record: Assign a type and describe the action without converting an optional benefit into an unconditional duty. Link any independently binding support obligation separately.

3. Split clauses into actionable records

Create separate rows when actions have different triggers, owners, deadlines, or completion evidence. Keep required report fields within the reporting row unless a separate correction or certification process requires independent tracking.

Preserve product limitations, customer exclusions, and qualifications. Follow defined terms such as “Net Sales,” “Authorized Customer,” and “Business Day” before paraphrasing. A concise operational instruction must not broaden the source language.

Agilent’s agreement separately addresses monthly sales reporting and invoice payment, including consequences for an uncured failure following written notice. These are distinct performance events, not one combined reporting-and-payment obligation (Agilent, §§3(b), 4(h)).

Record: Give each independent action an ID, precise citation, applicable definitions, and linked exceptions.

4. Verify triggers before calculating dates

Distinguish fixed deadlines from event-dependent periods. An invoice date differs from receipt; a cure period may require qualifying notice rather than awareness of a problem. Capture permitted notice methods, recipients, deemed-receipt provisions, and applicable day definitions.

Keep the timing formula beside any calculated date so another reviewer can reproduce it. For recurring duties, determine whether the period follows calendar months, contract quarters, or another definition. Assign recurring performance instances without overwriting the standing requirement.

Several termination-notice and cure periods in the filed Avaya example are redacted. Those omissions prevent calculation of the affected deadlines (Avaya, §§17.1–17.3).

Record: Enter the formula, trigger evidence, and verified date—or the missing input and reviewer responsible for resolving it.

5. Map customer and supplier dependencies

Identify dependencies that prevent completion. A customer may need to accept license terms before activation; a supplier may need to approve marketing material before publication. State who obtains approval and how the team handles work awaiting it.

Read termination requirements separately from ongoing performance. Avaya’s example preserves properly granted existing end-user licenses and separately accelerates invoices upon termination. License survival alone does not establish continuing support, renewal compensation, or inventory sell-off rights (Avaya, §§7.7, 17.4).

Record: Link prerequisite and dependent rows. Specify the affected customer population, product, transaction, or period; avoid a portfolio-wide instruction drawn from a product-specific clause.

6. Assign ownership and completion evidence

Assign an accountable owner rather than sending every requirement to legal. Finance can own payment evidence, sales operations reporting, and support service records. Counsel should resolve interpretation questions and approve translations of ambiguous provisions.

Match proof to the required act: a report plus transmission confirmation, customer acceptance of the applicable license version, or a completed training certificate. Preparation, approval, sending, receipt, and acceptance are different events.

For audit cooperation, preserve contractual scope, notice conditions, access limits, and related recordkeeping duties. Do not translate limited access into an instruction to disclose all business records.

Record: Name the owner, required proof, evidence location, and closure approval. Where no evidence has been located, keep performance unverified rather than asserting breach.

7. Verify sources and route unresolved questions

Have a second reviewer trace each operational instruction to its source. Test whether someone could perform it without guessing about timing, product scope, or prerequisites. Reconcile amendments and inspect schedules visually when text extraction is unreliable.

Separate extraction from legal clearance. For pricing restrictions, distinguish suggested prices, advertised-price conditions, and binding resale-price requirements. FTC guidance describes federal rule-of-reason analysis for vertical minimum resale-price arrangements while noting different treatment under some state and international regimes (FTC, Manufacturer-imposed Requirements).

Record: Mark source-verified rows separately from completed performance. Assign unresolved legal or interpretive questions, identify affected decisions, and state whether interim operational instructions have been approved.

Worked example

Entirely fictional scenario: Harborline Systems resells Northpeak Instruments’ monitoring devices. Their fictional executed agreement RA-01 requires monthly sales reports and conditions upgrade discounts on the original sale and current support. Incorporated schedule CL-02 requires customer-license acceptance before activation.

Finance asks whether an upgrade discount can be claimed on a new order. Counsel has both executed documents and the original customer invoice, but no current support record. Sales operations has drafted the monthly report without locating submission confirmation. Customer acceptance has not been established. The following excerpts and records are fictional.

These rows change the decision. A prepared report cannot be closed as submitted, but missing confirmation does not establish that submission failed. The original invoice supports only one discount condition; finance must verify support before claiming eligibility. Implementation receives a specific pre-activation requirement rather than a general instruction to retain paperwork.

No available evidence establishes current support or completed acceptance. The register assigns those gaps without inventing performance dates or treating uncertainty as a proven breach.

Common mistakes

• Citing only the master. Add the controlling schedule, version, and cross-reference so product-specific exceptions remain visible.
• Combining payment and cure timing. Separate the ordinary payment duty from consequences requiring nonpayment and qualifying notice.
• Turning benefit conditions into mandatory services. Label discount eligibility separately while retaining independently binding support duties.
• Treating silence as permission. Record “not located in reviewed documents,” identify that document set, and assign the question.
• Confusing source verification with completion. Maintain distinct statuses for a verified requirement and evidence that it was performed.

Final quality check

• Every row identifies the actor and a specific action or restriction.
• Source references resolve to the correct document version and clause or page.
• Definitions, exceptions, incorporation, and precedence have been checked.
• Timing formulas remain visible; calculated dates use verified triggers.
• Duties and commercial benefit conditions are distinguishable.
• Evidence addresses the relevant action, customer, product, and period.
• Open issues are resolved or assigned, with affected operational decisions identified.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support review through quoted findings, text locations, severity rankings, and identification of missing language. Tabular review supports work across documents; due diligence classification can organize the source set and prioritize human review. The register remains your team’s work product, with lawyers verifying sources and interpretation and business owners confirming performance. Book a demo to discuss this reseller workflow.

Frequently asked questions

Should supplier obligations appear in a reseller register?

Yes, where they affect reseller performance. Identify the supplier as actor and assign an internal contact to follow up. Do not rewrite a supplier obligation as the reseller’s duty to guarantee its performance.

How should we handle an incorporated online policy?

Check the incorporation and change provisions, identify the relevant version, and preserve an accessible copy. Flag uncertain applicability rather than assuming the current webpage controls earlier transactions.

Can we calculate a deadline from a redacted agreement?

Only if all necessary inputs remain available. If a period or trigger is missing, preserve the known components, request the complete source, and leave the calculation unresolved.

How should amendments change existing records?

Retain the earlier source and history. Identify affected rows and confirm the amendment’s effective scope, including products, transactions, and periods. Update operational instructions only after resolving those dependencies.

Sources

• SEC-filed Agilent–O.I. Corporation LSCA Value Added Reseller Program Agreement — historical reporting, payment, and discount provisions.
• SEC-filed Avaya Reseller Agreement — historical precedence, amendment, termination, and license provisions.
• FTC: Manufacturer-imposed Requirements — federal competition guidance.

Filed agreements illustrate wording, not market standards. The live FTC page does not independently establish its exact historical text on October 13, 2026.

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.