# US 2002/0178120 A1 · Contract generation and administration system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2002/0178120 A1
- Document ID: US20020178120A1
- Status: Published application
- Kind: A1
- Application number: 09/862,626
- Filed: 2001-05-22
- Published: 2002-11-28
- Earliest claimed: 2001-05-22
- Inventors: Zachariah J. Reid; Lucia T. Akers; Alan M. Braaten; James Ronald Clark; John F. Hunt; Daniel R. Schuessler
- Web page: https://patentgrep.com/patent/US20020178120A1

## CPC

- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A contract generation and administration system and method are provided. The system and method include a database for storing detailed data relating to draft and finalized contracts. The database is used to track pending and executed agreements, and to track manage specific agreement obligations and obligation triggering events to ensure that each agreement obligation is met. The system is capable of managing detailed agreements and numerous obligation types including financial and non-financial obligations. The system may also be used to generate correspondence and invoices as are necessary to meet various agreement obligations.

## Claims

### Claim 1

A contract generation and administration system comprising: a single contract database comprising data obtained from multiple contract documents, said data organized into fields comprising: draft contract status, contract identifier, contract type, effective date, and expiration date; and a field comprising obligation type, owner, status or due date; said system capable of generating reports based on said database, said reports obtainable through search of said fields; and said database being selectively accessible by a plurality of users.

### Claim 2 (depends on 1)

The system of claim 1 wherein the contract documents are selected from the group consisting of: confidentiality contracts, software licenses, technology licenses, lease contracts and service contracts.

### Claim 3 (depends on 1)

The system of claim 1 wherein the contract documents are licenses.

### Claim 4 (depends on 1)

The system of claim 1 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 5 (depends on 1)

The system of claim 1 wherein said draft contract status field indicates whether a contract document is being reviewed and/or executed.

### Claim 6 (depends on 1)

The system of claim 1 wherein said obligation type field is substantially defined as training, meeting, shipping, payment, receipt of payment, reporting, start-up, secrecy, restricted use, maintenance or technology transfer.

### Claim 7 (depends on 1)

The system of claim 1 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit, and/or user's authority level.

### Claim 8 (depends on 1)

The system of claim 1 wherein said reports are selected from the group consisting of: accrued revenue, obligations due, obligations owed, customer history, open invoice, depreciation, corporate plan, stewardship, implementation plan, payments requiring invoice, anticipated payments, audit, pending contracts, active contracts and expiring contracts.

### Claim 9 (depends on 1)

The system of claim 1 wherein said database further comprises standard contract forms or clauses.

### Claim 10 (depends on 1)

The system of claim 1 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 11 (depends on 1)

The system of claim 1 wherein said database is capable of using its data to generate invoices and correspondence.

### Claim 12

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said contract draft having one or more obligations;
storing data obtained from the draft in a single contract database comprising data obtained from multiple contract documents;
after execution of said draft, storing data obtained from the resulting contract in said database, said data organized into fields comprising: draft contract status, contract identifier, contract type, effective date, and expiration date; and a field comprising obligation type, status, owner or due date; and said database capable of generating reports based on said data, said reports obtainable through search of said fields; and said database being selectively accessible by a plurality of users; and
retrieving from said database a report of outstanding obligations.

### Claim 13 (depends on 12)

The method of claim 12 further comprising the step of analyzing said report to determine which, if any, of said obligations should be acted upon.

### Claim 14 (depends on 13)

The method of claim 13 further comprising the step of deciding, based on said analysis, whether to act upon one or more of said obligations.

### Claim 15 (depends on 13)

The method of claim 13 further comprising the step of taking action based on said analysis.

### Claim 16 (depends on 12)

The method of claim 12 further comprising the step of taking action based on an analysis of said report and updating said database to reflect said action.

### Claim 17 (depends on 12)

The method of claim 12 further comprising the step of routing the contract draft to one or more parties for review and/or execution.

### Claim 18 (depends on 17)

The method of claim 17 further comprising the step of storing review or execution data in the contract database.

### Claim 19 (depends on 12)

The method of claim 12 wherein the draft is selected from the group consisting of: draft confidentiality contracts, draft software licenses, draft technology licenses and draft service contracts.

### Claim 20 (depends on 12)

The method of claim 12 wherein the draft is a draft license contract.

### Claim 21 (depends on 12)

The method of claim 12 wherein the report is organized by obligation status, type, owner, or due date.

