US2010185548A1PendingUtilityA1

Systems and Methods for Facilitating Agreement Generation and Negotiation via an Agreement Modeling System

51
Assignee: WILCE SCOT DPriority: Jul 27, 2001Filed: Mar 29, 2010Published: Jul 22, 2010
Est. expiryJul 27, 2021(expired)· nominal 20-yr term from priority
G06Q 40/03G06Q 40/04G06Q 40/00G06Q 40/02Y10S707/99933Y10S707/99935G06F 40/166G06Q 50/188Y10S707/99934
51
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Systems and methods are provided to facilitate generation and/or negotiation of an agreement document via an agreement modeling system. According to one embodiment, agreement information associated with an agreement between a party and a counter-party is determined. An agreement document is generated in accordance with the agreement information, and it is automatically arranged for the agreement document to be received by the party and/or the counter-party. For example, an agreement modeling system controller may transmit the agreement document to the counter-party via an electronic mail address.

Claims

exact text as granted — not AI-modified
1 .- 29 . (canceled) 
     
     
         30 . A processor-implemented method of generating an agreement document associated with an agreement between a user and a counter-party, comprising:
 receiving into a storage element agreement data from a user;   determining one or more scopes associated with the agreement data;   initializing a scope stack by placing the determined one or more scopes in the scope stack;   dynamically evaluating the scope stack via a processor using an agreement model based on rules and expressions to generate a result; and   generating an agreement document based on the agreement data and the generated result.   
     
     
         31 . The method of  claim 30 , further comprising automatically transmitting the generated agreement document to the counter-party via a counter-party communication address contained in the agreement data. 
     
     
         32 . The method of  claim 30 , wherein the agreement data is associated with one or more financial transactions related to a plurality of financial products and instruments. 
     
     
         33 . The method of  claim 32 , further comprising determining an agreement type based on the agreement data associated with the one or more financial transactions related to a plurality of financial products and instruments. 
     
     
         34 . The method of  claim 33 , further comprising determining one or more agreement terms based on the agreement type. 
     
     
         35 . The method of  claim 30 , wherein the one or more scopes include an agreement scope, a document scope, a fact set scope and a work flow scope. 
     
     
         36 . The method of  claim 30 , wherein the generating is performed via at least one of: covered product matrix information retrieved from a database; a pre-stored default transaction term; information received from a user of an agreement modeling system; information received from a satellite system; and information received from a legacy agreement system. 
     
     
         37 . The method of  claim 31 , wherein the agreement document is a preliminary agreement document. 
     
     
         38 . The method of  claim 37 , further comprising:
 receiving a revised preliminary agreement document from the counter-party;   processing and reconciling the revised preliminary agreement document;   generating a final agreement document in accordance with the reconciliation; and   transmitting the generated final agreement document to the counter-party via the counter-party communication address contained in the agreement data.   
     
     
         39 . A processor-implemented method of generating an agreement document associated with an agreement between a user and a counter-party, comprising:
 receiving into a storage element agreement data from a user;   querying an agreement data store to determine whether a new agreement is required;   determining at least one of an agreement scope, a document scope and a fact set scope associated with the agreement data;   initializing a scope stack by placing the determined at least one scope in the scope stack;   dynamically evaluating the scope stack via a processor using an agreement model based on rules and expressions to generate a result; and   generating an agreement document based on the agreement data and the generated result.   
     
     
         40 . A system for generating an agreement document associated with an agreement between a user and a counter-party, comprising:
 a memory;   a processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues further instructions to:
 receive agreement data from a user; 
 determine one or more scopes associated with the agreement data; 
 initialize a scope stack by placing the determined one or more scopes in the scope stack; 
 dynamically evaluate the scope stack using an agreement model based on rules and expressions to generate a result; and 
 generate an agreement document based on the agreement data and the generated result. 
   
     
     
         41 . The system of  claim 40 , wherein the processor issues further instructions to automatically transmit the generated agreement document to the counter-party via a counter-party communication address contained in the agreement data. 
     
     
         42 . The system of  claim 40 , wherein the agreement data is associated with one or more financial transactions related to a plurality of financial products and instruments. 
     
     
         43 . The system of  claim 42 , wherein the processor issues further instructions to determine an agreement type based on the agreement data associated with the one or more financial transactions related to a plurality of financial products and instruments. 
     
     
         44 . The system of  claim 43 , wherein the processor issues further instructions to determine one or more agreement terms based on the agreement type. 
     
     
         45 . The system of  claim 40 , wherein the one or more scopes include an agreement scope, a document scope, a fact set scope and a work flow scope. 
     
     
         46 . The system of  claim 40 , wherein the generating is performed via at least one of: covered product matrix information retrieved from a database; a pre-stored default transaction term; information received from a user of an agreement modeling system; information received from a satellite system; and information received from a legacy agreement system. 
     
     
         47 . The system of  claim 41 , wherein the agreement document is a preliminary agreement document. 
     
     
         48 . The system of  claim 47 , wherein the processor issues further instructions to:
 receive a revised preliminary agreement document from the counter-party;   process and reconciling the revised preliminary agreement document;   generate a final agreement document in accordance with the reconciliation; and   transmit the generated final agreement document to the counter-party via the counter-party communication address contained in the agreement data.   
     
     
         49 . A system for generating an agreement document associated with an agreement between a user and a counter-party, comprising:
 a memory;   a processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues further instructions to:
 receive into a storage element agreement data from a user; 
 query an agreement data store to determine whether a new agreement is required; 
 determine at least one of an agreement scope, a document scope and a fact set scope associated with the agreement data; 
 initialize a scope stack by placing the determined at least one scope in the scope stack; 
 dynamically evaluate the scope stack using an agreement model based on rules and expressions to generate a result; and 
 generate an agreement document based on the agreement data and the generated result.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.