### Claim 22 (depends on 12)

The method of claim 12 wherein the report lists outstanding financial obligations.

### Claim 23 (depends on 12)

The method of claim 12 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 24 (depends on 12)

The method of claim 12 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit, and/or user's authority level.

### Claim 25 (depends on 12)

The method of claim 12 wherein said contract database is used to indicate whether a contract document is being reviewed and/or executed.

### Claim 26 (depends on 12)

The method of claim 12 wherein said database further comprises standard contract forms or clauses.

### Claim 27 (depends on 12)

The method of claim 12 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 28 (depends on 12)

The method of claim 12 further comprising the step of storing the invoice in the database.

### Claim 29

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract having one or more obligations;
routing the draft contract to one or more parties for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
storing, after execution of said draft, data obtained from the resulting contract in said database said data organized into fields comprising: draft contract status, contract identifier, contract type, effective date, and expiration date; and a field comprising obligation type, status, owner or due date; and said database capable of generating reports based on said data, said reports obtainable through search of said fields, and said database being selectively accessible by a plurality of users; and
retrieving from said database a report of outstanding financial obligations.

### Claim 30 (depends on 29)

The method of claim 29 further comprising the step of analyzing said report to determine which, if any, of said obligations should be acted upon.

### Claim 31 (depends on 30)

The method of claim 30 further comprising the step of deciding, based on said analysis, whether to act upon one or more of said financial obligations.

### Claim 32 (depends on 30)

The method of claim 30 further comprising the step of either making or receiving payment based on said analysis.

### Claim 33 (depends on 32)

The method of claim 32 further comprising the step of updating said database to reflect said payment or receipt of payment.

### Claim 34 (depends on 29)

The method of claim 29 wherein the draft is selected from the group consisting of: draft confidentiality contracts, draft software licenses, draft technology licenses and draft service contracts.

### Claim 35 (depends on 29)

The method of claim 29 wherein the draft is a draft license contract.

### Claim 36 (depends on 29)

The method of claim 29 wherein the report indicates obligation status, type, owner and/or due date.

### Claim 37 (depends on 29)

The method of claim 29 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 38 (depends on 29)

The method of claim 29 wherein said contract database is used to indicate whether a contract document is being reviewed and/or executed.

### Claim 39 (depends on 29)

The method of claim 29 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit and/or user's authority level.

### Claim 40 (depends on 29)

The method of claim 29 wherein said database further comprises standard contract forms or clauses.

### Claim 41 (depends on 29)

The method of claim 29 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 42 (depends on 29)

The method of claim 29 further comprising the step of obtaining an invoice generated automatically from said database.

### Claim 43

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract having one or more obligations;
routing the draft contract to one or more for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
storing, after contract execution, data obtained from the resulting contract in said database, said data organized into fields comprising: draft contract status, contract identifier, contract type, effective date, and expiration date;
and a field comprising obligation type, status, owner or due date; and said system capable of generating reports based on said database, said reports obtainable through search of said fields, and said database being selectively accessible by a plurality of users;
retrieving from said database a report of outstanding obligations;
analyzing said report to determine which, if any, of said obligations should be acted upon;
taking action based on said analysis; and
updating said database to reflect said action.

### Claim 44 (depends on 43)

The method of claim 43 wherein the draft is selected from the group consisting of: draft confidentiality contracts, draft software licenses, draft technology licenses and draft service contracts.

### Claim 45 (depends on 43)

The method of claim 43 wherein the draft is a draft license.

### Claim 46 (depends on 43)

The method of claim 43 wherein said obligations are financial obligations.

### Claim 47 (depends on 43)

The method of claim 43 wherein the report is organized by obligation status, type, owner and/or due date.

### Claim 48 (depends on 43)

The method of claim 43 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 49 (depends on 43)

The method of claim 43 wherein said contract database is used to indicate whether a contract document is being reviewed and/or executed.

### Claim 50 (depends on 43)

The method of claim 43 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit and/or user's authority level.

### Claim 51 (depends on 43)

The method of claim 43 wherein said database further comprises standard contract forms or clauses.

### Claim 52 (depends on 43)

The method of claim 43 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 53 (depends on 43)

The method of claim 43 further comprising the step of obtaining an invoice generated automatically from said database.

### Claim 54

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract proposing to obligate a party to make one or more payments;
routing the draft contract to one or more parties for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
storing, after execution of said draft, data obtained from the resulting contract in said database, said data organized into fields comprising: draft contract status, contract identifier, contract type, effective date, expiration date and payment due date; and said database capable of generating reports based on said data, said reports obtainable through search of said fields, and said database being selectively accessible by a plurality of users;
retrieving from said database a list of payments due;
obtaining from said database an invoice or payment letter wherein said invoice or payment letter is generated automatically using said stored data; and
sending the invoice or payment letter.

### Claim 55 (depends on 54)

The method of claim 54 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 56 (depends on 54)

The method of claim 54 wherein said contract database is used to indicate whether a contract document is being reviewed and/or executed.

### Claim 57 (depends on 54)

The method of claim 54 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit, and/or user's authority level.

### Claim 58 (depends on 54)

The method of claim 54 wherein said database further comprises standard contract forms or clauses.

### Claim 59 (depends on 54)

The method of claim 54 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 60 (depends on 54)

The method of claim 54 further comprising the step of updating the database to reflect that payment was made or to reflect receipt of payment.

### Claim 61 (depends on 54)

The method of claim 54 wherein the draft is a draft license contract.

### Claim 62

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract proposing to obligate a party to make one or more payments;
routing the draft contract to one or more parties for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
storing, after execution of said draft, data obtained from the resulting contract in said database, said data comprising payment data;
generating from said database a list of payments due;
obtaining from said database an invoice or payment letter wherein said invoice or payment letter is generated automatically using the data stored in said database;
sending the invoice or payment letter; and
updating the database to reflect that payment was made or to reflect receipt of payment.

### Claim 63 (depends on 62)

The method of claim 62 wherein said data is organized into fields comprising: draft contract status, contract identifier, contract type, effective date, expiration date and payment due date; and said database capable of generating reports based on said data, said reports obtainable through search of said fields, and said database being selectively accessible by a plurality of users.

### Claim 64 (depends on 62)

The method of claim 62 wherein said contract database is used to indicate whether a contract document is being reviewed and/or executed.

### Claim 65 (depends on 62)

The method of claim 62 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 66 (depends on 62)

The method of claim 62 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit, and/or user's authority level.

### Claim 67 (depends on 62)

The method of claim 62 wherein said database further comprises standard contract forms or clauses.

### Claim 68 (depends on 62)

The method of claim 62 wherein said database further comprises standard invoice forms or standard correspondence.

### Claim 69

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract proposing to obligate a party to make one or more payments;
routing the draft contract to one or more parties for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
obtaining from the database an indication as to whether the draft is being reviewed and/or executed.
storing, after execution of said draft, data obtained from the resulting contract in said database, said data comprising payment triggering event data; and
generating from said database a report of payment triggering events.

### Claim 70 (depends on 69)

The method of claim 69 further comprising the step of analyzing said report and deciding to make payment based on said analysis.

### Claim 71 (depends on 69)

The method of claim 69 further comprising the step of obtaining from said database a payment letter generated automatically using the data stored in said database.

### Claim 72 (depends on 69)

The method of claim 69 further comprising the steps of sending the payment letter and updating the database to reflect that payment was made.

### Claim 73 (depends on 69)

The method of claim 69 wherein said data is organized into multiple fields comprising: draft contract status, contract identifier, contract type, effective date, expiration date and payment due date; and said database capable of generating reports based on said data, said reports obtainable through search of said fields, and said database being selectively accessible by a plurality of users.

### Claim 74 (depends on 73)

The method of claim 73 wherein said fields further comprise at least one of those selected from the group consisting of: obligation triggering event, royalty basis, invoice due date, payment due date, payment received date, payment schedule, tax, currency and invoice status.

### Claim 75 (depends on 69)

The method of claim 69 wherein a user's access to one or more parts of said database is based on contract type, user's job description, user's title, user's business unit, and/or user's authority level.

### Claim 76

A contract generation and administration method comprising:
drafting a contract or receiving a draft contract, said draft contract proposing to obligate a party to make one or more payments;
routing the draft contract to one or more parties for review and/or execution;
storing review and/or execution data in a single contract database comprising data obtained from multiple contract documents;
obtaining from the database an indication as to whether the draft is being reviewed and/or executed. storing, after execution of said draft, data obtained from the resulting contract in said database, said data comprising payment triggering event data;
generating from said database a report of payment triggering events;
analyzing the report to determine whether payment should be made;
making payment; and
updating the database to reflect that payment was made.
