# Patent

## Title
Systems for exchanging an obligation

## Abstract

A system for exchanging an obligation between parties where the exchange is administered by a supervisory institution that ensures real-time settling of obligations between parties by updating shadow records in real-time and instructing one or more exchange institutions to effect, from time to time, the exchange of obligations in accounts maintained external to the supervisory institution. Updates to the exchange institution accounts may reflect the net obligations of parties over a nominated period of time. The role of the supervisory institution is to ensure that obligations are only settled where parties have sufficient balance in their shadow records to complete the transaction. Obligations that can be exchanged include, but are not limited to: shares in financial or physical assets, participation rights in wagers, national or synthetic currencies, exchange settlement account deposits, taxation account deposits, and deposits of financial instruments or precious metals.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application is a Continuation of application Ser. No. 09/567,507, filed May 9, 2000 now U.S. Pat. No. 6,912,510, which is a Continuation of U.S. application Ser. No. 08/870,691, filed Jun. 6, 1997, now issued as U.S. Pat. No. 6,134,536, which is a Continuation-In-Part of U.S. application Ser. No. 08/070,136, filed May 28, 1993, now issued as U.S. Pat. No. 5,970,479; said U.S. application Ser. No. 08/870,691 is also a continuation-in-part to International Application No. PCT/AU95/00827 filed Dec. 7, 1995, which designated the U.S. Both application Ser. No. 08/070,136 and PCT/AU95/00827 are incorporated by reference in their entireties herein.


TECHNICAL FIELD
This invention relates to methods and apparatus, including electrical computers and data processing systems applied to financial matters and risk management. In particular, the invention is concerned with the management of risk relating to specified, yet unknown, future events.
Background Art
Individuals and enterprises are continually exposed to risk because of future events beyond their control. The outcome of those events can either positively or negatively impact on their wellbeing.
Individuals and enterprises should generally prefer not to face exposure to the possibility of adverse consequences, regardless of their perception of the likelihood of such events occurring. It is in their interest to consider foregoing ‘resources’ they currently possess if doing so would reduce the possibility of being so greatly exposed to future outcomes.
Risk can take many forms in view of the large range and type of future events which might result in adverse consequences. Risk can be categorised, in one instance, as ‘economic’ in nature. Phenomena that constitute economic risk include: commodity prices, currency exchange rates, interest rates, property prices, share prices, inflation rates, company performance, and market event based indices.
Another characterisation of risk concerns ‘technical’ phenomena. This can include things like the breakdown of an electricity generation plant, aircraft engine failure, and the damage to, or failure of, orbiting telecommunications satellites. The outcomes for each of these phenomena will be adverse for the users and/or supplier.
Other forms of risk defy ready characterisation, such as weather-based (viz., rain damage or lightning strike), or other natural occurrences (viz., earthquakes or iceberg collision with sea-going vessels).
There are also less tangible risks associated with, for example, the emission of atmospheric pollutants or the disposal of intractable toxic wastes, in the sense that the future consequences are unknown, save that there is a notion, based on current information, that they could be adverse.
The capability to manage risk is more important today than it was in the past and is likely to become ever-more important into the future, because there is an ever increasing exposure to a wider generic range of future phenomena beyond the control of individuals or enterprises. There is also a wider feasible range of possible future events, and greater uncertainty about the likelihood of occurrence, associated with any single future phenomenon viz., an increasing volatility.
It is also thought that individuals are now more risk-averse in recessionary times, when there are fewer available discretionary resources to trade-off to protect themselves from such adverse future events.
In the prior art, individuals and enterprises faced with ‘technical’ risk have hedged against future outcomes by mechanisms such as the adoption of quality assurance practices, warranties, increased research and development activity (and associated intellectual property rights such as patents, utility models and registered designs), the purchase of modernised plant and equipment, and improved inventory, occupational health and safety and employer/employee relations practices.
Consider a manufacturer of, say, integrated circuits (ICs), which has many clients wishing to purchase its ICs. The demand may result in a delay in delivery due to limited manufacturing capacity, thereby requiring advance production scheduling for orders already in-hand. Typically, the manufacturer will give a warranty to a purchaser as to measurable performance criteria for its ICs; if a batch does not perform to the specified criteria, the manufacturer is required by contract to replace that batch. That is, a purchaser may have no interest in obtaining monetary compensation for the poor quality ICs, as the purchaser needs the components for their own products. In that case, the ‘consideration’ the warranty makes is the priority scheduling of a substitute batch of that type of IC, possibly displacing other scheduled production runs, or deferring delivery to another purchaser.
Such contractual arrangements are piece-meal in nature, and can only be struck between the manufacturer and each individual purchaser. They also leave the manufacturer exposed to claims from other customers whose orders are delayed by the re-scheduling. The manufacturer has no convenient mechanism available to it to hedge against such claims, perhaps by way of reserving production rights with another manufacturer, in lieu of unavailability of their own manufacturing facility.
In the face of such ‘economic’ risk, it is known for individuals and enterprises to hedge against adverse outcomes by indirect means such as self-insurance, and directly by means such as futures contracts, forward contracts, and swaps.
There are disadvantages or limitations associated with such available economic risk management mechanisms. Particularly, they provide, at best, only indirect approaches to dealing with the risk management needs. The available mechanisms are relatively expensive, and provide limited phenomenon coverage, and therefore cannot meet the requirements of the party seeking to hedge against such wide-ranging future risk. The infrastructure and pay-out costs associated with switching between, say, a commodities market and a stock market are often prohibitive for entities small and large alike. As a consequence, entities find themselves saddled with obligations they have little control over and cannot escape.
In respect of the “less tangible” forms of risk, an example in the prior art of a form of management of that risk is that of ‘pollution rights’ sold by the U.S. Environmental Protection Agency (EPA) in March 1993 for the atmospheric emission of sulphur dioxide. This was done by an auction of “allowances” permitting the release into the atmosphere. By the year 1995, any company or organisation emitting sulphur dioxide in the U.S. without enough allowances to cover their total emissions will face prosecution. This means polluters must either buy further allowances, or else modify or replace their plant and equipment to reduce these emissions. The EPA will regulate the total number of allowances able to be obtained. The existing allowances have already become a valuable tradeable ‘property’ as between sulphur dioxide emitters, that is, even before the time when no further allowances will be able to be purchased.
Management techniques for the “less tangible” forms of risk are in their infancy. The existing forms indicate an emerging demand for systems and methods to enable effective management.
Specific examples in the prior art of patents relating to methods and apparatus which deal with various forms of risk management include British Patent No. 2 180 380, in the name of Merrill Lynch Pierce Fenner and Smith Incorporated, directed to an Automated Securities Trading Apparatus (corresponding to U.S. Pat. No. 4,674,004, and further related to U.S. Pat. Nos. 4,346,442 and 4,376,978). Other examples include U.S. Pat. No. 4,739,478 assigned to Lazard Freres and Co., directed to Methods and Apparatus for Restructuring Debt Obligations, U.S. Pat. No. 4,751,640 assigned to Citibank, N.A., directed to An Automated Investment System, and U.S. Pat. Nos. 4,752,877, 4,722,055, and 4,839,804 assigned to College Savings Bank directed to Methods and Apparatus for Funding Future Liability of Uncertain Cost.
The present invention comes about in view of the shortcomings of existing risk management mechanisms, and the perceived increasing importance of the management of risk relating to specified, yet unknown, future events.
In this sense, the invention is directed to something having economic value to individuals, enterprises and societies as a whole. Methods and apparatus that provide for the management of risk offer material advantages by, for example, minimising adverse future outcomes, providing both a form of compensation in the event of adverse future outcomes, and forms of risk management not otherwise supported or available in the prior art, and thus have value in the field of economic endeavour.
DISCLOSURE OF THE INVENTION
The invention encompasses methods and apparatus enabling the management of risk relating to specified, yet unknown, future events by enabling entities (parties) to reduce their exposure to specified risks by constructing compensatory claim contract orders on yet-to-be-identified counter-parties, being contingent on the occurrence of the specified future events. The entities submit such orders to a ‘system’ which seeks to price and match the most appropriate counter-party, whereupon matched contracts are appropriately processed through to their maturity.
Therefore, the invention enables parties to manage perceived risk in respect of known, yet non-predictable, possible future events. These future events may relate to measurable phenomena whose outcome is verifiable, and cannot be materially influenced by any other entity having a stake in that outcome.
The ability to price and match risk aversion contracts essentially comes about because of the nature of risk itself. Any number of people will each have differing views as to the likelihood of an outcome of some future event. This means that when each person is required to independently assess a range of outcomes for a specified future date, there almost always will be a variance in those assessments. Thus it is possible to match these expectations as between parties to form a contract. The potential counter-parties to an offered contract have the motivation of taking up an opportunity to exploit differing views of future outcomes to their advantage, either for some gain or, again, as a form of risk management.
It is important that the assessments as to future outcomes of events are made independently of any other party who could be a counter-party to a contract. The nature of the pricing and matching, therefore, is totally different to conventional negotiation or bidding as between parties.
The present invention enables entities to better manage risk, as they are able to think more explicity about possible future events beyond their control which they perceive will have adverse consequences for them. They will have the capacity to utilise existing resources to reduce exposure to a specific risk, and have access to a generally available mechanism by which they can explicity trade-off existing assets for increased certainty about the future. They are also free to decide upon the degree to which they should make such trade-offs, and to actually effect and subsequently manage such trade-offs in a simple and low cost manner.
Risk management contract formulation comprising the steps of order placement, pricing and matching. An ordering party initiates contract formulation by submitting an order that relates to a specified phenomenon that has a range of possible outcomes relative to a future date of maturity. The ordering party specifies elemental entitlements (pay-outs) due at maturity relative to the phenomenon's actual outcome, and a maximum consideration to be paid to a counterparty on matching of a contract. Independently, potential counterparties have submitted registering data based on their assessed probability of each possible outcome at maturity for the phenomenon in question. From this counterparty registering data, a data processing system then seeks to price each counterparty against the ordering party's specified entitlement. Broadly speaking, this involves multiplying each of the elemental ordering party entitlements with the corresponding counterparty probability and summing the results to derive counter considerations. The counter considerations must fall below the ordering party's maximum consideration for there to be the possibility of a match. Most usually a match will be made between the ordering party and the counterparty having the lowest counter consideration.
The ordering stakeholders and counter-party stakeholders can be considered to be contract buyers and contract sellers respectively. The entitlement for each outcome can be in the form of ‘money’ payoffs (both positive and negative) at maturity of a matched contract, or can be other types of compensation, possibly in the form of goods, services, promises, credits or warrants. The consideration, whether buyer specified or seller calculated, can again be in the nature of a premium or payments, or can relate to other ‘non-money’ forms of property or obligations, typically transferable when a contract is matched, although possibly deferable, until, and potentially beyond, the time of maturity.
In the period between the match of a contract and maturity the various buyers, sellers and other contract stakeholders can review any contract to which they are a party and seek to trade that contract to other parties by the pricing and matching procedure, or variations on the pricing and matching procedure. They would tend to do so if their view of the future outcome of the phenomenon, being the subject of the contract, had changed markedly, or as a means to minimise expected losses if some unforseen adverse trend in the present day outcome of the phenomenon has occurred. As well as trading existing contracts, further contracts can be offered to ‘lay off’ or avert risk. Stakeholder parties can build up a portfolio of matched contracts and offered contracts, which are continually traded to obtain the best possible position at any time, and that position can be continually reviewed with time.
It is further possible for offered contracts to be based on the difference between phenomena, and so manage perceived risk as between the phenomena. Elemental contract phenomena can therefore be developed to meet the most particular needs of buyers and sellers, thus creating great flexibility.
In most instances the date of maturity will be predetermined by a ‘product sponsor’ stakeholder, who otherwise cannot be a buyer or seller of contracts they sponsor. Even so, it is conceivable that the date of maturity can be tied to a specified time from the instant a contract is matched. This may be appropriate where the time of maturity is in the near future, in which case offered contracts could otherwise remain unmatched following initial offer even up until the time of maturity.
Other stakeholders have executive roles in administration, guaranteeing the performance of buyers and seller, regulation, supervision and so on. In this way the number and types of buyers and sellers that can be considered in pricing and matching offered contracts can be controlled.
The invention also encompasses apparatus and method dealing with the handling of contracts at maturity, and specifically the transfer of entitlement.
In another preferred form, the invention provides that the phenomenon for an offered contract is specified such that the elemental entitlements for the range of outcomes are the same for each outcome. In mathematical terms this corresponds to a shape in an x-y cartesian coordinate system where entitlement value (y) with respect to the outcome values (x) is a flat line. Put another way, the entitlement vs. outcome (y,x) shape has zero gradient (Δy/Δx). This type of entitlement/outcome shape can be thought of as a form of lending (if the entitlement is positive, or borrowing if the entitlement is negative), in that the ordering party wishes to make the consideration available for lending now, having the expectation of receiving a known (non-contingent) entitlement in the future. Contract pricing and matching with a counterparty can proceed as described above.
Embodiments of the invention significantly advance the state-of-the-art of formulating and trading risk management contracts. Essentially, this is achieved by a computing/telecommunications infrastructure that is capable of being accessed worldwide by any enterprise/individual having access to a computer and telephone network. Furthermore, a virtually infinite number and range of risk typescan be accommodated. One embodiment presents itself in a form that assists users in making consideration-entitlement (insurance-type) trade-off decisions and provides a blind yet transparent price-discovery and trading process. Through its capability to create special case lending/borrowing and exchange products, end users are also provided with a low-cost mechanism for pricing and acquiring these products without the involvement of traditional intermediaries.
The invention also encompasses apparatus and method dealing with the handling of contracts at maturity, and specifically the transfer of entitlement. Therefore, in accordance with a further aspect of the invention, there is disclosed a method of exchanging obligations as between parties, each party holding a credit record and a debit record with an exchange institution, the credit records and debit records for exchange of predetermined obligations, the method comprising the steps of: (a) creating a shadow credit record and debit record for each party to be held independently from the exchange institutions by a supervisory institution; (b) obtaining from each exchange institution a start-of-day balance for each shadow credit record and debit record; (c) for every transaction resulting in an exchange obligation, the supervisory institution adjusts each respective party's shadow credit record or debit record, allowing only those transactions that do not result in the value of the shadow debit record being less than the value of the shadow credit record at any time, each said adjustment taking place in chronological order; and (d) at the end-of-day, the supervisory institution instructing ones of the exchange institutions to exchange credits or debits to the credit record and debit record of the respective parties in accordance with the adjustments of the said permitted transactions, the credits and debits being irrevocable, time invariant obligations placed on the exchange institutions.



BRIEF DESCRIPTION OF THE DRAWINGS
A number of embodiments of the invention will now be described with reference to the accompanying drawings, in which:
FIG. 1 shows a block diagram of a generic ‘system’ embodying the invention;
FIG. 2a shows a schematic block diagram of an indicative hardware platform supporting the system of FIG. 1;
FIG. 2b is a schematic block diagram of an alternate hardware platform supporting the system of FIG. 1;
FIG. 3 shows a representation of INVENTCO and its main component parts;
FIG. 4 shows a block diagram of a subset of the components of an INVENTCO system's markets-depository (M-INVENTCO);
FIG. 5 shows a block diagram of the process components of a subset of one type of ‘market’ (termed CONTRACT APP) which can reside within M-INVENTCO;
FIG. 6 shows a timeline applicable to Example I;
FIG. 7 shows a timeline applicable to Example II;
FIGS. 8 to 16 show flow diagrams of the contract pricing and matching methodology;
FIG. 17 shows a timeline applicable to Example III; and
FIGS. 18 to 40 show flow diagrams of the first to ninth process components for a CONTRACT APP; and
FIG. 41 shows a timeline for Example IV;
FIG. 42 shows a timeline for Example V; and
FIGS. 43A to 82B show tables and charts associated with Examples I, II, III, IV, and V.



DETAILED DESCRIPTION OF A BEST MODE FOR CARRYING OUT THE INVENTION
1. Introduction
The description firstly discusses the relation of the various users (stakeholders) of the ‘system’, followed by a consideration of a hardware data processing platform and peripheral input/output devices by which stakeholders interact with each other and the system.
This is followed by a discussion of the scope of the ‘applications’ that can be supported by the system in relation to the various stakeholders, and the interrelation of component parts thereof.
Details as to software methodologies for implementation of the applications supported by the system are also described, including a number of worked examples relating to the formulation and trading of risk management contracts.
In the course of the detailed description reference is made to a number of non-conventional expressions and terminologies. For convenience, an explanation of these is listed in the Glossary hereinbelow.
2. ‘Systems’ Configurations
FIG. 1 shows a block diagram of a generic ‘system’ embodying the invention. The various stakeholders or parties to the system 10 each have access to a centralised processing unit 20. The processing units 20 can be constituted by one or more data processing apparatus, with each one thereof providing access for any one or more of the various stakeholders to applications software supported by the system 10, as all the processing units would be interconnected. Access to the one or more data processing apparatus is controlled by a generic form of communications co-ordination and security processing unit 25.
FIG. 1 also indicates that there are a number of types of stakeholder, and a number of individual stakeholders within each stakeholder type. The basic types of stakeholder are described as: applications promoters 11, product sponsors 12, product ordering parties (buyers) 13, potential product counter-parties (sellers) 14, counter-party guarantors 15, regulators 16, consideration/entitlement transfer (‘accounting’) entities 17, and miscellaneous parties 18. The detailed roles of each of these stakeholders will be subsequently described in greater detail at a later time. The number of types of stakeholder represented in FIG. 1 is typically the largest that will be supported by the system 10.
An embodiment of a computer system for the system 10 is shown in FIG. 2. The core of the system hardware is a collection of data processing units. In the embodiment described, the processing unit 20 comprises three inter-linked data processors 93, 97, 104, such as the Sun 670 MP manufactured by Sun Microsystems, Inc. of the USA. Each processing unit 93, 97, 104 runs operational system software, such as Sun Microsystems OS 4.1.2, as well as applications software. The applications software is, in part, written around the flow diagrams subsequently described in FIGS. 8 to 16, and FIGS. 18 to 40, and accesses, or otherwise creates, the data files as summarized in the section headed PROCESS 2 VARIABLES AND DATA FILES hereinbelow. The processor configuration shown in FIG. 1 represents a large system designed to handle the transactions of thousands of stakeholders, the input and output data generated by those stakeholders, and risk management contact pricing, matching and subsequent processing functions.
Each processing unit 93,97,104 is operably connected with it one or more mass data storage units 95,100,110 to store all data received from stakeholders, and other data relating to all other software operations generating or retrieving stored information. Suitable mass storage units are, for example, such as those commercially available from Sun Microsystems.
A number of communications controllers 80,84,87, forming the communications co-ordination and security processing unit 25, are coupled with the processing unit 20. These controllers effect communications between the processing units 93,97,104 and the various external hardware devices used by the stakeholders to communicate data or instructions to or from the processing units. The communications controllers are such as the Encore ANNEX II, the IBM AS/400 server or the CISCO Systems AGS+.
A large range of communications hardware products are supported, and collectively are referred to as the stakeholder input/output devices 70. One amongst many of the communication devices 70 are personal computers 51 and associated printers 52, which have communications connection with the communications controller 80 by means of a modem 50. There can also be an external host device 53, such as a mini or mainframe computer, again linked with the communications controller 80 by means of a modem 54. In other forms, communications can be established simply by means of a tone dialing telephone 56, which provides for the input of instructions or data by use of the tone dialing facility itself. In the alternative, a voice connection via an operator 75 can be effected by a conventional telephone 58. Both these external devices are shown connected with the communications controller 84. A further possibility is to have data transfer by means of a facsimile machine 65, in this case shown linked to the communications controller 87.
In all cases, users of the input devices are likely to be required to make use of system access password generation and encryption devices such as the Racal RG 500 Watchword Generator 66,67,68,69, (for personal use) and the Racal RG 1000, which is incorporated in a mainframe computer 53. The corresponding decoding units for these devices are incorporated in the communications controllers 80,84,87.
The generic processing unit 20 also includes a large number of ‘portable’ information recordal devices, such as printers, disc drives, and the like, which allow various forms of information to be printed or otherwise written to storage media to be transferable. This is particularly appropriate where confirmatory documentation of matched risk contracts is required to be produced, either for safekeeping as a hard copy record, else to be forwarded to any one or more of the stakeholders that are a party to each individual matched contract.
The generic system 10 shown in FIG. 1 encompasses many varied configurations, relating not only to the number and types of stakeholders, but also the ‘architectures’ realisable by the system hardware and software in combination. In that sense the arrangement shown in FIG. 2a is to be considered only as broadly indicative of one type of hardware configuration that may be required to put the invention into effect.
For example, FIG. 2b shows an alternative configuration that does not rely upon a centralised (hub) data processing unit, rather the necessary processing is performed locally at each stakeholder site 200n by means of distributed software.
The ‘virtual’ level of the system 10 is termed INVENTCO. INVENTCO is a collection of one or more potentially interrelated systems, as shown in FIG. 3. Each INVENTCO system (INVENTCO SYSTEM #1 . . . INVENTCO SYSTEM #N) enables the formulation and trading of a wide range of contractual obligations, including risk management contracts. The hardware configuration shown in FIG. 2, is to be understood both as a realisation for a single INVENTCO system, and equally can represent a number of INVENTCO SYSTEMS, where the processing unit 20 is common to all and supports a number of communications co-ordination and security units 25, others of which are not shown, together with associated external communications devices 70, also not shown.
While INVENTCO allows the formulation and trading of risk management contracts, it is also responsible for processing of such contracts through to, and including, their maturity, and in some respects, subsequent to maturity.
Where there are a number of INVENTCO systems, those systems may be inter-dependent or stand-alone in nature. If inter-dependent, INVENTCO (10) is responsible for transactions between those systems.
INVENTCO and all of its component parts can be legally or geographically domiciled in separate countries or states. The supra-national nature of INVENTCO enables the stakeholders to avail themselves of the risk management mechanisms independently of legal domicile or other such restrictions that are often a feature of some conventional risk management mechanisms, subject to meeting certain criteria regarding credit worthiness and such. Indeed, the legal domicile, location, ownership and participating stakeholders of INVENTCO, or any of the sub-systems, can be continually changing.
FIG. 3 further shows that each INVENTCO SYSTEM comprises an infrastructure component, termed I-INVENTCO, and a markets depository component M-INVENTCO. I-INVENTCO is concerned with coordination of communications and other security considerations, that part termed AXSCO, and also provides a network and general management system, termed VIRPRO. M-INVENTCO is a depository of authorised product-market (applications) software residing within INVENTCO under the authorisation of VIRPRO, and as distributed using I-INVENTCO.
One or more local or wide area telecommunication networks may link VIRPRO and M-INVENTCO to AXSCO, and thus to each other. In this way both VIRPRO and M-INVENTCO effectively reside around AXSCO.
AXSCO therefore comprises multiple, uniquely addressed communications controllers linked together in a number of possible ways. In one embodiment, AXSCO is represented by the communications co-ordination and security processing unit 25 shown in FIG. 2. The component hardware, such as the three controllers 80,84,87 shown in FIG. 2, typically are responsible for three types of operational applications. The first is in respect of time stamping data received from other parts of INVENTCO and data similarly transmitted to entities external of INVENTCO. The second is in respect of protecting the identity and/or location of entities within INVENTCO from one another, and from entities external to INVENTCO. The third is responsible for overall management of the routing of data received and to be transmitted within INVENTCO and to external entities thereto.
Referring now to FIG. 4, within M-INVENTCO reside different collections of system sponsored phenomena or ‘markets’, one collection of which is termed CONTRACT APPS. Each CONTRACT APP within the CONTRACT APPS ‘markets’ collection is essentially related to a specific type of risk management phenomenon. The purpose of individual CONTRACT APPS is two-fold. First, to effect the trading/exchange/transfer of risk management contracts (and derivatives of these transactions) between participating product ordering parties and counter-parties on terms acceptable to the parties involved, as well as to others within INVENTCO registered as having a legitimate interest in the nature, size and composition of these trades/exchanges/transfers. And second, to appropriately manage all matched/confirmed contracts through to their time of maturity.
Individual CONTRACT APPS are responsible for performing the above-described tasks according to the specific rules they embody, defined by their applicable stakeholders.
The role played by the various stakeholders to CONTRACT APPS, remembering that in many cases it would not be necessary to have the involvement of all the possible types of stakeholder, briefly stated is as follows:
(a) An application promoter is an entity having overall responsibility for the functioning of a CONTRACT APP, having being granted that responsibility by VIRPRO.
(b) A product sponsor is an entity which promotes and administers the rules of trading, and subsequent management of defined “products” selected for inclusion in a CONTRACT APP by its application promoter.
(c) An ordering party (buyer) is an entity seeking to acquire a CONTRACT APP product from a potential counter-party (seller).
(d) A counter-party (seller) is an entity potentially prepared to satisfy the CONTRACT APP product needs of an ordering party (buyer).
(e) A guarantor is an entity guaranteeing a seller's ability to settle or meet obligations as a result of a CONTRACT APP effected match.
(f) Regulators are entities overseeing the on-going performance of all other stakeholders involved in a CONTRACT APP, and especially guarantors.
(g) Consideration/entitlement transfer (‘accounting’) entities are those parties with which all other CONTRACT APP stakeholders maintain ‘accounts’ to transfer required considerations/entitlements to or from each other.
(h) Other miscellaneous parties are those having some other defined stake in the functioning of a CONTRACT APP. In any implementation of the system, multiple numbers of each form of stakeholder are accommodated. A detailed consideration of the nature of CONTRACT APPS and the types of stakeholders to a CONTRACT APP is given in the section headed CONTRACT APPS hereinbelow.
As shown in FIG. 5, any one CONTRACT APP consists of a cluster of nine (and potentially more, or fewer) specific processes, these include:
(a) a process handling file administration and updating tasks supporting all other processes (termed Process 1);
(b) a process handling the receipt and processing of “primary” risk aversion contract transactions (termed Process 2);
(c) a process handling the receipt and processing of “secondary” risk aversion contract transactions (termed Process 3);
(d) a process handling the receipt and processing of “derivative-primary” risk aversion contract transactions (termed Process 4);
(e) a process handling the receipt and processing of “derivative-secondary” risk aversion contract transactions (termed Process 5);
(f) a process handling the “back office” management of all four types of risk aversion contract transactions, and transactions handled by Processes 7 to 9 (termed Process 6);
(g) a process handling non-CONTRACT APP-transaction related consideration, entitlement, and other “payment” obligation transfers between stakeholders (termed Process 7);
(h) a process handling CONTRACT APP (and authorised other INVENTCO) stakeholder access to specialist systems to assist the stakeholder concerned to decide how best to interface with a defined element of INVENTCO (termed Process 8); and
(i) a process handling CONTRACT APP (and authorised other INVENTCO) stakeholder access to a range of INVENTCO-facilitated “value added services” (termed Process 9).
A detailed discussion of the nine CONTRACT APP processes given in the section headed DESCRIPTION OF CONTRACT APP PROCESSES hereinbelow.
All these processes collectively access multiple data files and multiple records within these files. A description of the variables and data files used by Process 2, a key component process of a CONTRACT APP, is provided in the section headed PROCESS 2 VARIABLES AND DATA FILES hereinbelow.
The foregoing description identifies the essential inter-reaction between the hardware platform and the applications computer software run thereon.
A first example of the life-cycle of a risk management contract will now be described. A further detailed discussion of the nature of risk management contracts is given in the section headed RISK MANAGEMENT CONTRACTS hereinbelow.
3. Life Cycle of Risk Management Contract: Example I
The first example of a risk management contract describes a contract to manage risk associated with faults in microprocessors. In summary, the example shows how the system could enable one party, such as a supplier of military standard equipment seeking to avoid the adverse consequences of faulty microprocessors (specifically, 64-bit microprocessors) used in that equipment to make a contract with another party, such as a manufacturer of these microprocessors, who is seeking to exploit an opportunity based on their view of the future incidence of faults in the microprocessors they produce.
The specific offering is one which provides a contract ordering party with a specified contingent entitlement to “exclusive production warrants” (XPWs). That is, warrants providing the holder with priority access to a specified quantity of replacement and additional microprocessors sourced, immediately, from a defined, different, guaranteed high-quality, production line available to the supplier in consideration of payment of a money amount. The XPW entitlement is contingent on the value, at contract maturity date, of a percentage index of the proportion of 64-bit microprocessors shipped by the manufacturer, during a specified prior period, which are subsequently determined to be faulty to a defined degree. The defined degree, in this case, is the microprocessor being fault-free, as determined by successful completion of self-tests.
In this example, the relevant key stakeholders are: an application promoter (Demdata Inc); various product sponsors (the relevant one for the example being Demdata Inc itself); various primary product ordering parties (the relevant one for the example being Denisons); a single potential counterparty (Demdata Inc again); and an application regulator (the Department of Defence).
The timeline depicting the steps in the contract from the first step, Application Specification, to the final step, Contract Settlement, is shown in FIG. 6. FIGS. 43A–50B are eight detailed explanatory charts supporting FIG. 6. They should be read together with the following description.
Looking at the first step in the timeline (Application Specification) in conjunction with FIGS. 43A and 43B, it can be seen that Demdata Inc. established a Contract APP (Application ID 100) on 92.02.10.17.00.00 (that is, in inverse order, 5 pm on Feb. 10, 1992) to deal with defect liability management. Application ID 100 supports a range of products (Applicable Product ID's 1200–1250).
Looking at the second step in the timeline (Product Specification) in conjunction with FIGS. 44A and 44B, it can be seen that Demdata was also Product Sponsor of Product 1210 at the same time (92.02.10.17.00.00). This Product relates to the market termed: Factory Output Quality Indices, and to the sub-market termed 64-bit Microprocessor Fault Tolerance Index. The maturity date for Product 1210 is 95.02.10.17.00.00.00. The consideration for a specific contract involving Product 1210 is in the form of money (commercial bank deposits denominated in Australian dollars). The entitlement is in the form of Exclusive Product Warrants (XPWs); these entitle the contract ordering party to priority access over the forward production capacity of a defined, guaranteed-high-quality, 64-bit microprocessor production line. Product 1210 specifies a range of 0% to 100% in 2% increments in respect of the sub-market outcomes.
Looking at the third step in the timeline (Potential Counterparty Product Pricing Specifications), it can be found that Demdata is acting as the sole potential counterparty for forthcoming primary product orders dealing with Product 1210. At this point in the timeline (93.07.01.14.00.00.00), 17 months after the specification of Product 1210, Demdata has currently-specified parameters for pricing potentially forthcoming orders for the product.
Looking at the fourth step in the timeline (Primary Order Specification) in conjunction with FIGS. 45A and 45B, it can be seen that an Ordering party, Denisons, is seeking a contract (from the offering party, Demdata) in Product 1210 at that time (93.07.01.14.25.30.00). FIGS. 45A and 45B show the specific “pay-off” parameters that Denisons has defined for the contract it is seeking at this time, including a maximum acceptable contract consideration (premium) amount of 32,000 (denominated in commercial bank, Australian dollars).
Looking at the fifth step in the timeline (Order Specification Pricing) in conjunction with FIGS. 46A and 46B, it can be seen that Demdata (using the specified pricing parameters set at (93.07.01.14.00.00.00) prices the Denison order 93.07.01.15.26.40.00. Demdata's pricing parameters indicate that their appropriate Defined Circumstances ID for Denisons is 14. As is shown, this ID in turn implies a Commission Rate of 1.10%, a Discount Rate of 9.90%, a particular set of Component product prices and a particular set of Assessed Probabilities of Occurrence over the range of feasible product values (outcomes).
The Contract Bid Price is calculated automatically by the application software in the following manner: The ordering party-specified desired contingent entitlement amounts, i.e. the “registered data”, (covering the feasible product definition value range) are multiplied by the potential counterparty-specified component product prices (which will rarely add to “1” because each counterparty is endeavouring to ‘game’ potential ordering parties in different ways) to yield the corresponding number of implied contingent entitlement amounts. When added together, these figures sum to (34.110), where the brackets signify a negative value. This figure represents an expected future counterparty-entitlement payout amount (as at the designated contract maturity date of 95.02.10.17.00.00). The present day value of this figure, calculated using the specified discount rate of 9.90% per annum, is 29,220. To this amount is added the potential counterparty's desired flat commission amount of 1.10%, yielding a contract Bid Price (in the consideration/entitlement denomination of the product, commercial bank-denominated Australian dollars) of 29,540. No exchange rates are applicable in this case, because the ordering party, Denisons, is not seeking to deal in a consideration or entitlement denomination different to the denominations formally specified for the product. Demdata's parameters calculate that a consideration bid price of 29,540 will yield them a base margin on the contract of 3,180 (again denominated in commercial bank, Australian dollars).
This margin amount is calculated in the following manner: The ordering party-specified desired contingent entitlement amounts (covering the feasible product definition value range) are multiplied by the potential counterparty-specified assessed probabilities of occurrence to yield a corresponding number of net contingent entitlement valuation amounts. When added together, these sum to (30.770). This amount represents an expected future counterparty-entitlement loss-on the contract (as at the designated contract maturity date of 95.02.10.17.00.00). The present value of this amount, calculated using the specified discount rate of 9.90% per annum, is 26,360. Thus, (ignoring for this example the margin Demdata may gain from using, in some manner, the consideration amount of 29,540 through to the time the contract expires, and various transaction fees) the margin Demdata can expect from entering into this contract with Denisons is their calculated present-value indifference price of 29,540 less their calculated present-value expected loss on the contract of 26,360 (or 3,180).
The amounts in the last two rows of the table of FIGS. 46A and 46B are used for checking that this contract, if entered into by Demdata, will not result in them violating any self imposed portfolio valuation or composition limits. This notion is explained in detail in Example III.
Looking at the sixth step in the timeline (Order Matching), it can be found that Demdata's contract bid price of 29,540 is below Denison's specified maximum consideration price of 32,000, leading to a matching of the order at 93.07.01.14.29.10.00.
The seventh step in the timeline (Order/Contract Confirmation) can be seen to take place twelve minutes later at 93.07.01.14.38.50.00, after the system has determined that Denisons is able to (and then does) immediately pay the required consideration funds amount of 29,540 to Demdata.
Looking at the eighth step in the timeline (Contract Valuation) in conjunction with FIGS. 47A and 47B, it can be seen that a contract valuation report for Denisons was published not much longer than one hour after confirmation of the contract, that is, at 93.07.01.16.00.00.00. As can be seen, the market estimate of the future product value of the 64BMFT Index at this moment is 38 (with a standard deviation of 4), which implies that this contract has an expected future value of 29,330 XPWs (with a standard deviation of 6,213).
On FIGS. 48A and 48B it can be seen the equivalent report for Demdata Inc. of their expected future entitlement payout is identical to Denisons' expected future entitlement receipt (ignoring future fee payments which may be netted against these payments/receipts). The above-described market estimate of the future product value is determined by the system applying a defined composite of contract-counterparty assessed probabilities of occurrence figures drawn from the collection of all like contracts recently matched/confirmed by the system.
The ninth step in the timeline (Contract Valuation) refers to a contract valuation report published for Denisons sixteen months later, at 94.11.15.10.00.00.00 (see FIGS. 49A and 49B). As can be seen, the market estimate of the future product value of the 64 BMFT Index at this moment is 58 (with a standard deviation of 5), which implies that this contract now has an expected future value of 42,160 XPWs (with a standard deviation of 6,209). This is an increase in expected future value of 12,830 XPWs for Denisons since the former valuation date/time.
The tenth step in the timeline, Contract Maturity, refers to the actual determination of the product value at time of maturity, 95.02.10.17.00.00.00. As can be seen on FIGS. 50A and 50B, this product value of the 64 BMFT Index was specified by Demdata (as Product Sponsor) to be 74, implying a contract value of 100,660 XPWs to Denisons and a corresponding obligation on Demdata. The amount of 74 represents the percentage of 64-bit microprocessors shipped by Demdata, during a specified period some time before the designated contract maturity date, which are subsequently determined (possibly by the application regulator, The Department of Defence) to be faulty.
The eleventh step in the timeline involves the formal assignment of 100,660 XPWs by Demdata to Denisons (ignoring possible fee payments by one or both parties).
4. Life Cycle of Risk Management Contract: Example II
The second example describes a risk management contract associated with the utilisation of telecommunications carrying capacity. In summary, the example shows how the system could enable one party (a telecommunications carrier) seeking to avoid the adverse consequences of under and over-committing their call carrying capacity between specified points (say, between the two cities, New York and Boston) to make a contract with another party (say, another telecommunications carrier with call carrying capacity between the same two cities) similarly prepared to hedge against the consequences of this occurring.
The specific offering is one which provides a contract ordering party with a specified contingent entitlement to transmission time units between the hours 1200–1800 daily on the NY-Boston link within a defined future period (termed, Prime TTU's) upon assignment by the ordering party—to the counterparty—of a calculated consideration amount of Prime TTUs on the ordering party's own NY-Boston line within another defined future period (these defined TTUs may or may not be convertible to TTUs on other city links). The TTU entitlement is contingent on the value, at contract maturity date, of the log of the difference between the ordering party's utilisation of the counterparty's network and the counterparty's utilisation of the ordering party's network, during a specified prior period ending on the contract maturity date.
In this example, the relevant key stakeholders are: an application promoter (Newcom Inc); various product sponsors (the relevant one for the example being Newcom Inc itself); various primary product ordering parties (the relevant one for the example being Basstel Co.); two potential counterparties (Tasnet and Aarcom); and an application regulator (ITT).
The timeline depicting the steps in the contract from the first step, Application Specification, to the final step, Contract Settlement, is shown in FIG. 7. FIGS. 51A–59B are nine detailed explanatory charts supporting FIG. 7. They should be read together with the following description.
Looking at the first step in the timeline (Application Specification) in conjunction with FIGS. 51A and 51B, it can be seen that Newcom Inc. established a Contract APP (Application ID 001) on 93.11.01.17.00.00 (that is, 5 pm on Nov. 1, 1993) to deal with hardware capacity management. Application ID 001 supports a range of products (Applicable Product ID's 2001–2020).
Looking at the second step in the timeline (Product Specification) in conjunction with FIGS. 52A and 52B, it can be seen that Newcom Inc. was also Product Sponsor of Product 2001 at the same time (93.11.01.17.00.00). This Product relates to the market termed Telecommunications Carrying Capacity and to the sub-market termed Prime TTUs. The maturity date for Product 2001 is 96.11.01.17.00.00.00. The consideration for a specific contract involving Product 2001 is in the form of “Ordering Party TTUs”. The entitlement is in the form of “Counterparty TTUs”; these entitle the contract ordering party to “transmission time units between the hours 1200–1800 daily on the NY-Boston link (within a defined future period)”. The feasible values of PRIME TTUs are normalized in the range of −1.0 to +1.0, respectively signifying the proportionate utilization of respective networks as between the parties to a contract.
Looking at the third step in the timeline (Potential Counterparty Product Pricing Specifications), one can find two other carriers, Tasnet and Aarcom, acting as potential counterparties for forthcoming primary product orders dealing with Product 2001. At this point in the timeline (94.06.01.14.00.00.00), 7 months after the specification of Product 2001, both Tasnet and Aarcom have currently-specified parameters for pricing potentially forthcoming orders for the product.
Looking at the fourth step in the timeline (Primary Order Specification) in conjunction with FIGS. 53A and 53B, it can be seen that an Ordering Party, Basstel Co., is seeking a contract, from an offering party, in Product 2001 at that time (94.06.01.14.25.30.00). FIGS. 53A and 53B show the specific parameters (entitlements) that Basstel Co. has defined for the contract it is seeking at this time, including a maximum acceptable contract consideration amount of 58,000 (denominated in its own TTUs).
Looking at the fifth step in the timeline (Order Specification Pricing) in conjunction with FIGS. 54A and 54B, it can be seen that Tasnet (using the specified pricing parameters set at 94.06.01.14.00.00.00) prices the Basstel Co. order at 94.06.01.14.26.40.00. Tasnet's pricing parameters indicate that their appropriate Defined Circumstances ID for Basstel Co. is 8. As is shown, this ID in turn implies a Commission Rate of 1.00%, a Discount Rate of 9.90% per annum, a particular set of Component product prices and a particular set of Assessed Probabilities of Occurrence. In a similar process to that described for Example 1, this results in a Contract Bid Price of 55,180 (denominated in Basstel Co. TTUs), which Tasnet's parameters calculate will yield them a base margin on the contract of 10,760 (again denominated in Basstel Co. TTUs).
Still looking at the fifth step in the timeline, in conjunction with FIGS. 55A and 55B, it can be seen that Aarcom (again using the specified pricing parameters set at 94.06.01.14.00.00.00) also prices the Basstel Co. order at 94.06.01.14.26.40.00. Aarcom's pricing parameters indicate that their appropriate Defined Circumstances ID for Basstel Co. is 9. As is shown, this ID in turn implies a Commission Rate of 0.90%, a Discount Rate of 8.50% per annum, a particular set of Component product prices and a particular set of Assessed Probabilities of Occurrence. This results in a Contract Bid Price of 55,390 (denominated in Basstel Co. TTUs), which Aarcom's parameters calculate will yield them a base margin on the contract of 9,430 (again denominated in Basstel Co. TTUs).
Looking at the sixth step in the timeline (Order Matching) it can be found that Tasnet's price bid of 55,180 is below Aarcom's bid of 55,390 and, in turn, that the 55,180 amount is below Basstel Co.'s specified maximum consideration price of 58,000. This leads to a formal matching of Basstel Co,'s order by Tasnet at 94.06.01.14.29.10.00.
The seventh step in the timeline (Order/Contract Confirmation) can be seen to take place nearly ten seconds later at 94.06.01.14.38.50.00, after the system has determined that Basstel Co. is able to (and then does) immediately assign the required consideration amount of 55,180 TTUs to Tasnet.
Looking at the eighth step in the timeline (Contract Valuation) in conjunction with FIGS. 56A and 56B, one can see a contract valuation report for Basstel Co. published about two hours after confirmation of the contract, that is, at 94.06.01.16.00.00.00. As can be seen, the market estimate of the future product value of the log of the difference between Basstel Co.'s utilization of Tasnet's network and Tasnet's utilization of Basstel Co.'s network (during a specified prior period ending on the contract maturity date) at this moment is (0.150) (with a standard deviation of 0.023), which implies that this contract has an expected future value of 54,236 Tasnet TTUs (with a standard deviation of 9,207). On FIGS. 57A and 57B one can see in the equivalent report for Tasnet that their required expected future entitlement payout is identical to Basstel Co.'s expected future entitlement receipt (ignoring future fee payments which may be netted against these payments/receipts).
The ninth step in the timeline (Contract Valuation) refers to a contract valuation report published for Basstel Co. five months later, at 94.11.22. 10.00.00.00 (see FIGS. 58A and 58B). As can be seen, the market estimate of the future product value of the log of the difference between Basstel Co.'s utilization of Tasnet's network and Tasnet's utilization of Basstel Co.'s network (during a specified prior period ending on the contract maturity date) at this moment is (0.400) (with a standard deviation of 0.010), which implies that this contract now has an expected future value of 350,181 Tasnet TTUs (with a standard deviation of 74,200). This is an increase in expected future value of 295,945 TTUs for Basstel Co. since the former valuation date/time.
The tenth step in the timeline (Contract Maturity) refers to the actual determination of the product value at time of maturity, 96.11.01.17.00.00.00. As can be seen on FIGS. 59A and 59B, this product value of TTU's was specified by Newcom Inc (as Product Sponsor) to be (0.400), unchanged from the prior valuation date/time, implying a contract value of 368,340 Tasnet TTUs to Basstel Co. and a corresponding obligation on Tasnet. The amount is higher than the prior valuation figure due to the actual determination figure being naturally without a standard deviation element.
The eleventh step in the timeline involves the formal assignment of the 368,340 TTUs by Tasnet to Basstel Co. (ignoring possible fee payments by one or both parties).
5. Primary Product Order Processing
Before describing the third, and most detailed, example, consideration will be given to the ‘core’ product (contact) ordering, pricing and matching processes. Note that expressions such as (PORD NEW) represent file names.
The flow charts in FIGS. 8 to 16 depict the processing flow of the matching system for primary product orders submitted by ordering party stakeholders to a CONTRACT APP, where this APP is based upon: an EV-CE counterparty pricing regime (assuming paid consideration amounts do not yield an income stream in their own right); a sequential order matching process; consideration/entitlement value dates which are immediately after a product sponsor-designated date/time; and matching rules which do three things: First, identify, for each ordering party's order, a counterparty offering the lowest price bid for an order, subject to this price being at or below the specified maximum price the ordering party has indicated it is prepared to pay. Second, accommodate portfolio expected loss constraints on an ‘equivalent maturity date products’, ‘same-month maturity products’, and ‘all-products’ basis. And third, apply the above-described matching rules on a pre-tax basis, with partial matching of product orders, and without conditional order matching rules.
As shown in FIG. 8, starting at block 610, and proceeding to block 625, the system determines which set of orders to process, authorises these orders, matches them with counterparties where possible, and then confirms them. As shown in blocks 1010 to 1070 in FIG. 9, the system holds newly submitted orders (PORD NEW), and all previously submitted, but as yet unmatched, orders which are defined as queued orders (PORD QUEUE). Parameters and algorithms can be implemented to give the system the ability to determine whether new or queued orders are to be processed at any time. For example, a simplistic algorithm would be to alternate between PORD NEW and PORD QUEUE one order at a time. Another example would be to load queued orders only when there is a change in the counterparty parameters. Test 1020 checks the decision made in block 1010.
For new orders, the system moves to block 1030. Details of the next recorded new order are loaded from the PORD NEW master file (block 1040). The order data fields include: the ordering party identification (BID); the ordering party's own reference (BREF); the product identification (PID) specified by the ordering party; the entitlement “payoff” function type (PAYFUNC); the parameters for the entitlement “pay off” function (PAYPARAM); a “deal type” identifier (DTID); the anonymous and manual deal identifiers (OANON and OMANUAL); the order retention time limit (RET LIM); the maximum consideration the ordering party is prepared to pay (MAXCONSID); the number of the account from which the consideration is to be “paid” (ACC CONSID); and the number of the account to which any entitlement “pay off” amount is to be paid (ACC ENTITL). With this information set, the system's next step is to authorise the order. This occurs at block 1050.
Order Authorisation
Blocks 1100 to 1162 in FIG. 10 provide an expansion of block 1050. Starting at block 1100 the order is assigned a unique identification, which is set in the order data field OID. Before verifying the order, additional information is required by the system. At block 1110, details of the product (order data field PID) are loaded from the master file PPRODUCT (block 1120). The information includes the product maturity date (PMAT); the product consideration/entitlement denomination (PC/ED); the product currency denomination (PCUR) and national currency denomination (PNCUR); and the product limits and parameters (PMIN, PMAX, and PSTEP). The test 1130 checks that the order parameters are consistent with the master file parameters implied by the defined product identification (PID). Orders which fail this test are rejected at block 1140, with details of these orders being stored in the master file PORD REJ (block 1150). In turn, the ordering party is informed of this event (block 1160). Processing then returns to the start of the flow chart (block 1010), ready to load the next order. When an order is authorised, processing continues at block 640.
In the case of a queued order being loaded (block 1060), the order fields are set using the details stored in the queue file PORD QUEUE (block 1070). This data is a combination of new order data (as described in block 1030) and the data loaded/set when the order was originally verified (block 1110). Authorised order processing continues with the order matching process at block 640.
Order Matching
Blocks 1200 to 1616 in FIGS. 11 to 15 provide an explanation of block 640. Orders have retention time limits, stored in the order variable RET LIM. Test 1200 checks that the order retention time has not expired. If it has, the order is rejected at block 1210, with the order details copied to the rejected order file (PORD REJ). The ordering party is then informed of the rejection at block 1230, and processing returns to the main loop via connector “A”. If the order is still valid, the order matching process proceeds. The aim now is to find a suitable counterparty (or counterparties) who “prices” the ordering party's “entitlement function” within the limits set by the ordering party. Starting at block 1240, the matching process described is one which seeks to identify, for each ordering party's order, a counterparty offering the lowest “price bid” for an order subject to this price being at or below the specified maximum “price” the ordering party has indicated it is prepared to pay.
Blocks 1300 to 1370 in FIG. 12 provide an explanation of block 1240. The first step is to narrow down a group of counterparties prepared to at least deal with the ordering party. This is described as obtaining the available counterparty short list. First the counterparty short list is wiped (block 1300). Next, the order data fields BID (ordering part identification) and PID (product identification) are used to search the PDEAL LIST master file (block 1320) for all counterparties prepared to consider dealing with the ordering party in the specified product. Any stakeholders who have set a MANUAL or ANON flag are also loaded. For each counterparty selected, SID is set to the corresponding identification. Test 1330 commences a loop which allows every counterparty available to be dealt with in turn. For any currently selected counterparty (with identification set in SID), the data flow proceeds to test 1365. Where the order data field OANON has been set by the ordering party and some stakeholder requires manual confirmation (MANUAL (SID)), the current potential counterparty is not included in the short list. Likewise if the ordering party set OMANUAL and some other stakeholder required anonymity (ANON (SID)). In both cases, data flow returns to test 1330. Otherwise, flow continues at block 1335. At this point, the system determines the applicable “defined circumstances” for the order. It uses the order data fields currently loaded and parameters set in the PSEL DC masterfile (block 1336) to determine this. At block 1340, pricing parameters including consideration/entitlement exchange rates (if applicable), commission rates, and discount rates are selected from the PSEL PRICE master file (block 1350). Using the “defined circumstances” identification (set in DCID) all potential counterparties can have different sets of pricing parameters specified based on any of the order data fields of each order. Test 1360 checks that all the necessary parameters have been found. It is possible that the counterparty, though prepared to deal with the ordering party, does not have a complete set of pricing parameters for the current order specifications. Such a counterparty is not included in the counterparty short list, and processing returns to test 1330. At block 1370, the counterparty is added to the counterparty short list by including the pricing details in the variables: PRICEFUNC(SID), CR(SID), DR(SID), C-C/EDXCHANG(SID), C-CXCHANG(SID), C-NCXCHANG(SID), E-C/EDEXCHANG(SID), E-CXCHANG(SID), E-NCXCHANG(SID), MANUAL(SID), and ANON(SID). Processing then returns to test 1330 where the next selected potential counterparty is dealt with. When all selected potential counterparties have been processed, program flow returns to block 1250. At this point a potential counterparty short list has been obtained.
Blocks 1400 to 1550 in FIGS. 13 and 14 depict block 1250 in more detail, where every potential counterparty has its price offer calculated, based on their individual pricing parameters, for the currently loaded order. At block 1400 a loop commences allowing each potential counterparty in the potential counterparty shortlist to be dealt with in turn. SID is set to the identification of the counterparty currently selected. Test 1410 checks whether any counterparties are left for processing. At block 1420, the potential counterparty's price bid is calculated. Blocks 1490 to 1550 describe this calculation in more detail. At block 1490 the variable, INDEX, is assigned the starting value of the product value range (PMIN). Also, “price” is initialised to zero. Test 1500 commences a loop, where every index point in the product range is traversed. Block 1520 calculates the pricing value returned by the potential counterparty's pricing function, PRICEFUNC, as stored in (PRICEFUNC(SID)), at the current index point, and stores the value in P1. Block 1530 determines the pay-off amount required by the ordering party at the current index point and stores this value in P2. At block 1540, the total price at the current index point is calculated by multiplying P1 by P2. This value is added to the running total stored in PRICE(SID). At block 1550, the index counter (INDEX) is incremented by the product step size (PSTEP), and flow returns to the test 1500. When the end of the product range has been reached (PMAX), flow proceeds to block 1510, where the calculated price bid is modified by the following calculation:

PRICE(SID)=PRICE(SID)*E-C/EDXCHANG(SID)*E-CXCHANG(SID)*E-NCXCHANG(SID).

Returning to block 1430, the price bid stored in PRICE(SID) will be in the applicable product's consideration/entitlement denomination, currency denomination, and national currency denomination. The following steps (block 1430–1470) determine and apply the applicable discount rate to the calculated price bid (currently in future value terms) to yield a price bid in present value terms. This is done as follows: At block 1430 the number of days to product maturity is determined. Block 1440 initialises the loop counter and discount rate divisor. For each day (or appropriate part thereof) between the current date/time and the product maturity date/time, the divisor is changed according to the formula (block 1460):

DIV=DIV*(1+((DR(SID)/100)/365))

At block 1470, the price bid is adjusted according to the formula:

PRICE(SID)=PRICE(SID)/DIV

Once the price bid in present value terms is known, the potential counterparty's defined commission is added to the price (block 1480). Given that CR(SID) is a percentage commission rate, the formula is:

PRICE(SID)=PRICE(SID)+((CR(SID)/100)*PRICE(SID))

When test 1410 confirms that every potential counterparty has been priced, program flow continues at 1255.
The test at 1255 checks whether the order was a “quote only” order. If so, flow continues at block 1256 where one or more of the counterparty bid prices are selected. At block 1230, the ordering party is informed of the pricing information gathered. If the order was not a quote order (that is, it was a real product order), an attempt is now made to identify a counterparty from the potential counterparty short list matching the requirements of the current order. This is done at block 1260. Blocks 1560 to 1616 in FIG. 15 describe this process in detail.
Starting at test 1560, a check is made to ensure the potential counterparty shortlist is not empty. If it is, no match is possible and flow continues at block 1612. At this point SID is assigned “0” to indicate that no counterparty was selected from the potential counterparty short list, before moving to block 1614 where the entire order (as no part was matched) is queued. When the list is not empty, program flow continues at block 1570, where the lowest priced counterparty is selected from the counterparty short list. This determination is done based upon each potential counterparty's bid price (PRICE(SID)), being converted to the consideration/entitlement type, currency, and national currency consideration “payment” denominations sought by the ordering party (that is, PRICE(SID)=PRICE(SID)*C-C/EDXCHANG(SID)*C-CXCHANG(SID)*C-NCXCHANG(SID)). The counterparty identification is stored in SID, and its price offer is stored in BPRICE. At block 1580, the following check is made:

BPRICE>MAXCONSID

If the selected price is greater than the ordering party's specified maximum consideration payment (MAXCONSID) limit, a match with the current potential counterparty is not deemed possible. This must also be true for any of the remaining counterparties in the counterparty short list. This part of the matching process returns without any potential counterparty in the short list having been selected for a match (block 1612). Otherwise, the current price is acceptable, and the process proceeds to attempt a match with the current selected counterparty.
The next step (block 1590), requires all the applicable contract, product, and portfolio absolute loss, expected loss, expected value limits, and maximum composition limits to be read from the PSEL LIMIT master file (block 1600) and stored in ALL1(SID), ALL2(SID), ELL1(SID), ELL2(SID), ELL3(SID), ELL4(SID), ELL5(SID), EVL1(SID), MC(SID) and MCC(SID). The current absolute and expected losses accumulated are also read and stored in CAL2(SID), CEL2(SID), CEL3(SID), CEL4(SID), and CEL5(SID).The ELFUNC(SID) and EVFUNC(SID) values are also set for use when calculating the expected loss and expected value for the current order. Block 1602 calculates the price of the order entitlement function using the counterparty product expected loss and expected value parameters ELFUNC(SID) and EVFUNC(SID). The order's expected loss is stored in EL(SID); the order's expected value is stored in EV(SID). The absolute loss function is also determined at block 1602 and it is stored in AL(SID). Proceeding to block 1604, the portion of the order which will not violate the counterparty limits is calculated. This check is made at test 1606. If no part of the order is matched, process flow continues at block 1608. The potential counterparty is removed from the counterparty shortlist.
If some portion of the order is matched with the current counterparty, processing continues at block 1610. Here the SID is set to the identification of the matching counterparty. The unmatched portion (if any) is stored at block 1614 as a new order in the PORD QUEUE masterfile (block 1616). Flow then returns to test 1261 in FIG. 1. When a match occurs, program flow returns to block 650. The matched order must now be confirmed by carrying out a number of additional steps, as shown in FIG. 16, blocks 1620 to 1641. If no match occurred, processing of the current order steps, and program flow returns to the beginning via connector “A”. The system is ready to load the next available order.
Matched Order Confirmation
For matched orders to become a contract, a number of additional actions are required. First, at test 1620, a check for manual authorisation is made. If required, program flow moves to block 1621 where authorisation requests are sent to the relevant stakeholders. Block 1623 then tests the replies for any rejections. If one or more rejections were received, program flow continues at block 1627 where the order is rejected. Otherwise, flow continues at 1624. Block 1624 effects the consideration payment by creating transactions in the payment shadow file (PAYACC SHADOW—block 1625). However, this may fail if the accounts specified do not exist or if at least the required consideration amount is shown not to be available. Test 1626 checks that “consideration payment” was effected successfully. If “consideration payment” fails, the matched order is rejected (block 1627), with details stored in the rejected order master file, PORD REJ (block 1628). The ordering party is then informed of this event at block 1640.
With successful payment, program flow proceeds to block 1630 where the counterparty's current accumulated absolute and expected loss figures are updated (masterfile PSEL LIMIT—block 1631). At block 1632, the order data field OPRICE is set to the price given by the counterparty PRICE(SID), and SPRICE set to the counterparty's identification, SID. At block 1634, the matched order is certified as confirmed, with full details recorded in the masterfile PORD CONF (block 1636). The next step, block 1638, reports details of the newly created contingent contract to all stakeholders concerned. Program flow then returns to the beginning, via connector “A”. The system is now ready to start processing the next order submitted by a specified ordering party.
6. Life Cycle of Risk Management Contract: Example III
The third example of a risk management contract describes a contract to manage risk associated with potential future movements in the value of a specified index of share prices (termed the PTSE 75 index). In summary, the example shows how the system could enable one party (such as an institutional fund manager) seeking to avoid the adverse consequences of a significant decline in the future value of the PTSE 75 index (specifically a decline by June 1996, relative to the assumed current (June 1991) value of the index) to make a contract with another, as-yet-unknown, party, such as another fund manager seeking to avoid the adverse consequences of a significant corresponding increase in PTSE 75 index value.
The specific offering is one which provides a contract ordering party with a specified contingent entitlement to a compensatory Australian dollar future payout upon payment of a calculated up-front consideration money amount by the ordering party to the as-yet-unknown counterparty. The future money entitlement is contingent on the value, at contract maturity date, of the independently-determined value of the PTSE 75 index.
In this example, the relevant key stakeholders are: an application promoter (BLC Inc); various product sponsors (the relevant one for the example being BLC Inc itself); various product ordering parties (the relevant ones for the example being Abbotts & Taylor and Shearer & Associates); various potential counterparties (the relevant ones for the example being Abrahamsons and Carpenters Inc); a counterparty guarantor (CNZ Banking Corporation); and an application regulator (the Pacific Central Bank).
The timeline depicting the steps in the contract from the first step (Application Specification) to the final step (Contract Settlement) is shown in FIG. 17. FIGS. 60A to 72B are thirteen detailed explanatory charts supporting FIG. 17. They should be read together with the following description.
Looking at the first step in the timeline (Application Specification) in conjunction with FIGS. 60A and 60B, it can be seen that BLC Inc established a Contract APP (Application ID 001) on 91.06.03.17.00.00 (that is, 5 pm on Jun. 3, 1991) to deal with economic risk management. Application ID 001 supports a range of products (Applicable Product ID's 10020–11400).
Looking at the second step in the timeline (Product Specification) in conjunction with FIGS. 61A and 61B, it can be seen that BLC Inc was also Product Sponsor of Product 10061 at the same time (91.06.03.17.00.00). This Product relates to the Market termed Stock Indices and to the Sub-market termed PTSE 75. The maturity date for Product 10061 is 94.06.03.17.00.00.00. The consideration for a specific contract involving Product 10061 is in the form of money (commercial bank deposits denominated in Australian dollars). The entitlement is also in the form of commercial bank deposits denominated in Australian dollars, payable (if necessary) immediately after the Product's specified maturity date/time.
Looking at the third step in the timeline (Potential Counterparty Product Pricing Specifications), one can find two entities, Abrahamsons and Carpenters Inc, acting as potential counterparties for forthcoming primary product orders dealing with Product 10061. At this point in the timeline (95.01.01.17.00.00.00), 19 months after the specification of Product 10061, both Abrahamsons and Carpenters Inc have currently-specified parameters for pricing potentially forthcoming orders for the product.
Looking at the fourth step in the timeline (Primary Order Specification), in conjunction with FIGS. 62A and 62B, it can be seen that an Ordering Party, Abbotts & Taylor, is seeking a contract, from an offering party, in Product 10061 at that time (95.01.01.17.37.06.00). FIGS. 62A and 62B show the specific parameters (entitlement) that Abbotts & Taylor has defined for the contract it is seeking at this time, including a maximum acceptable contract consideration amount of 54,000 (denominated in commercial bank, Australian dollars).
In order to provide a more detailed explanation of the following fifth to seventh steps in the timeline, selected processing block numbers from FIGS. 8–16 will be referred to in brackets as follows: “[ ]”.
Looking at the fifth step in the timeline (Order Specification Pricing) in conjunction with FIGS. 63A and 63B, it can be seen that Abrahamsons' specified pricing parameters, as set at 95.01.01.17.37.06.06 are used to price the Abbotts & Taylor order at 95.01.01.17.38.02.00. Abrahamsons' pricing parameters indicate that their appropriate Defined Circumstances ID for Abbotts & Taylor is 26. As is shown, this ID in turn implies a Commission Rate of 1.25%, a Discount Rate of 10.00% per annum, a particular set of Component product prices and a particular set of Assessed Probabilities of Occurrence. In a similar process to that described for Example 1, this results in a Contract Bid Price of 51,920 (denominated in commercial bank, Australian dollars), which Abrahamsons' parameters calculate will yield them a base margin on the contract of 4,580 (again denominated in commercial bank, Australian dollars).
Still looking at the fifth step in the timeline, in conjunction with FIGS. 64A and 64B, it can be seen that Carpenters Inc specified pricing parameters, as set at 95.01.01.17.37.06.00, are also used to price the Abbotts & Taylor order at 95.01.01.17.38.02.00. Carpenters Inc's pricing parameters indicate that their appropriate Defined Circumstances ID for Abbotts & Taylor is 17. As is shown, this ID in turn implies a Commission Rate of 1.30%, a Discount Rate of 9.80% per annum, a particular set of Component product prices and a particular set of Assessed Probabilities of Occurrence. This results in a Contract Bid Price of 53,050 (denominated in commercial bank, Australian dollars), which Carpenters Inc's parameters calculate will yield them a base margin on the contract of 5,610 (again denominated in commercial bank, Australian dollars).
Again, still looking at the fifth step in the timeline, in conjunction with FIGS. 65A and 65B, it can be seen that Abrahamsons' pricing-related parameters (also set at 95.01.01.17.37.06.00) for determining the acceptability of ordered-contracts on the basis of their absolute loss, expected loss, expected value, and maximum portfolio composition attributes are satisfied by Abbotts & Taylor's order. From Abrahamsons' perspective, this qualifies Abbotts & Taylor's order for inclusion in their product/contract portfolio, as long as Abrahamsons' consideration price bid turns out to be lower than Carpenters Inc's price bid, and, in turn, this bid is below the maximum consideration price that Abbotts & Taylor has specified, in its order specification (FIGS. 62A and 62B), it is prepared to pay.
Finally, still looking at the fifth step in the timeline, but now in conjunction with FIGS. 66A and 66B, it can be seen that Carpenters Inc's pricing-related parameters (set at 95.01.01. 17.37.06.00) for determining the acceptability of ordered-contract oil the basis of their absolute loss, expected loss, expected value, and maximum portfolio composition attributes are also satisfied by Abbotts & Taylor's order. Now, from Carpenters Inc's perspective, this qualifies Abbotts & Taylor's order for inclusion in their product/contract portfolio, in this case, as long as Carpenters Inc's consideration price bid turns out to be lower than Abrahamsons' price bid, and, in turn, this bid is below the maximum consideration price that Abbotts & Taylor has specified, in its order specification (FIGS. 62A and 62B), it is prepared to pay.
Looking at the sixth step in the timeline (Order Matching), it can be found that Abrahamsons' price bid of 51,920 is below Carpenters Inc's bid of 53,050 and, in turn, that the 51,920 amount is below Abbotts & Taylor's specified maximum consideration price of 54,000. This leads to a formal matching of Abbotts & Taylor's order by Abrahamsons' at 95.01.01.17.38.07.00 [1260].
The seventh step in the timeline (Order/Contract Confirmation) takes place five seconds later at 95.01.01.17.38.11.00, after the system has determined that Abbotts & Taylor is able to (and then does) immediately pay the required consideration funds amount of 51,920 to Abrahamsons [650].
Looking at the eighth step in the timeline (Contract Valuation) in conjunction with FIGS. 67A and 67B, one can see a contract valuation report for Abbotts & Taylor published nearly six hours after confirmation of the contract, that is, at 95.01.01.23.00.00.00. As can be seen, the market estimate of the future product value of the PTSE 75 Index at this moment is 1970 (with a standard deviation of 333), which implies that this contract has an expected future value of 53,000 commercial bank-denominated Australian dollars (with a standard deviation of 21,160). On FIGS. 68A and 68B one can see in the equivalent report for Abrahamsons that their required expected future entitlement payout is identical to Abbotts & Taylor's expected future entitlement receipt (ignoring future fee payments which may be netted against these payments/receipts).
The ninth step in the timeline (Secondary Order Specification), detailed on FIGS. 69A and 69B, occurs nearly six months after the above-described contract valuation event; that is, at 95.06.06.08.00.00.00. At this time, Abbotts & Taylor is seeking to sell its position in the contract which was matched/confirmed at 95.01.01.17.38.11.00 (and at that time assigned the Order ID of 9156515800 by the system) at a price better than 57,000. Shearer & Associates is prepared to pay 60,000 (commercial bank deposit-denominated Australian dollars) for this position. In all other respects the contract's attributes remain unchanged. On FIGS. 70A and 70B, the tenth step in the timeline, a contract sale is seen to have occurred at a price of 58,300, just below the above-described 60,000 upper limit purchase-price amount specified by Shearer & Associates. This amount is the current best estimate of the contract's expected future value, with the standard deviation of this expected future value calculated by the system, utilizing other recent transaction data, as being 10,610. Shearer & Associates has now formally taken the place of Abbotts & Taylor as a stakeholder to the contract.
The eleventh step in the timeline (Contract Valuation) refers to a contract valuation report published for Shearer & Associates seven months later, at 96.01.01.17.00.00.00 (see FIGS. 71A and 71B). As can be seen, the market estimate of the future product value of the PTSE 75 Index at this moment is 1800 (with a standard deviation of 283), which implies that this contract now has an expected future value of 162,360 commercial bank deposit-denominated Australian dollars (with a standard deviation of 35,160). This is an increase in expected future value of 104,060 for Shearer & Associates since the former valuation date/time. The above described market estimate of the future product value is determined by the system applying a defined composite of contract-counterparty assessed probabilities of occurrence figures drawn from the collection of all like contracts recently matched/confirmed by the system.
The twelfth step in the timeline (Contract Maturity) refers to the actual determination of the product value at time of maturity, 96.06.03.17.00.00.00. As can be seen on FIGS. 72A and 72B, this product value of the PTSE Index was specified by BLC Inc (as Product Sponsor) to be 1820, implying a contract value of 187,200 (commercial bank deposit-denominated Australian dollars) to Shearer & Associates, and a corresponding obligation on Abrahamsons. The figure of 1820 represents the actual value of the PTSE share price index at 96.06.03.17.00.00.00 as obtained by BLC Inc from the independently verifiable information source, the identity of which they would have disclosed at the time they first announced their sponsorship of trading in the PTSE 75 share index product.
The thirteenth step in the timeline involves the formal payment of 187,200 (commercial bank deposit-denominated Australian dollars) by Abrahamsons to Shearer & Associates (ignoring possible fee payments by one or both parties).
Life Cycle of Economic Management Contract: Example IV
This further example of a risk management contract is an extension of Example III. More particularly, however, it is a special case of the general case of Example III, in that for a particular phenomenon the same entitlement is specified by the ordering party for each of the possible outcomes. This is a case where X=1, α(X) is not applicable, β(X)=the specified non-contingent entitlement (constant), and γ(X)=11, where “11” denotes a mathematical shape that is a straightline with respect to the ‘outcome’ axis, drawn from a menu of such shapes. Put another way, the gradient of the graph of entitlement (y-axis) against outcome (x-axis) is zero.
The counterparty registering data remains the same as for Example III. It can be thought of as the scenario where the outcome is not of concern to the ordering party. When its future entitlement is positive, the contract, from the ordering party's view, is in the nature of a loan, in that the consideration is made available now for a future known entitlement. It is of course possible for the consideration and entitlement to be negative so that the nature of the contract from the ordering party's viewpoint is borrowing.
The example shows just this situation, in that one party (such as an institutional fund manager) seeks to avoid the adverse consequences of not having immediate possession of a defined resource (say, Australian dollars) by becoming a party to a contract with another, as-yet-unknown, party (such as another fund manager seeking to avoid the adverse consequences of being unable to adequately utilise the defined resource).
The specific contract offering is one which provides an ordering party with a specified non-contingent obligation (that is, a negative future entitlement) to make an Australian dollar future payout to the contract's counterparty upon that counterparty's payment of a calculated up-front consideration money amount to the ordering party.
Thus, for a given guaranteed entitlement payout amount by the ordering party to its counterparty on a contract's maturity date, the up-front consideration payment is essentially a function of two matters implicitly determined between the ordering party and the counterparty registering data:

    
    
        1. The discount (interest) rate applicable to the contract (this will itself be credit risk-free Australian dollar instruments with the same maturity date, plus a margin reflecting the counterparty's assessment of the likelihood of default by the ordering party in making their required future entitlement payment in Australian dollars);
        2. The counterparty's sought-after commission on the transaction.
    
    


Note that if, say, the contract entitlement is based in US dollars, the matter of the counterparty's defined forward Australian dollar/U.S. dollar exchange rate would also be relevant.
As noted, the relevant key stakeholders are the same as in Example III: an application promoter (BLC Inc); various product sponsors (the relevant one for the example being BLC Inc itself); various product ordering parties (the relevant ones for the example being Abbotts & Taylor and Shearer & Associates); various potential counterparties (the relevant ones for the example being Abrahamsons and Carpenters Inc); a counterparty guarantor (CNZ Banking Corporation); and an application regulator (the Pacific Central Bank).
A timeline depicting the steps in the contract from the first step, Application Specification, to the final step, Contract Settlement, is shown in FIG. 41 and further supported by FIGS. 73–77B.
Looking at the first step in the timeline, Application Specification' in conjunction with FIG. 73, we see that BLC Inc established a Contract APP (Application ID 001) on 91.06.03.17.00.00 (that is, 5 PM on Jun. 3, 1991) to deal with economic risk management. The application involves a pricing and matching objective function of: “minimize pre-tax consideration payment under an expected value (EV)/certainty equivalent (CE) value”. Note that a negative consideration payment is allowed.
Looking at the second step in the timeline, Product Specification, in conjunction with FIG. 74, we see that BLC Inc was also product sponsor of Product 10061 at the same time (91.06.03.17.00.00). This product relates again to the market of stock indices. The maturity date for Product 10061 is 96.06.03.17.00.00.00. The sub-market is the PTSE 75 stock index. The consideration for a specific contract involving Product 10061 is in the form of money (commercial bank deposits denominated in Australian dollars). The entitlement is also in the form of commercial bank deposits denominated in Australian dollars, payable immediately after the product's specified maturity date/time.
Looking at the third step in the timeline, Potential Counterparty Product Pricing Specifications, one can find two entities, Abrahamsons and Carpenters Inc, acting as potential counterparties for forthcoming primary product orders dealing with Product 10061. At this point in the timeline (95.01.01.17.00.00.00), 43 months after the specification of Product 10061, both Abrahamsons and Carpenters Inc have currently-specified parameters for pricing potentially forthcoming orders for the product.
Looking at the fourth step in the timeline, Primary Order Specification, in conjunction with FIG. 75, it can be seen that Abbotts & Taylor is seeking a contract in Product 10061 at that time (95.01.01.17.37.06.00). FIG. 75 shows the specific parameters that Abbotts & Taylor has defined for the contract it is seeking at this time, namely $A 83,830 for any feasible product value including a minimum acceptable contract consideration amount of ($A 55,000). The parentheses indicate that the consideration is negative. The calculated counter consideration (≧$A 55,000) will be paid by the counterparty to Abbotts & Taylor immediately after contract matching.
Looking at the fifth step in the timeline, Order Specification Pricing, in conjunction with FIGS. 76A and 76B, it can be seen that Abrahamsons (using the specified pricing parameters set at 95.01.01.17.37.06.00) prices the Abbotts & Taylor order at 95.01.01.17.38.02.00. Abrahamsons' pricing parameters, indicated by their defined circumstances ID of 31, require a commission rate of 1.25% and a discount rate of 10.00% pa. A particular set of component product prices together with a particular set of assessed probabilities of occurrence are specified. This results in a counter consideration of ($A 58,710), which Abrahamsons' parameters calculate will yield them a base margin on the contract of $A 1,980.
Still looking at the fifth step in the timeline, in conjunction with FIGS. 77A and 77B, it can be seen that Carpenters Inc (again using the specified pricing parameters set at 95.01.01.17.37.06.00) also prices the Abbotts & Taylor order at 95.01.01.17.38.02.00. Carpenters Inc's pricing parameters, indicated by their defined circumstances ID of 19, require a commission rate of 1.30% and a discount rate of 9.8% pa. A particular set of component product prices and a particular set of assessed probabilities of occurrence are specified. This results in a contract bid price of ($A 58,640), which Carpenters Inc's parameters calculate will yield them a base margin on the contract of $1,990.
Looking at the sixth step in the timeline, Primary Order Matching, it can be found that Abrahamsons' price bid of ($A 58,710) is above Carpenters Inc's bid of ($A 58,640) and above Abbotts & Taylor's specified minimum consideration price of ($A 55,000). This leads to a formal matching of Abbotts & Taylor's order by Abrahamsons at 95.01.01.17.38.07.00. Before the matching formally occurs, a check is made that absolute loss, expected loss, expected value and portfolio attribute limits are not violated.
The seventh step in the timeline, Contact Maturity, refers to the actual determination of the product value at time of maturity, 96.06.03.17.00.00.00.
The eighth step in the timeline involves the formal payment of $A 83,830 by Abbotts & Taylor to Abrahamsons.
The example just described can also be thought of as a case where the market is irrelevant, and therefore there is no minimum or maximum product definition value nor product step value. This equates to there being no future outcome, rather simply a known specified entitlement that is not dependent upon the outcome of any particular phenomenon. The mathematical representation of curves or lines no longer is relevant. The counterparty counter consideration thus becomes a function only of the discount rate, commission and (if applicable) entitlement exchange rate.
Life Cycle of Economic Management Contract: Example V
This embodiment relates to an economic management contract (based on a variation of Example IV) and describes the formulation of an immediate exchange contract involving an entitlement of a defined $US amount in return for a to-be-determined consideration denominated in commercial bank Australian dollars.
This example is a special case of the general case of Example II in that it is independent of the outcome of any particular phenomenon. It has only a single outcome for which a single entitlement is specified by the ordering party.
Unlike Example IV, however, this case also involves a unique notion of a contract maturity date/time. This is the notion of “as soon as possible after the date/time the transaction is originated by the ordering party”, implying an immediate exchange. That is, the date of maturity is now.
In this example, the offering is one which provides a contract ordering party with a specified non-contingent entitlement to receive its desired $US currency amount ($US 70,000) as soon as possible after the ordering party specifies it is prepared to immediately pay not more than $A 102,900 (as a consideration) in exchange for this US currency.
In this example, the relevant key stakeholders are: an application promoter (BLC Inc); various product sponsors (the relevant one for the example being BLC Inc itself), various product ordering parties (the relevant ones for the example being Abbotts & Taylor), various potential counterparties (the relevant ones for the example being Abrahamsons and Carpenters Inc), a counterparty guarantor (CNZ Banking Corporation) and an application regulator (the Pacific Central Bank).
The timeline depicting the steps in the contract from the first step, Application Specification, to the final step, Contract Settlement, is shown in FIG. 42, and are supported by FIGS. 78–82B.
Looking at the first step in the timeline, Application Specification, in conjunction with FIG. 78, we see that BLC Inc established a contract APP (Application ID 201) on 91.06.03.17.00.00 (that is, 5 pm on Jun. 3, 1991) to deal with economic risk management. The application involves a pricing and matching objective function of: “maximize pre-tax consideration/entitlement exchange rate”. Application ID 201 supports a range of products.
Looking at the second step in the timeline, Product Specification, in conjunction with FIG. 79, we see that BLC Inc was also product sponsor of Product 11099 at the same time (91.06.03.17.00.00). This product relates to the market of immediate exchange. The maturity date for Product 11099 is “as soon as possible after transaction initiation’. The consideration for a specific contract involving Product 11099 is commercial bank deposits denominated in Australian dollars. The entitlement is in the form of commercial bank deposits denominated in US dollars, payable immediately after the product's specified maturity date/time (that is, as soon as possible after transaction initiation).
Looking at the third step in the timeline, Potential Counterparty Product Pricing Specifications, two entities, Abrahamsons and Carpenters Inc, are potential counterparties for forthcoming primary product orders dealing with Product 11099. At this point in the timeline (92.06.03.15.00.00.00), 12 months after the specification of Product 11099, both Abrahamsons and Carpenters Inc have currently-specified parameters for pricing potentially forthcoming orders for the product.
Looking at the fourth step in the timeline, Primary Order Specification, in conjunction with FIG. 80, it can be seen that an ordering party, Abbotts & Taylor, is seeking a contract from an offering party in Product 11099 at that time (92.06.03.17.00.00.00). FIG. 80 shows the specific parameters that Abbotts & Taylor has defined for the contract it is seeking at this time, including a maximum exchange (consideration) amount of ($A 102,900) and a defined $US 70,000 entitlement.
Looking at the fifth step in the timeline, Order Specification Pricing, in conjunction with FIGS. 81A and 81B, it can be seen that the system determines that the counter consideration amount Abrahamsons judge to be ideal given their specified parameters is $A 94,500. This occurs at 92.06.03.17.38.02.00. Abrahamsons' pricing parameters specify an exchange rate of 0.75, a commission rate of 1.25% and a single assessed probability of occurrence of one (1) (discount rate and component product prices being irrelevant in this example). The counter consideration of $A 94,500 is lower than Abbotts & Taylor's specified maximum consideration amount of $A 102,900.
Still looking at the fifth step in the timeline, in conjunction with FIGS. 82A and 82B, the system determines that the counter consideration amount Carpenters Inc judge to be ideal given their specified parameters is $A 101,300. Carpenters Inc's pricing parameters imply an exchange rate of 0.70, a commission rate of 1.30% and a single assessed probability of occurrence of one (1) (discount rate and component product prices again being irrelevant).
Looking at the sixth step in the timeline, Order Matching, it can be found that the system assesses Abrahamsons' to be superior to that of Carpenter Inc and below Abbotts & Taylor's maximum consideration. This leads to a formal matching of Abbotts & Taylor's order by Abrahamsons' at 92.06.03.17.38.12.00. Matching coincides in time with maturity, and very shortly thereafter there is the transfer of $A 94,500 from Abrahamsons to Abbotts & Taylor and a corresponding transfer of $US 70,000 from Abrahamsons to Abbotts & Taylor. This then represent finalisation of the transaction, including all the transfers involved at the date/time of maturity of other contract types.
A further embodiment, relevant to each of the embodiments of Examples III to V above, involves the order pricing procedure as before, followed by a step of obligating the ordering party with the would-be matched counterparty for a period of time before the match is formally made. As before, the consideration can be payable immediately upon match or deferred for a time (even up until maturity), and the date of maturity can be at a future time from matching (or even immediately upon match). The period of obligation can be specified by the promoter stakeholder, and thus be known to the ordering party and the registering counterparties. The period of obligation thus enables parties to contract to future contingent contracts (in the case of Examples I and IV) or future exchange (in the case of Example V).
7. Description of Consideration/Entitlement Payment Process
The purpose of the CONTRACT APP consideration/entitlement (and related transactions) payment/receipt process is to effect debits and credits to INVENTCO stakeholder accounts, typically at maturity of a contract, with participating consideration/entitlement transfer (or exchange) entities, reflecting payment/receipt entitlements and obligations originated within INVENTCO. The process effects these payments/receipts in a two-stage process. First, by debiting/crediting, on a real-time basis, the relevant shadow records (in the data file PAYACC SHADOW) of the applicable stakeholder accounts with a participating consideration/entitlement transfer entity (C/E entity), external to INVENTCO, with which they maintain an account. And second, by periodically effecting, via existing and potential payment mechanisms, corresponding payment instructions to the payment entities concerned. Details of the above-described mechanism are as follows.
All INVENTCO stakeholders maintain (a minimum of) two special-purpose (net-credit balance only) accounts with (at least) one selected, VIRPRO authorised, C/E transfer entity. The purpose of special-purpose accounts is to ensure that only INVENTCO-initiated debits and credits are capable of being effected to the accounts. Thus, at any time the balance of each PAYACC SHADOW file account record should be equivalent to the true, but usually unknown, time-of-day balance of the actual account maintained by the C/E transfer entity.
The purpose of two accounts is to enable only credits to be effected through one account and only debits through another account. And the purpose of “net-credit balance only” accounts is to ensure that accumulated debits to the debits-only account never exceed the account opening balance plus accumulated credits to the credits-only account.
C/E transfer entities will typically be (but do not need to be) institutions of any/all of six types: public/private record-registries of various types; credit card companies (typically for retail transactions only); commercial banks; central banks; taxation authorities; and non-bank clearing houses and depositories.
The resources transferred by these entities may be of any type. However, most typically, they will be deposits appropriate for the entity concerned: With respect to public/private record-registries—entitlement deposits (including shares in financial or physical assets, participation rights in wagers, and so on). With respect to credit/debit card companies—normal card company deposits (denominated in national currencies or synthetic currencies (for example, SDRs)). With respect to commercial banks—normal bank deposits (denominated in national currencies or synthetic currencies (for example, SDRs)). With respect to central banks—exchange settlement account (or equivalent) deposits. With respect to taxation authorities—taxation account deposits. And with respect to non-bank clearing houses and depositories—deposits of financial instruments, precious metals and the like. CONTRACT APP potential counterparties will also effectively be C/E transfer entities, as will ordering party guarantors (external to INVENTCO) where they offer credit to product ordering parties. Also, some accounts will be trust accounts maintained on behalf of potential counterparties (and some product ordering parties) involved in applications requiring the periodic payment of collateral to independent third parties to serve as an additional security device.
Immediately after the completion of its daily—or more frequent—transaction processing, and their associated settlement functions, each C/E transfer entity electronically notifies the applicable CONTRACT APP of the “opening balances” of all the debit and credit INVENTCO accounts it maintains (At this stage, the debit account balance should be zero and the credit account balance should be greater than or equal to zero). Where an INVENTCO stakeholder has an overdraft or line-of-credit with its C/E transfer entity, the credit value of this will be reflected in the non-zero balance of its credit account at this time.
Upon receipt of the above-described notifications, the applicable CONTRACT APP updates/confirms its stakeholder shadow balances. Thus, at this point-in-time, all credit and debit shadow account balances should be equivalent to their actual debit and credit account balances.
Progressively throughout the day (where “day” here is likely to be different for each C/E transfer entity due to a combination of differences in the time-zone locations of payment entities in relation to the applicable CONTRACT APP, and the likely different account processing cycles of these entities), INVENTCO-stakeholder—authorised 15 debits and credits to INVENTCO stakeholder shadow accounts are effected on a real-time basis—debits to debit accounts and credits to credit accounts. At all times, the CONTRACT APP ensures that the cumulative debit balance of each stakeholder's debits account does not exceed the “opening balance” plus the cumulative credit balance of the stakeholder's credit account. Thus, at any time, for every INVENTCO stakeholder, the combination of each stakeholder's debit account and credit account will represent the “true”, net, time-of-day value of the stakeholder's two actual special-purpose accounts maintained external to INVENTCO.
Debits and credits to INVENTCO stakeholder accounts are effected according to strict rules and conditions, being different for credits and debits. Credits can be made to any INVENTCO stakeholder's credit account with its nominated C/E transfer entity by any other INVENTCO stakeholder for any reason. Naturally, as INVENTCO stakeholders will not know the account details of other stakeholders, such credits will be effected either automatically, according to information and rules known by the applicable CONTRACT APP, or semi-automatically by way of an INVENTCO stakeholder requesting from VIRPRO, as they need to do so, a credit-account number of the stakeholder to which they wish to transfer assets. This account number may only be valid for a nominated period and would not typically be the specified stakeholder's actual account number with its nominated consideration/entitlement transfer entity—it would only be a reference to an INVENTCO file containing this number.
On the other hand, debits can only be made to an INVENTCO stakeholder's debit account with its nominated C/E transfer entity by the stakeholder itself, and by other stakeholders explicitly granted this right by each stakeholder, subject to these other stakeholders exercising this right according to the rules and conditions specified for them.
Where an INVENTCO stakeholder seeks to initiate/authorise debits to its nominated account(s) on its own, this can only be done through the stakeholder satisfactorily completing the identification and security procedures set down by their C/E consideration/entitlement transfer entity (and reflected in VIRPRO-specified INVENTCO communication procedures). The type of procedure set down by all participating C/E transfer entities involves (at least) the following: First, the consideration/entitlement transfer entity supplying VIRPRO with a confidential file of account Pin numbers corresponding to each of its INVENTCO stakeholder debit accounts, and a similarly confidential “black box” which, by initiating any of a number of possible proprietary password request-response processes involving any one of its customers possessing the appropriate device(s), confirms that remote messages received from that customer, and processed by the “black box”, are authentic. Second, the consideration/entitlement transfer entity supplying their INVENTCO customers with a programmable smart card (or equivalent device) enabling each customer, remotely—via telephone or direct computer line, to unambiguously confirm their identity with their INVENTCO-maintained account, thereby having the capability to authorise debits to their account within predefined parameters concerning factors such as maximum transaction amounts, possible transaction types, account usage patterns and so on. Third, INVENTCO providing the mechanisms for direct, confidential, stakeholder communications with their C/E transfer entity shadow debit accounts, and the formal updating of these accounts, through non real-time processes, utilizing the unique time-stamped reference numbers created as/when stakeholders authorise access to their account records.
Where an INVENTCO stakeholder has authorised other INVENTCO stakeholders to initiate debits to (any of) its nominated account(s) according to a standing authority of some type, this can only be done through the authorised stakeholder itself satisfactorily completing the identification and security procedures set down by the authorisation-granting stakeholder's nominated C/E transfer entity (and reflected in VIRPRO-specified INVENTCO communication procedures). Once again, the type of procedure, set down by all participating C/E transfer entities in this respect, involves (at least) the following: First, the C/E transfer entity supplying VIRPRO with a confidential file of account Pin numbers corresponding to each of its INVENTCO stakeholder debit accounts and each other INVENTCO stakeholder which has been authorised to effect debits (within defined parameters) to these accounts. Second, the C/E transfer entity supplying VIRPRO with a similarly confidential black box which, by initiating any of a number of possible proprietary password request-response processes involving an entity nominated by any of its customers possessing the appropriate device(s), confirms that remote messages received from that authorised entity, and processed by the black box, are authentic. Third, the C/E transfer entity supplying their INVENTCO customers with a collection of programmable smart cards (or equivalent devices), for distribution to these authorised entities, enabling each authorised entity, remotely—via telephone or direct computer line—to unambiguously confirm their identity with the customer's PAYACC SHADOW account, thereby having the capability to authorise debits to this account (again, within predefined parameters concerning factors such as maximum transaction amounts, possible transaction types, account usage patterns and so on). And four, INVENTCO providing the mechanisms for direct, confidential, authorised stakeholder communications with a stakeholder's C/E transfer entity shadow debit account(s).
At the end of each C/E transfer entity's specified day (or part of a day), the applicable CONTRACT APP transfers (at least) two things to the entity: First, if required, a series of figures representing the exchange settlement (or equivalent) accounting entries it has or will communicate to the C/E transfer entity's appropriate clearing authority (for each of the applicable consideration/entitlement denomination, currency and national currency types of the payments/receipts involved) where these figures represent the balancing net debit or credit figure corresponding to the aggregation of all of the entity's INVENTCO customer transactions in the prior day. And second, a detailed file of all customer transactions effected during the day (corresponding, if required, to the above-described net figures). Upon their receipt of these transactions and summary figures, the C/E transfer entity then debits/credits each transaction to the appropriate actual customer accounts, enabling new “closing” account balances to be calculated (these “closing” balances should be exactly the same as the end-of-day balances communicated by the applicable CONTRACT APPS with it's file of customer transactions). In turn, these “closing balances” become the C/E transfer entity's account “opening balances” for the next day. The CONTRACT APPS notification process then repeats itself.
Where applicable, at days-end for the “clearing house” of clusters of like C/E transfer entities (for example, a national central bank), CONTRACT APP transfers netted exchange settlement accounting entries to the clearing houses concerned. These entries serve to “balance the individual customer account entries transferred to each associated C/E transfer entity individually.
8. Industrial Applicability
The invention has industrial application in the use of electrical computing devices and data communications. The apparatus and methods described allow the management of risk in an automated manner by means of programming of the computing devices. The types of events associated with the risk management apparatus and methodologies includes physical and technical phenomena, and therefore have value in the field of economic endeavour.
Glossary of Key Terms
Alpha (X)
The Ordering party-specified event value corresponding to the Xth future product event value contract entitlement payoff (payout) inflection point.
Application Promoter
An entity authorised by VIRPRO that specifies and administers defined rules and regulations underlying a defined CONTRACT APP—including the specific products offered for trading; categories of, and conditions of involvement, of stakeholders; nature of involvement and dispute resolution procedures of stakeholders.
Automatic/Manual Deal and No Deal Flags
Indicators notified by each stakeholder to CONTRACT APP specifying the manner in which that stakeholder wishes to deal with each other stakeholder.
AXSCO
A communications co-ordination and security system, linked to all stakeholders and component application.
Base Pricing Probabilities
The prices set by sellers for unit entitlement payoffs of a contract at each of its possible future index values denominated in the contract's formally specified consideration/entitlement, currency and national currency.
Beta (X)
The Ordering party-specified desired entitlement payoff (payout) amount in the desired currency denomination of contract entitlement payout (payoff) and national currency denomination of contract entitlement of payout (payoff) corresponding to the Xth event value inflection point.
Bilateral Obligations Netting Indicator
An indicator that individual ‘rolling’ net present values of future payment/receipt commitments to/from all pairs of participating stakeholders are to be netted.
Bilateral Payments Netting Indicator
An indicator that individual end-of-day gross payments/receipts to/from all pairs of participating INVENTCO stakeholders are to be netted.
Commission Rate
The minimum required percentage profit margin required by a Potential Counterparty above the “breakeven” bid price for an Ordering party purchase order.
Consideration/Entitlement Transfer Entity
An entity acceptable to VIRPRO and the Application Promoter, satisfying defined minimum standards of financial strength, credit standing and integrity, able to maintain Consideration/entitlement accounts on behalf of stakeholders and effect transfers of those assets as directed.
CONTRACT APP Stakeholder Types
Expected stakeholder types are Application Promoter, Product Sponsor, Product Ordering party, Counterparty, Counterparty-Guarantor, Regulator, Consideration/entitlement transfer Entities and Miscellaneous other parties.
Contract and Product “Absolute Loss” Limit
A value limit specified by a potential counterparty of the maximum absolute loss it is prepared to sustain on a contract/product irrespective of the assessment of the likelihood of any particular level of possible loss being incurred.
Contract and Product “Expected Loss” Limit
A value limit specified by a potential counterparty of the maximum expected loss it is prepared to sustain on a contract/product based on the counterparty's assessment of the likelihood of all levels of possible loss being incurred.
Contract Authorisation
A process of verifying that an Ordering Party product purchase order contains data appropriate to the product being sought and that the Ordering Party is accurately identified and credentialled.
Contract Collateralisation Indicator
A descriptor set by the Application Promoter specifying whether and on what basis, counterparties may be required to periodically transfer assets/monies (collateral) to an independent trust fund to ensure they will be able to meet their potential entitlement payoff obligations on the maturity date of a contract.
Contract Confirmation
The process of securing the positive agreement of all affected stakeholders to a purchase order, including acknowledgement by the relevant Consideration/entitlement transfer entity of the Ordering party'ability to pay the required product consideration and fees, either automatically or through manual approvals.
Contract Matching
See Ordering party/Potential counterparty matching process.
Contract Obligation
a. A binding commitment one entity (or group of entities) has to provide products or services or information to another entity (or group of entities) in exchange for an agreed quantity of other products, services or information.
b. A binding commitment all entities have to the network and general management system entity VIRPRO and thus to each other, to accept constraints on their activities imposed by other authorised on terms specified and agreed to by them as a condition of their participation in one or more of the component systems.
Contract Portfolio Netting
A terms used to describe the process of “setting-off” or “netting”, the future payment entitlement obligations between Ordering parties and Counterparties, either bi-laterally or multi-laterally.
Currency and National Currency Exchange Rates
The rates used to convert contracts consideration/entitlement currency and national currency requirements into the product's consideration/entitlement currency and national currency denomination.
Deal Flag
An indicator or “flag” notified to CONTRACT APP signifying that the stakeholder is satisfied to deal unreservedly with the stakeholder against whom the flag has been set.
Defined Circumstances
The possible combinations of the categories of product-order information provided by Ordering parties.
Defined Probability Distributions
A set of pricing probability parameters specified by an Ordering party and including at least, a probability distribution type identifier, the expected value of the distribution, the standard deviation of the distribution and a probability distribution adjustment value or function.
Desired Currency Denomination of Contract Entitlement
A term indicating the currency in which an Ordering party wishes to receive potential entitlement payments from the sought contract.
Desired Currency Denomination of Consideration Payment
A term indicating the currency in which an Ordering party wishes to pay the required consideration for the contract sought.
Desired National Currency Denomination of Contract Entitlement
A term indicating the National currency in which an Ordering party wishes to receive potential entitlement payments from the sought contract.
Desired National Currency Denomination of Consideration Payment
A term indicating the National currency in which the Ordering party wishes to pay the required consideration for the contract being sought.
Discount Rate
The rate used to determine the present value of a potential counterparty's expected future entitlements.
Entitlement
The payout expected by the offering party at maturity as specified for each outcome in the range of outcomes. The payout can be both positive and negative in value over the range of outcomes, and can be in the form of money or other non-money types of goods, services, promises, credits or warrants.
EV-CE Pricing
A price discovery mechanism for primary contracts meaning “expected value certainty equivalent pricing” being the calculated expected present value or future value of the contract.
Expected Value
A function in EV-CE pricing which means the sum of the product of all possible contract entitlement payoff/payout amounts of the Ordering party's/Counterparty's assessment of the probability of occurrence of the future events which would contractually give rise to these entitlement payoff amounts.
Expected Value Limits on a Counterparty's Aggregate Product Portfolio
Optional value limits specified by a Potential counterparty at any one time, where time can be specified in terms including “equivalent maturity date”; “same-month maturity date” and “all possible maturity dates” including product expected loss limits and maximum (and possible minimum) proportion of the expected total loss of the aggregate of the Counterparty's product portfolio that can be accounted for the expected loss on the individual contract/product.
Gamma(X)
The Ordering party-specified desired shape of the function between each of the co-ordinates Alpha(1), Beta(1) and Alpha(2), Beta(2) and so on; such that Gamma can represent all possible mathematically definable shapes.
I-INVENTCO
The infrastructure component of INVENTCO.
INVENTCO
A collection of one or more (potentially interrelated) systems, where each system is the combination of a telecommunications, computing and other forms of infrastructure, and a variety of markets and support services distributed by this infrastructure.
M-INVENTCO
A depository of VIRPRO authorised “markets” application software.
Manual Deal Flag
An indicator or “flag” notified to CONTRACT APP by a stakeholder signifying that the stakeholder wishes to manually approve a transaction involving the other stakeholder against whom the flag has been set.
Multilateral Payments Netting Indicator
An indicator that individual end-of-day gross payments/receipts to/from all participating stakeholders from/to a specified third party trustee/clearing entity are to be netted.
Multilateral Obligations Netting Indicator
An indicator that individual ‘rolling’ net present values of future payment/receipt commitments to/from all participating stakeholders from/to a third party trustee/clearing entity are to be netted.
Negative Contract Payoffs
A type of contract in which the contract Ordering party may have a contingent payoff to the contract's Potential counterparty (i.e. the reverse of a normal contract).
No Deal Flag
An indicator or “flag” notified to a CONTRACT APP by a stakeholder signifying that the stakeholder does not wish to deal in any way with the other stakeholder against whom the flag has been set.
Ordering Party Contingent Claims Function
Specifications of a product payoff or a mathematical function to calculate an Ordering party's product payoff requirement.
Portfolio Product “Expected Loss” Limit
A value limit, specified by a potential Counterparty, of the maximum expected loss the potential Counterparty is prepared to sustain on its product portfolio based on the Counterparty's assessment of the likelihood of all levels of possible loss being incurred.
Product Ordering Party
An entity acceptable to VIRPRO and the Application Promoter, interested in and able to acquire a CONTRACT APP product.
Product Establishment Date/Time
The date/time an Application Promoter first offers a defined product for trading.
Product Future Event Value “Density” Indicator
An indicator specifying the number of intermediate points between the minimum and maximum future event product definition values specified for the product by the Application Promoter/Product Sponsor.
Product Event Value “Width” Indicator
An indicator specifying the range (minimum-maximum) of future event values accommodated by the product as set by the Application Promoter/Product Sponsor.
Product Future Event Value
A term used to indicate the actual values of a defined product at its date/time of maturity.
product Maturity Date/Time
The date-time at which the Application Promoter is required to make a determination of the actual event value to enable entitlement and related payoffs on successful contracts.
Product Price Quote Requests
A type of product purchase order for which the matching process is terminated and the result communicated to the Ordering party, when a desired price bid or range of price bids has been obtained.
Product Purchase Orders
Specific product purchase orders for which the Ordering party is seeking a potential Counterparty match, which may be of three types: automatic orders; manual orders and “hide” orders.
Product Purchase Order Withdrawals
Ordering party-initiated requests to withdraw from processing pre-submitted but as yet unconfirmed product purchase orders.
Product Potential Counterparty
An entity acceptable to VIRPRO and the Application Promoter, exceeding a defined minimum standard of financial strength, credit standing and integrity, offering defined CONTRACT APP products to product Ordering parties.
Product Sponsor
An entity acceptable to VIRPRO and the Application Promoter, having responsibility for detailed definition of product parameters including the continual determination of product values over time.
Regulator
An entity acceptable to VIRPRO having local, state, national or international jurisdiction over one or more CONTRACT APPS.
Set of Pricing Probabilities
The range of probabilities a potential Counterparty applies to a class of Ordering party order, specified by the value of “defined circumstances” and applying to every feasible future product event defined for that product by an Application Promoter.
Stakeholder
An entity that is a registered participant in one or more INVENTCO's component parts.
Value Dates
The respective dates/times at which matched contract consideration and entitlements are agreed to be made by the relevant Ordering party/Counterparty to a contract.
VIRPRO
The network and general management system component of INVENTCO.
“X”
A term indicating the number of contract payoff (payout) inflection points the Ordering party is seeking within the allowable range of future product event values (including the value range extremity points).
CONTRACT APPS
Overview
CONTRACT APPS is a term used to refer to certain types of units of applications software which can, but do not need to, reside within an INVENTCO system's (M-INVENTCO) depository of “markets” software. The purpose of individual CONTRACT APPS is two-fold: First, to effect the trading/exchange/transfer of risk aversion transactions (and derivatives of these transactions) between participating ordering parties and counterparties on terms acceptable to the parties involved as well as to others within INVENTCO registered as having a legitimate interest in the nature, size and composition of these trade/exchanges/transfers. And second, to appropriately manage all matched/confirmed contracts through their time of maturity, including their ultimate settlement.
Individual CONTRACT APPS perform these tasks according to the specific rules they embody, defined by their own stakeholders. CONTRACT APPS effectively reside upon AXSCO and within M-INVENTCO.
Stakeholder Types
CONTRACT APPS accommodate eight (and potentially fewer) generic types of their “own” stakeholders (as distinct from other INVENTCO stakeholders) termed: application promoter, product sponsors, product ordering parties, potential product counterparties, counterparty-guarantors, regulators, consideration/entitlement transfer entities, and other miscellaneous parties.
Some details of these stakeholders are as follows: an application is an entity having overall responsibility for the functioning of a CONTRACT APP (that responsibility having been granted by the VIRPRO); a product sponsor is an entity which promotes and administers the rules of trading, and subsequent management, of defined contingent claims contracting product(s) selected for inclusion in a CONTRACT APP by its application promoter; a product ordering party is an entity seeking to acquire a CONTRACT APP product from a potential product counterparty (where a product ordering party can also be a product counterparty); a potential product counterparty is an entity potentially prepared to satisfy the CONTRACT APP product needs of a product ordering party (where a potential product counterparty can also be a product ordering party); a counterparty-guarantor is an entity guaranteeing a product counterparty's ability to settle any/all of its potential entitlement transfer obligations to a product ordering party to which it has become a counterparty as a result of a CONTRACT APP effected “match”; regulators are entities overseeing the on-going performance of all other stakeholders involved in a CONTRACT APP, especially counterparty-guarantors; consideration/entitlement transfer entities are entities with which all other CONTRACT APP stakeholders maintain “accounts” to transfer required considerations/entitlements to/from all each other; and miscellaneous parties are all other entities having a defined stake in the functioning of a CONTRACT APP.
Miscellaneous parties include: independent entities contracted by application promoters or product sponsors to formally determine the “value” of products on their date-of-maturity; multilateral obligations and payment netting trustee/clearing entity organisations; independent (non-regulator) taxation and other governmental authorities; electronic “gateway” providers (external to INVENTCO); and host system organizations (in the case of CONTRACT APPS within INVENTCO systems linked to a common host system). CONTRACT APPS accommodate any number of their own stakeholders of each of the above-defined generic types.
Product Types
CONTRACT APPS can support risk aversion contract “product types” with any combination of values of multiple attributes, including: the fundamental nature/purpose of the product; the establishment/maturity date/time of the product; the consideration/entitlement denomination type, currency (if applicable), and national currency (if applicable) consideration/entitlement identifiers associated with the product; the “width” and “density” identifiers of possible future event values of the product; and miscellaneous other product descriptors.
The “fundamental nature/purpose of the product” attribute may incorporate identifiers including: a conditional entitlement-payoff dimensions identifier; a market identifier; a sub-market identifier; and a market-type identifier. The “conditional entitlement-payoff dimensions identifier” specifies the number of dimensions to an ordering party's sought-after conditional entitlement-payoffs. The market identifier specifies whether the product relates to an “actual” or “perceived” phenomenon (or phenomena), the number of such phenomena (if applicable), and the applicable phenomenon category (for example, industrial, scientific, financial market hedging, and so on). The sub-market identifier provides a more specific description of the product concerned. The market-type identifier specifies the applicable future period date/time (where this can be anything—for example, “at a defined contract maturity date/time”, “at a specified time on or before contract maturity date/time”, and so on), and type-of-future event involved (where, again, this can be anything—for example, as an indicator of some relative value of a phenomenon (spot value, average value and so on), or as an indicator of the “rate-of-change” of some value of a phenomenon.
The “establishment and maturity date/time of the product” attribute specifies, respectively, the date/time an application promoter first offered a product for trading, and the date/time the defined product matures (that is, the date/time at which the product sponsor is required to make a determination of the actual event at that date/time so enabling contract entitlement transfers to be effected).
The “consideration/entitlement denomination type, currency (if applicable), and national currency (if applicable) consideration/entitlement identifiers associated with the product” attribute specify: the type of consideration/entitlement involved (where this can include rights and entitlements, physical assets, and “money” of al possible types); in the case of a “money” consideration/entitlement type, the currency of the consideration/entitlement (where such currency types can include: public/private record-depository deposits, commercial credit card company deposits, commercial bank deposits, central bank deposits, taxation authority deposits, and deposits in non-bank clearing houses and depositories, and the like); and, again, in the case of a “money” consideration/entitlement type, the national currency of the consideration/entitlement identifier (where such currency types can be in any national currency, or form of synthetic currency).
The “width and density identifiers of possible future event values of the product” attribute specifies, respectively: the minimum and maximum values of the allowable range of future event values accommodated by a product; and the number of intermediate points between the defined minimum and maximum future event values accommodated by the product.
The “miscellaneous other product descriptors” attribute specifies such things as: the degree of stakeholder access granted the product by the application promoter in question; the forms of trading-services granted the product by the application promoter in question (where this product attribute specifies the accessibility of the product to a range of feasible “stakeholder services” with respect to such things as contract portfolio netting, contract collateralisation, consideration credit provision, ordering party ability to specify negative contract entitlements, and availability of secondary/derivative market product rating); and the degrees of trading, clearing and settlement “transparency” granted the product by the application promoter in question.
Transaction Types
A range of primary, secondary, derivative-primary, and derivative-secondary risk aversion contract transactions are accommodated by CONTRACT APPS.
The range of “primary” (and derivative-primary (options, for example)) risk aversion Contract transaction-types (handled principally by Processes 2 and 4 include: ordering party product orders (and option orders) for which the ordering party is seeking a counterparty “match”, ordering-part), price quote (and options price quote) requests; and ordering-party withdrawals of existing product orders (and withdrawal of options on product orders). Ordering party product orders consist of: automatic orders and manual orders. Automatic orders consist of: normal automatic orders (being orders the ordering party is prepared to have matched automatically, subject only to the constraints defined in the ordering party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified); and anonymous-automatic orders (being orders the ordering party is prepared to have matched automatically, subject to the constraints defined in the ordering party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified, provided that no CONTRACT APP stakeholder has sought to manually authorise the transaction and, through so doing, being able to potentially identify the ordering party). Manual orders consist of normal-manual orders (being orders the ordering party wishes to manually authorise before they are finalised—that is, after a counterparty “match” has been effected but before the contract has been “confirmed”—subject only to the constraints defined in the ordering party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified); and anonymous-manual orders (being orders the ordering party wishes to manually authorise before they are finalised—that is, after a counterparty “match” has been effected but before the contract has been “confirmed” subject to the constraints defined in the ordering party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified, provided that no CONTRACT APP stakeholder has also sought to manually authorise the transaction and, through so doing, potentially identify the ordering party).
The range of “secondary” (and derivative-secondary (options, for example) risk aversion contract transaction-types (handled principally by Processes 3 and 5 include: acquiring party product orders (and option orders) for which the acquiring party is seeking to “acquire” the position of a specified “risk counterparty” stakeholder in an existing contract; acquiring-party product price indications (and option price indications); and acquiring-party withdrawals of existing product orders (and option withdrawals).
Acquiring product party orders for which the acquiring party is seeking to “Acquire” the position of a specified “risk counterparty” stakeholder in an existing contract, consist of automatic orders and manual orders.
Automatic orders consist of: normal-automatic orders (being orders the acquiring party is prepared to have matched automatically, subject only to the constraints defined in the acquiring party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified); and anonymous-automatic orders (being orders the acquiring party is prepared to have matched automatically, subject to the constraints defined in the acquiring party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified, provided that no CONTRACT APP stakeholder has sought to manually authorise the transaction and, through so doing, being able to potentially identify the acquiring party).
Manual orders consist of normal-manual orders (being orders the acquiring party wishes to manually authorise before they are finalised—that is, after a “match” has been effected but before the contract “sale” is “confirmed”—subject only to the constraints defined in the acquiring party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified); and anonymous-manual orders (being orders the acquiring party wishes to manually authorise before they are finalised—that is, after a “match” has been effected but before the contract “sale” is “confirmed”—subject to the constraints defined in the acquiring party's order, in addition to whatever “match” constraints other CONTRACT APP stakeholders have prespecified, provided that no CONTRACT APP stakeholder has also sought to manually authorise the transaction and, through so doing, potentially identify the acquiring party).
Primary Product Pricing Process Types
CONTRACT APPS enable potential counterparties to automatically establish “bids” on any defined (primary and derivative-primary) product order according to either an “expected-value/utility-certainty equivalent” (EV/U-CE) pricing regime, or any other mathematically-definable pricing regime.
In the case of an “expected value-certainty equivalent” (EV-CE) pricing regime, each potential counterparty specifies, amongst other things: an indicator of certain defined attributes of an as-yet-unknown product order; a base commission rate; a base discount rate; (if applicable) a set of base consideration/entitlement denomination, currency, and national currency exchange rates; base unit product prices; and desired adjustments to the preceding base-bid-price determinants dependent on any specific order (submitted by a specified ordering party).
The above-described indicator of certain defined attributes of an as-yet-unknown product order (termed, defined circumstances) may reflect any combination of the multiple characteristics of an order (irrespective of the ordering party concerned) including: the multiple attributes of the contingent claims function sought; the ordering party's interest or otherwise in being granted credit by a counterparty; the ordering party's interest or otherwise in participating in the possible netting and collateralisation features of the APP; and the maximum (and possibly minimum) consideration amount of the ordering party is prepared to pay for their defined product. The above-described base commission rate specifies the minimum required percentage profit margin required by the counterparty above their breakeven consideration bid price for a product order.
The above-described base discount rate determines the present value of the counterparty's expected future entitlement associated with a contract (net of the ordering party's consideration, and making allowance for the future income stream this consideration is expected to generate). The above-described set of base consideration/entitlement denomination, currency and national currency exchange rates are used, where applicable, to convert an ordering party's contract requirements into the base consideration/entitlement denomination, currency and national currency of the product so enabling the contract matching process to make like comparisons of counterparty bids for product orders.
The above-described base unit product prices are prices set by potential counterparties for unit entitlement-payoffs of a contract at each of its possible future values, denominated in the contract's formally specified consideration/entitlement type and, if applicable, currency type and national currency type (where these unit prices can be specified as directly input figures for every feasible future product event (the sum of which may or may not add to 1), or as parameters of defined mathematical functions). The above-described desired adjustments to the preceding base-bid-price determinants dependent on the specific ordering party submitting a specific order can include: a commission rate adjustment; a discount rate adjustment; a consideration/denomination exchange rate adjustment; a currency exchange rate adjustment; and a national currency exchange rate adjustment.
In the case of an “expected utility-certainty equivalent” (EU-CE) pricing regime, each potential counterparty specifies all of the above-described parameters applicable to a EV-CE pricing regime as well as “utility bench-mark” figures for all possible consideration and entitlement “payment amounts” which could, conceivably, be associated with a product/contract.
Primary Product Matching Process Types
CONTRACT APPS may similarly accommodate any of a number of possible (primary or derivative-primary) order matching processes where these processes can be of multiple types, including sequential processes and simultaneous processes.
Sequential order matching processes can be characterised according to the “sequence determining” and “matching” rules they embody, where “sequence” rules may be of various types: “last-in-first-out (LIFO)”, “first-in-first-out (FIFO)”, priced priority, and so on; and matching rules may also be of various types—for example, a specific matching process could seek, for each product ordering party, a counterparty (or counterparties) offering a product price at or below the maximum price the ordering party is prepared to pay (where the determined contract could be either the lowest price offered by a potential counterparty, the mid-point between an ordering party's specified “maximum consideration amount” and the lowest price offered by a potential counterparty, and so on); or seek for each potential product counterparty an ordering party prepared to pay the maximum price above a price at which the counterparty is prepared to deal (here, the determined contract price could be either: the ordering party's “maximum consideration amount” price, the mid point between the minimum price the counterparty is prepared to receive and the ordering party's “maximum consideration amount” price, and so on).
Simultaneous order matching processes are those seeking some type of optimum solution according to pre-defined objectives. For example: “maximise the number of ordering party-counterparty matches”; “maximize the aggregate consideration and/or entitlement value of ordering party-counterparty matches”; or “minimize the value of a function specifying the sum of the difference (possibly weighted according to their perceived importance) between the actual and desired values of match attributes of ordering parties and counterparties”.
Both of the above-described sequential and simultaneous matching processes can also accommodate conditional contract matching rules; and pre and post tax price optimisation mechanisms.
Application Types
CONTRACT APPS may be: “in-house” APPS or “public” APPS; “single potential counterparty” APPS or “multiple potential counterparty” APPS; APPS with differing degrees and forms of “regulator” oversight of other application stakeholder; and APPS with differing degrees and forms of “counterparty-guatantor” oversight of product potential counterparties.
CONTRACT APPS support consideration “payment” value dates being “immediate” (meaning exactly the same at which a contract match is confirmed); or deferred until a defined time in the future, measured in terms of seconds, minutes, hours, or days. Similarly, CONTRACT APPS support entitlement “payment” value dates being “immediate” (meaning exactly the time at which the applicable application promoter formally notifies other CONTRACT APP stakeholders of the “result” of a maturing contract); or deferred until a defined time after the “result” of a maturing contract is known.
CONTRACT APPS allow contracts to be modified and liquidated after their creation. Contracts can be modified through: direct negotiation by the relevant “risk counterparties” to a particular contract; or the purchase/sale of “derivative” secondary risk aversion contract transactions (See Process 5 description below). Contracts can be similarly liquidated after their creation through sale of the contract (within or outside INVENTCO); and through direct negotiation between the initial ordering party and counter-parties to the contract. They can also be effectively liquidated through the ordering party/counterparty acquiring a mirror image of the contract to which they are a party (within or outside of INVENTCO).
Post Order Process Types
CONTRACT APPS undertake various generic types of “post-order-process” management functions for all of the above-described generic types of “transactions”, including: a function which maintains a formal record of contractual commitments entered into by all CONTRACT APP stakeholders with one another, and with VIRPRO-authorised entities external to either the applicable CONTRACT APP or INVENTCO overall; a function which effects the independent valuation of consideration and entitlement obligations between CONTRACT APP stakeholders, and between CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP; a function which determines and effects “collateralisation” consideration/entitlement transfers between CONTRACT APP stakeholders, and between CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP, based on above-described valuations of consideration and entitlement obligations associated with CONTRACT APP transactions; a function which determines and effects, as required, the bi-lateral netting of accumulated “consideration/entitlement” obligations “between CONTRACT APP stakeholders, and between CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP; a function which determines and effects, as required, the multi-lateral netting of accumulated “consideration/entitlement” obligations” between CONTRACT APP stakeholders, and between CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP (involving a nominated third-party “clearing house” entity); a function which manages the processing, accounting, reporting, and entitlement “payment” tasks associated with maturing contracts; a function which determines system usage and access fees payable to/from all CONTRACT APP (and other INVENTCO, stakeholders, and to/from VIRPRO-authorised entities external to INVENTCO; a function which determines and effects, as required, “bi-laterally netted” consideration/entitlement transfers from/to CONTRACT APP stakeholders themselves, and from/to CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP; a function which determines and effects, as required, “multi-laterally netted” consideration/entitlement transfers from/to CONTRACT APP stakeholders themselves, and from/to CONTRACT APP stakeholders and VIRPRO-authorised entities external to each applicable CONTRACT APP (involving a nominated third-party “clearing house” entity); and a function which compiles and distributes CONTRACT APP (and other INVENTCO) stakeholder customised information.
Supplementary Process Types
CONTRACT APPS undertake various other types of support processes, including: enabling stakeholders to transfer consideration, entitlement and other “payment” obligations to and from one another, independently of transfers initiated by CONTRACT APP transactions (See Process 7 description below); providing CONTRACT APP (and other INVENTCO) stakeholders with shared access to specialist systems to assist them to decide how best to interface with the multiple aspects of INVENTCO (See Process 8 description below); and providing CONTRACT APP (and other INVENTCO) stakeholders with access to a range of INVENTCO-facilitated “value added services” (See Process 9 description below).
Order Matching Constraint Types
For their operation, CONTRACT APPS require all stakeholders to a specific APP to specify, amongst other things, which other stakeholders they do and do not want to have interactions with, and the conditions under which they wish to manually authorise some aspect of a transaction involving any other CONTRACT APP stakeholder over which they have control authority of some form.
In specifying which other stakeholders they do and do not want to have interactions with, CONTRACT APP stakeholders have various options. Application promoters can specify acceptable product sponsors, products, ordering parties and potential counterparties within their application—individually and by type. Similarly, product sponsors can specify acceptable application promoters, products, ordering parties, potential counterparties and counterparty-guarantors within their application—individually and by type.
Product counterparties and ordering parties (collectively) can specify: ordering parties/potential counterparties they do and do not want to deal with—individually and by type; the extent of their preparedness to be involved in contract netting and collateralisation arrangements provided for by their application promoter; application promoters, product sponsors, products, and consideration/entitlement transfer entities they do and do not want to deal with—individually and by type; ordering parties/potential counterparties they prefer to deal with, and those with which they wish to deal exclusively; the degree of trading transparency they require; and their wish or otherwise to manually authorise order matches before they are confirmed.
Potential counterparties can specify which ordering parties, or classes of ordering parties, they are prepared to offer credit to (and under what terms), and ones they are prepared to allow “ordering party-guarantors” to offer credit to and under what terms. Similarly, product ordering parties (uniquely) can specify: counterparty-guarantors with which they do and do not want to deal (individually and by type); counterparties with which they wish to deal exclusively or preferentially to obtain a particular form of counterparty-credit; and potential “ordering party-guarantors” (external to INVENTCO) with which they do and do not want to deal.
Counterparty-guarantors can specify which potential counterparties have their authority to operate and which application promoters, product sponsors and ordering parties they are prepared, indirectly, to have relationships with. Similarly, regulators can specify which counterparty-guarantors, potential counterparties, ordering parties, application promoters, product sponsors and products have their authority to operate. Finally, consideration/entitlement transfer entities can monitor and maintain up-to-date rules with respect to ordering parties, counterparties, application promoters, product sponsors, counterparty-guarantors, and regulators they are and are not prepared to deal with—individually and by type.
Ordering Party Requirements
For their operation, CONTRACT APPS require primary product ordering party stakeholders to a CONTRACT APP, in registering an order for a product of their choice, to specify: the above-described “product type” and “other stakeholder involvement” information; multiple attributes of the specific order they are seeking; their interest or otherwise in being granted credit by potential counterparties for their contract consideration amount, or in availing themselves of the possible netting and collateralisation features of the APP concerned; the maximum (and possibly minimum) consideration “price” they are prepared to pay for their defined product; and various other dimensions of their needs, where these include: the name/title by which they wish to be identified by other APP stakeholders; the time at which they wish their order to be submitted; the period of time after an order has been submitted that they wish the order to be retained before it is automatically withdrawn; whether or not they are prepared to accept partial matches of their order; the degree of market transparency they wish to be exposed to; whether or not they wish to have the option of trading a matched contract on an authorised INVENTCO secondary market (See Process 5 description below); whether or not they wish to manually consider/authorise potential counterparty quotes on an order; in the case where potential counterparty quotes are required to be manually considered/authorised, the maximum time after potential counterparty quote details are provided to the ordering party that the ordering party wishes to consider the quote(s); and the consideration/entitlement transfer entity accounts from which/to which they wish to have relevant “payments” made/received.
The above-mentioned multiple attributes of a specific primary order an ordering party is seeking include: their wish or otherwise to directly input the entitlement “coordinates” of their desired contingent claim order; their wish or otherwise to mathematically specify an entitlement function reflecting their desired product order, where such functions can be single or multidimensional (indicating a contingent contract entitlement conditional on two or more phenomena); the “conditional/entitlement unit”, “currency” (if applicable), and “national currency” (if applicable) in which they wish to “pay”/“receive” their contract consideration/entitlement. Where an ordering party wishes to mathematically specify their desired primary product order as a single-dimensional entitlement function: the input term “X” can indicate the number of contract entitlement “inflection points” the ordering party is seeking within the allowable range of future product event values (including the value range extremity points); the input term “Alpha (X)” can indicate the ordering party-specified event value corresponding to the Xth future product event value contract entitlement inflection point; the input term “Beta (X)” can indicate the ordering party-specified desired entitlement amount (in the desired “consideration/entitlement form”, “currency” and “national currency” entitlement denomination) corresponding to the Xth event value inflection point; and the input term “Gamma (X-1)” can indicate the ordering party-specified desired shape of the function between each of the co-ordinates: [Alpha (1), Beta (1)] and [Alpha (2), Beta (2)], [Alpha (2), Beta (2)] and [Alpha (3), beta (3)], and so on (as applicable), where Gamma can represent all possible, mathematically definable, shapes.
Potential Counterparty Requirements
For their operation, CONTRACT APPS also require primary product “potential counterparty” stakeholders to a CONTRACT APP to define various parameters on the basis of which they can automatically price orders, including parameters with which they wish to establish a “consideration bid” on a defined product order; possible individual contract and product constraints they require to be satisfied if they were to become a counterparty to a defined product ordering party order; and possible expected-value product-portfolio constraints they require to be satisfied if they were to become a counterparty to a defined product ordering party order.
In parameters with which they wish to establish a “consideration bid” on a defined product order under a “EV-CE” pricing regime (described above), each potential counterparty is required to specify, amongst other things: and indicator of the appropriate “defined circumstances” of all possible product orders; a base “commission rate”; a base “discount rate”; (if applicable), a set of base “consideration/entitlement denomination”, “currency” and “national currency” exchange rates; base “unit product prices”; and desired adjustments to the base commission rate, discount rate, exchange rates, and unit product prices on specific product orders according to the determined-value of the “defined circumstances” indicator (based on a specific product order).
Possible individual contract and product constraints the potential counterparty requires to be satisfied if they were to become a counterparty to a defined product ordering party order, include: an absolute loss limit constraint (this constraint being specified as a single-figure constraint and/or as a function constraint); an expected loss limit constraint (this constraint defining the maximum “expected” aggregate loss the potential counterparty is prepared to incur on a contract/product, taking into account their assessment of the likelihood of all feasible future product values occurring); and a constraint on the maximum proportion of the expected total loss of the aggregate of the potential counterparty's contracts/products that can be accounted for by the expected loss of the defined individual contract/product. Similarly, possible expected-value product-portfolio constraints the potential counterparty requires to be satisfied if they were to become a counterparty to a defined product ordering party order include the maximum (and possibly minimum) proportion of the expected total loss of the aggregate of the potential counterparty's product portfolio that can be accounted for by the expected loss of an individual contract/product.
Communications
CONTRACT APP stakeholders communicate with their applicable APP via AXSCO. Individual “stakeholder-to/from-AXSCO” communications can be by way of any/all of the following: voice communications with an AXSCO-linked “live operator” or “recorded messaging” system; touch-telephone communication with AXSCO directly; or computer-to-computer link with AXSCO (via a dedicated or dial-up communications line). With all three forms of communication, CONTRACT APP stakeholders may be required to utilize specified computer hardware and/or software mechanisms in their communications with AXSCO (including “payments” authorisation “black box” devices referred to below).
Component Process
In their manifestation as telecommunications/computer software residing on telecommunications/computer hardware, individual CONTRACT APPS consist of a cluster of processes, utilizing a number of data files, residing on one or more processing units. A cluster of nine (and potentially more or fewer) specific processes and their related data files reside within a CONTRACT APP: a process handling file administration and updating tasks supporting all other processes (termed Process 1); a process handling the receipt and processing of “primary” risk management contract transactions (termed Process 2); a process handling the receipt and processing of “secondary” risk management contract transactions (termed Process 3); a process handling the receipt and processing of “derivative-primary” risk management contract transactions (termed Process 4); a process handling the receipt and processing of “derivative-secondary” risk management contract transactions (termed Process 5); a process handling the “back office” management of all four types of risk management contract transactions (termed Process 6); a process handling non-transaction related consideration, entitlement, and other “payment” obligation transfers between stakeholders (termed Process 7); a process handling CONTRACT APP (and other INVENTCO) stakeholder access to specialist systems to assist these stakeholders decide how best to interface with the multiple aspects of INVENTCO (termed Process 8); and a process handling CONTRACT APP (and other INVENTCO) stakeholder access to a range of INVENTCO-facilitated “value added services” (termed Process 9). These processes may function concurrently.
Description of CONTRACT APP Processed
Process 1
Process 1 handles file administration and updating tasks supporting all other processes (FIG. 18), The PRODUCT, PRODUCT TRANS, DEAL LIST and DEAL LIST TRANS files referred to in FIG. 18 are applicable, individually or collectively, to primary, secondary, derivative-primary, and derivative-secondary contract orders. The SEL PRICE, SEL PRICE TRANS, SEL LIMIT and SEL LIMIT TRANS files are applicable only to primary and derivative-primary contract orders. The TRADE PRICE, TRADE PRICE TRANS, TRADE LIMIT and TRADE LIMIT TRANS files are applicable only to secondary and derivative-secondary contract orders.
The file administration and updating tasks handled by Process 1 comprise: dealing with general data-file information received from CONTRACT APP stakeholders; dealing with general data-file and order processing information received from relevant other INVENTCO stakeholders, particularly VIRPRO and AXSCO; dealing with trading support information received directly from CONTRACT APP stakeholders; dealing with potential counterparty primary, and derivative-primary, product order “consideration bid” parameters and order-match constraints; dealing with existing-contract offering party secondary, and derivative secondary, order match conditions; and dealing with miscellaneous information from entities external to INVENTCO.
Existing and prospective stakeholders are required to supply their applicable CONTRACT APP with specified identification and other information, and to continually maintain the integrity of this information. For each stakeholder, this information includes: applicable name(s), addresses, contact numbers, and references; their desired system access medium; their consideration/entitlement transfer entity account details; and, if applicable, their required schedule and fees and charges payable by other INVENTCO stakeholders. This information is maintained in the data file ADMIN, updated information being received by way of the transaction file ADMIN TRANS.
VIRPRO is required to supply the applicable CONTRACT APP with various forms of general data-file information including: identification data relating to the application promoter for (each) CONTRACT APP; details of the permitted types of system access mediums; and consideration/entitlement denominations available in each application. Again, this information is maintained in the data file ADMIN, updated information being received by way of the transaction file ADMIN TRANS.
VIRPRO is similarly required to supply the applicable CONTRACT APP with various forms of general data-file information including: information on all data received by and sent from the various parts of INVENTCO to one another and to entities external to INVENTCO; and statistical information of various types, including data traffic volumes, data file location information and so on. This information is continuously collected by AXSCO and maintained in the data file HISTORY.
Trading support information received directly from CONTRACT APP stakeholders comprises stakeholder relationship information of a general nature, and specific information from individual stakeholders.
Stakeholder relationship information of a general nature comprises “transaction communication parameters” and automatic/manual deal and no deal flags”. Transaction communication parameters are parameters set by all (registered) CONTRACT APP stakeholders defining the bounds within which they wish, for security reasons, all of their communications within INVENTCO to fall. Automatic/manual deal and no deal flags are “flags” set, as required, by all (registered) CONTRACT APP stakeholders indicating their requirements with respect to dealing with other CONTRACT APP stakeholders. This information is maintained in the data file DEAL LIST, updated information being received by way of the transaction file DEAL LIST TRANS.
Specific information from individual stakeholders differs according to category of stakeholder involved.
Application promoters provide, amongst other things: information for the data file, PRODUCT (updated transactions being received from the file, PRODUCT TRANS), and further information for the data file ADMIN (updated transactions being received from the file, ADMIN TRANS). Information for the data file, PRODUCT includes details of the specific products application promoters offer for trading/exchange/transfer. Information for the data file, ADMIN includes: the order pricing and matching process upon which their application is based; the consideration/entitlement “value date” regime upon which their application is based; the categories of other stakeholders allowed to participate in the application and the conditions under which they can do this; the specific rules of engagement of counterparty-guarantors by potential counterparties; the availability and, in turn, the terms and conditions for CONTRACT APP stakeholder utilization of “consideration credit”, “collateralisation”, and “netting” features of the application (embodied in the various post-order processing management routines); and details of the consideration/entitlement transfer entities involved in the application and relevant security information concerning account access.
Product sponsors provide full detail of the product(s) they are sponsoring; product ordering parties and potential counterparties (collectively) indicate, with respect to each other, the parties they either prefer to deal with or wish to deal with exclusively. Potential counterparties (exclusively) provide a variety of specific information, including: details of the Application promoter, Product sponsor, and Counterparty-guarantor rules under which they have chosen to operate; data recording the lines of credit (if any) offered to the ordering parties and the general and specific terms and conditions of these credit lines (applicable to ordering parties individually and/or to defined classes of ordering parties); parameters with which a potential counterparty wishes to determine its consideration “bids” on orders. Counterparty-guarantors provide details of the potential counterparties (if any) they have agreed to guarantee and the nature of such guarantees. Regulators provide details of: all entities having a stake in the application and their relationships to one another (for example, which counterparty-guarantors cover which counterparties, which potential counterparties offer which products, and so on); specific regulations developed for the regime; and parameters defining the taxation treatment of all types of orders and related transactions. Consideration/entitlement transfer entities provide “set-up” and on-going account access and balance-updating services. All of the above-described information is maintained in the data file, ADMIN, updated information being received by way of the transaction file ADMIN TRANS.
In dealing with potential counterparty primary product order “consideration bid” parameters and order-match constraints, potential product order counterparties are required, amongst other things, to: define various parameters with which they wish to establish a consideration bid on a defined product order; and define parameters with which the potential counterparty wishes to determine adjustments to the “base-price” bids on product orders according to the specific ordering party involved (this information is maintained in the data file SEL PRICE; updated information is received by way of the transaction files SEL PRICE TRANS); define possible individual contract and product constraints the potential counterparty requires to be satisfied if they are to become a counterparty to a defined product ordering party order; and define possible expected-value product-portfolio constraints the potential counterparty requires to be satisfied if they are to become a counterparty to a defined product ordering party order (these latter two categories of information are maintained in the data files SEL LIMIT and BUY LIMIT; updated information being received by way of the transaction file SEL LIMIT TRANS).
In dealing with existing-contract offering party secondary order match conditions, offering parties are required, amongst other things, to specify: the Order IDs of the contracts in which the entity concerned wishes to “sell” its position as a contract stakeholder, and, for each such contract, the pricing and other parameters it requires to be satisfied before a contract position “sale” is effected. This information is maintained in the data file TRADE PRICE; updated information is received by way of the transaction file TRADE PRICE TRANS.
In dealing with potential counterparty derivative-primary product order “consideration bid” parameters and order-match constraints, potential product order counterparties are required to provide essentially the same information described above in relation to primary product order. However, in addition, information directly applicable to the relevant type of derivative-primary transaction concerned (say, an option to establish a primary product order at a later date) is also required.
In dealing with existing-contract-offering party derivative-secondary order match conditions, offering parties are required to provide essentially the same information described above in relation to secondary product orders. However, in addition, information directly applicable to the relevant type of derivative-secondary transaction concerned (say, an option to sell a position in a primary product order at a later date) is also required.
In dealing with miscellaneous information from entities external to INVENTCO, this information can be of any type and may, potentially, be used by any part of INVENTCO; the information is maintained in the data file ADMIN with updated information being received by way of the transaction file ADMIN TRANS
Process 2
Process 2 handles the receipt and processing of “primary” risk management contract transactions, such transactions being of multiple types. Various sub-processes of Process 2 handle the receipt and processing of all possible types of these transactions, including product order processing, price quote requests, and withdrawals of existing product orders.
Primary “product orders” constitute “core” risk management contract transaction type (FIG. 19 provides a summary flow chart, and the document text provides a detailed flow chart and description of the processing of this transaction type).
Primary product orders incorporate the following key items of information: ordering party identification information; CONTRACT APP application and product identification information; “other stakeholder involvement” information; the ordering party's desired form of product specification (directly input as entitlement coordinates or as mathematical function(s)); when the order specification is by way of single-dimensional mathematical function, the parameters of such a function (which can include: the term “X”, the term “Alpha (X)”, the terms Beta (X)”, the term Gamma (X-1)”; the contract consideration and entitlement “denomination type”, “currency (if applicable)” and “national currency (if applicable)”; the ordering party's interest or otherwise in being granted credit by potential counterparties for the yet-to-be-determined contract consideration amount; the ordering party's interest or otherwise in availing themselves of the possible netting and collateralisation features of the APP concerned; the consideration “price” range within which the ordering party is prepared to “pay” for their defined product; miscellaneous other dimensions of the ordering party's needs, and the consideration/entitlement transfer entity accounts from which/to which they wish to have relevant “payments” made/received). Upon its receipt, all of this information is written to—and subsequently processed from—the PORD NEW.
Three sub-processes are involved in processing primary product orders—order authorisation, order matching, and matched order confirmation. In the case of the anticipated most typical form of order, termed a “normal-automatic” primary product order these sub-processes function as follows:
The primary product order authorisation sub-process verifies that all orders contain data appropriate to the product being sought and that each ordering party is accurately identified and credentialled (this sub-process draws principally on the data file, PPRODUCT).
The primary product order matching sub-process locates the best possible counterparty(ies) for the ordering party's transaction according to the application promoter-specified “matching rules” embodied in the APP; it does this utilizing three component sub-processes, termed: short-listing of potential counterparties, individual potential-counterparty “pricing” calculations, and counterparty selection.
The “of short-listing of potential counterparties” sub-process component establishes a list of potential counterparties (if any) willing to offer the product sought by the ordering party, upon their receipt from the ordering party of a consideration they deem to be appropriate (this sub-process draws principally on the data-file, PDEAL LIST).
The individual potential-counterparties pricing calculations sub-process component utilises the above-described pricing parameters pre-specified by each short-listed potential counterparty to calculate the “bid” each of them is prepared to make on the ordering-party's product order (or part thereof), and to add these to the potential counterparties short-list file (this sub-process draws principally on the data-file, PSEL PRICE).
The “counterparty selection” sub-process component extracts from the above-described “potential-counterparties short-list” file the best possible counterparty(ies) for the ordering party's transaction, according to the application promoter-specified “matching rules” embodied in the APP, taking into account whatever matching constraints all applicable APP stakeholders may have prespecified. This selection being made, and price bid being within the allowable limits specified by the ordering party, and there being no requirements for manual-approval intervention by any relevant stakeholder, a matched order is deemed to be in existence (this sub-process draws principally on the data-file, PSEL LIMIT).
The matched order confirmation sub-process effectively secures, automatically, the positive agreement of all affected stakeholders to the contract, including confirmation of the product ordering party's ability to immediately pay (or be granted counterparty credit, or ordering party guarantor credit, for) the required contract consideration (and possible other applicable fees). Automatic approvals of contracts are made the CONTRACT APP electronically transferring resources records in the ordering party's applicable consideration/entitlement transfer entity account to the account of the applicable counterparty (See Appendix H for a description of the consideration/entitlement “payment” process). In turn, automatic updates of the counterparty's matching constraints maintained in the file PSEL LIMIT are made.
Upon completion of the above-described processing steps: unmatched order transactions are written to the file, PORD QUEUE, for subsequent match attempts; matched and confirmed order transactions are confirmed to the relevant CONTRACT APP stakeholders (this process drawing principally on the data-file, ADMIN) and are written to the file PORD CONF for subsequent “back-office” processing; and relevant CONTRACT APP stakeholders are notified of rejected orders (again, this process principally on the data-file, ADMIN), records of this being written to the file PORD REJ for subsequent “back-office” processing. A copy of all processing outputs is written to the file, HISTORY.
Process 3
Process 3 handles the receipt and processing of “secondary” risk management contract transactions. Like “primary” risk management contracts, “secondary” risk management contracts are of multiple types various sub-processes of Process 3 handle the receipt and processing of all possible types of these transactions, including product order processing, product price indications, and withdrawals of existing product orders.
“Secondary product orders” constitute the core “secondary” risk management contract transaction type (FIG. 20 provides a summary flow chart of the processing of this transaction type).
“Secondary” product orders incorporate the following key items of information: potential acquiring party identification information; the pre-established Order ID reference to the sought-after primary contract; the potential acquiring party's interest or otherwise in being granted credit by offering parties for the yet-to-be-determined contract acquisition amount; the acquiring party's interest or otherwise in availing themselves of the possible netting and other features of the APP concerned; the acquisition “price” range within which the potential acquiring party is prepared to “pay” for the contract they have specified; other dimensions of the potential acquiring party's needs; and the consideration/entitlement transfer entity accounts from which/to which they wish to have relevant “payments” made/received. The above-described information is, upon receipt, written to—and subsequently processed from—the file SORD NEW.
Three sub-processes are involved in processing secondary product orders—order authorisation, order matching, and matched order confirmation. In case of the anticipated most typical form of order, termed a “normal-automatic” secondary product order these sub-processes function as follows:
The secondary product order authorisation sub-process verifies that all orders contain data appropriate to the contract sought and that each potential acquiring party is accurately identified and credentialled (this sub-process draws principally on the data-file, SPRODUCT).
The secondary product order matching sub-process locates sought-after contract records and, based on the contents of these records, determines whether a “sale” of the position of the specified stakeholder in the contract to the potential acquiring party is possible—in particular, whether the acquisition “price” range within which the potential acquiring party has specified it is prepared to “pay” for the position of the specified current stakeholder is equal to, or in excess of, the “allowable sale price” figure prespecified by the applicable contract stakeholder. If a contract “sale” is found to be possible, and there being no requirements for manual-approval intervention by any relevant stakeholder, a “match” is deemed to have occurred.
The secondary product matched order confirmation sub-process effectively sources, automatically, the positive agreement of all affected stakeholders to the contract position “sale”, including confirmation of the contract acquiring party's ability to immediately pay (or be granted current stakeholder credit, or acquiring party guarantor credit, for) the required “sale price” consideration (and possible other applicable fees). Automatic approvals of such “sales” are made by the CONTRACT APP electronically transferring resources recorded in the acquiring party's applicable consideration/entitlement transfer entity account to the account of the applicable current contract stakeholder.
Upon completion of the above-described processing steps: unmatched order transactions are written to the file, SORD QUEUE, for subsequent match attempts; matched and confirmed order transactions are confirmed by the relevant CONTRACT APP stakeholders (this process drawing principally on the data-file, ADMIN), required records being written to the file SORD CONF for further “back-office” processing as required; and rejected order transactions are similarly notified to the relevant CONTRACT APP stakeholders (again, this process drawing principally on the data-file, ADMIN), required records being written to the file SORD REJ for further “back-office” processing. A copy of all processing outputs is written to the file, HISTORY.
Process 4
Process 4 handles the receipt and processing of “derivative-primary” risk management contract transactions. Like “primary” risk management contracts, “derivative-primary” risk management contracts are of multiple types; various sub-processes of Process 4 handle the receipt and processing of all possible types of these transactions, including product order processing, product price indications, and existing product order withdrawals.
“Product option orders” is one illustrative “derivative-primary” risk management contract transaction type (FIG. 21 provides a summary flow chart of the processing of this transaction type).
“Derivative-primary” product option orders incorporate the following key items of information: ordering party identification information; CONTRACT APP application and product identification information; “other stakeholder involvement” information; the ordering party's desired form of product specification (directly input as entitlement coordinates or as mathematical function(s)); when the order specification is by way of a single-dimensional mathematical function, the parameters of such a function (which can include: the term “X”, the term “Alpha (X)”, the term “Beta (X)”, the term “Gamma (X-1)”; the contract consideration and entitlement “denomination type”, “currency (if applicable)” and “national currency (if applicable)”; the ordering party's interest or otherwise in being granted credit by potential counterparties for the yet-to-be-determined contract option consideration amount; the ordering party's interest or otherwise in availing themselves of the possible netting and collateralisation features of the APP concerned; the consideration “price” range within which the ordering party is prepared to “pay” for their defined product option; miscellaneous other dimensions of the ordering party's needs, and the consideration/entitlement transfer entity accounts from which/to which they wish to have relevant “payments” made/received). Upon its receipt, all of this information is written to—and subsequently processed from—the file DPORD NEW.
Three sub-processes are involved in processing derivative-primary product orders order authorisation, order matching, and matched order confirmation. In the case of the most likely form of the above-mentioned illustrative option order, termed a “normal-automatic” derivative-primary product option order these sub-processes function as follows:
The primary product option order authorisation sub-process verifies that all orders contain data appropriate to the product option being sought and that each ordering party is accurately identified and credentialled (this process draws principally on the data-file, DPPRODUCT).
The primary product option order matching sub-process locates the best possible counterparty(ies) for the ordering party's transaction according to the application promoter-specified “matching rules” embodied in the APP; it does this utilizing three component sub-processes, termed: short-listing of potential counterparties, individual potential option-counterparty “pricing” calculations, and option-counterparty selection.
The “short-listing of potential option-counterparties” sub-process component establishes a list of potential option-counterparties (if any) willing to offer the product option sought by the ordering party, upon their receipt from the ordering party of an option consideration they deem to be appropriate (this sub-process draws principally on the data-file, DPDEAL LIST).
The “individual potential option-counterparties pricing calculations” sub-process component utilises the above-described pricing parameters prespecified by each short-listed potential option-counterparty to calculate the “bid” each of them is prepared to make on the ordering party's product option order (or part thereof), and to add these to the potential option-counterparties short-list file (this sub-process draws principally on the data-file, DPSEL PRICE).
The “option-counterparty selection” sub-process component extracts from the above-described “potential option-counterparties short-list” file the best possible counterparty(ies) for the ordering party's transaction, according to the application promoter-specified “matching rules” embodied in the APP, taking into account whatever matching constraints all applicable APP stakeholders may have prespecified. This selection being made, and the price bid being within the allowable limits specified by the ordering party, and there being no requirements for manual-approval intervention by any relevant stakeholder, a matched option order is deemed to being existence (this sub-process draws principally on the data-file, DPSEL LIMIT).
The matched option order confirmation sub-process effectively secures, automatically, the positive agreement of all affected stakeholders to the options contract, including confirmation of the product-option-ordering party's ability to immediately pay (or be granted counterparty credit, or ordering party guarantor credit, for) the required option product consideration (and possible other applicable fees). Automatic approvals of contracts are made by the CONTRACT APP electronically transferring resources recorded in the ordering party's applicable consideration/entitlement transfer entity account to the account of the applicable counterparty. In turn, automatic updates of the option-counterparty's matching constraints maintained in the file DPSEL LIMIT are made.
Upon completion of the above-described processing steps: unmatched option-order transactions are written to the file, DPORD QUEUE, for subsequent match attempts; matched and confirmed option-order transactions are confirmed to the relevant CONTRACT APP stakeholders (this process drawing principally on the data-file, ADMIN) and are written to the reference file DP MSTR, and the file DPORD CONF for subsequent “back-office” processing; and relevant CONTRACT APP stakeholders are notified of rejected orders (again, this process drawing principally on the data-file, ADMIN), records of this being written to the file DPORD REJ for subsequent “back-office” processing. A copy of all processing outputs is written to the file, HISTORY.
If/when and option-holder wishes to exercise its option over a pre-established contract, it does so by appropriately notifying the CONTRACT APP which, in turn, retrieves the contract record from DPMSTR, effect the necessary additional consideration payments, and writes a new record to PORD CONF for subsequent back office processing. As described above, the appropriate HISTORY and other files are updated in this process.
Process 5
Process 5 handles the receipt and processing of “derivative-secondary” risk Management contract transactions. Like “secondary” risk management contracts, “derivative-secondary” risk management contracts are of multiple types; various sub-processes of Process 5 handle the receipt and processing of all possible types of these transactions, including product order processing, product price indications, and withdrawals of existing product orders.
“Product option orders” is an illustrative “derivative-secondary” risk management contract transaction type (FIG. 22 provides a summary flow chart of the processing of this transaction type).
“derivative-secondary” product option orders incorporate the following key items of information: potential acquiring party identification information; the pre-established Order ID reference to the sought-after primary contract (in relation to which an option is to be purchased or sold); the potential acquiring party's interest or otherwise in being granted credit by offering parties for the yet-to-be-determined option contract acquisition amount; the acquiring party's interest or otherwise in availing itself of the possible netting and other feature of the APP concerned; the acquisition “price” range within which the potential acquiring party is prepared to “pay” for the contract option they have specified; other dimensions of the potential acquiring party's needs; and the consideration/entitlement transfer entity accounts from which/to which they wish to have relevant “payments” made/received. The above-described information is, upon receipt, written to—and subsequently processed from—the file DSORD NEW.
The subprocesses involved in the processing of derivative-secondary product option order are essentially a combination of the processes described above in the case of secondary product orders (Process 3) and derivative-primary product option orders (Process 4). At the completion of the matching process, matched orders are written to the reference file DSMSTR and the file DSORD CONF for subsequent back office processing.
If/when an option holder wishes to exercise its option over a pre-established contract, it does so by appropriate notifying the CONTRACT APP which, in turn, retrieves the contract record from DSMSTR, effects the necessary additional consideration payments, and writes a new record to SORD CONF for subsequent back office processing. As described above, the appropriate HISTORY and other files are updated in this process.
Process 6
Process 6 handles the “back office” management of “matched/confirmed” primary, secondary, derivative-primary, and derivative-secondary risk management contract transactions and transactions handled by Processes 7–9. The process incorporates multiple sub-processes, collectively accessing multiple data files (FIG. 23); primary risk management contract back office processing; secondary risk management contract back office processing; derivative-primary risk management contract back office processing; derivative-secondary risk management contract back office processing; “Process 7” transactions back office processing; “Process 8” transactions back office processing; and “Process 9” transactions back office processing.
In relation to the back-office management of confirmed/matched primary risk management contracts—a number of sub-processes are involved, including: Receipt of the previous operating day's “matured-contract actual product event value” sub-process; “Start-of-day PAYACC management” sub-process; Contract maturity management sub-process; Confirmed contract processing sub-process; Information compilation and distribution sub-process; Information extraction from primary orders sub-process; Contract valuation sub-process; Contract collateralisation payments sub-process; System Access and usage fee determination and payments sub-process; Bilateral obligations netting sub-process; Multilateral obligations netting sub-process; Bilateral payments netting sub-process; multilateral payments netting sub-process; and “end-of-day PAYACC management” sub-process.
Receipt of the previous operating day's “matured-contract actual product event value” details. This sub-process is flowcharted in FIG. 24; it involves the applicable CONTRACT APP receiving “matured-contract actual product event value” details from the relevant product sponsors (external to INVENTCO). The primary data-file, MAT PROD VALUES, is updated with this information. The support data-files, ADMIN, HISTORY, and INFO are similarly updated with applicable information.
“Start-of-day” PAYACC management. This sub-process is flowcharted in FIG. 25; it involves the applicable CONTRACT APP receiving consideration/entitlement “actual account” opening-balances from participating consideration/entitlement transfer entities (external to INVENTCO) (see Process 7 for details). The primary data-files, PAYACC SHADOW and PAYACC FINAL are updated with this information. The support data-files, HISTORY, INFO and ADMIN, are similarly updated with applicable information.
Contract maturity management. This subprocess is flowcharted in FIG. 26; it involves the applicable CONTRACT APP determining and giving effect to primary and related entitlement-transfers to/from applicable CONTRACT APP stakeholders, applicable other INVENTCO stakeholders, where such transfers are principally reflected in entries to the data-file, PAYACC SHADOW. CONTRACT APP determines and gives effect to these transfers, principally by drawing upon product/contract information maintained in the data files, INTREG, MAT PROD VALUES, COLLAT, CREDIT MGMT, BILAT OBLIG NET, and MULTILAT OBLIGNET. These data-files are appropriately updated in the process as are the support data-files, ADMIN, HISTORY TAX/SUB, PAYACC SHADOW and INFO.
Confirmed contract processing. This sub-process, flowcharted in FIG. 27, operates continually throughout each operating day. Details of new matched/confirmed contracts are read from the file PORD CONF and are then time-stamped and written to the file INTREG as two records—one record pertaining to the contract ordering party and the other to the contract counterparty. The support data files, INFO, ADMIN, and HISTORY are appropriately updated in the process.
Information compilation and distribution. This sub-process, flowcharted in FIG. 28, operates continually (beyond a defined operating day), drawing on the data-file INFO. As already described, INFO is updated continually as CONTRACT APP and other INVENTCO events occur, including pertinent AXSCO message information written in the first instance to HISTORY. All relevant INVENTCO stakeholders have access to preauthorised parts of INFO.
Information extraction from primary orders. This sub-process, flowcharted in FIG. 29, is effected after the completion of the defined operating day. Essentially, it involves the single task of processing the data-file, HISTORY, to yield pertinent information for the data-file INFO. One of the most important items of information drawn from HISTORY is (confidential) information on all of the prior day's potential counterparty consideration bid parameters, in particular the data items termed “assessed probabilities of occurrence”. This information yields “market” information for the subsequent contract valuation sub-process.
Contract valuation. This sub-process, flowcharted in FIG. 30, draws principally upon the above-described “markets” information previously written to INFO. Pertinent data from this file is “applied against” all outstanding contracts maintained in INTREG, thereby yielding updated “future product value (FPV)”, “expected value” and “distribution” value information for all contracts and, from this, revaluations of all future entitlement “expected values” and “distribution” values. All these revaluation figures are maintained in INTREG with applicable information also being written to INFO and HISTORY.
Contract collateralisation payments. This sub-process, flowcharted in FIG. 31, draws principally on the data-file INTREG. Following the contract valuation process, this collateralisation process involves relevant INTREG records being read and, depending (amongst other things) on the precalculated “present value” of the expected future entitlement associated with each relevant contract, a calculated portion of the present value of the expected future consideration amount is debited or credited to the PAYACC SHADOW file of the applicable collateralisation trustee entity, and the product ordering party and/or counterparty as is applicable.
Generally, if the most recent precalculated “present value” of the expected future entitlement associated with each relevant contract indicates a negative contract value, and if this negative value exceeds the prior contact valuation figure, the applicable entity's trust account in credited with the funds difference, with the entity's own consideration/entitlement transfer entity account being debited correspondingly. If this negative value does not exceed the prior contract valuation figure, the applicable entity's trust account is debited with the funds difference, with the entity's own consideration/entitlement transfer entity account being credited correspondingly. On the other hand, if the most recent precalculated “present value” of the expected future entitlement associated with each relevant contract indicates a positive contract value, the only collateralisation payment adjustment called for is one in which all funds (if any) in the applicable entity's trust account are transferred to the entity's own consideration/entitlement transfer entity account. In each of the above-described cases, a record of all entries effected is written to the data-file, COLLAT, and a subset of this information is written to the data-files HISTORY and INFO.
System Access and usage fee determination and payments. This subprocess, flowcharted in FIG. 32, deals with the determination and payment of system access and usage fees (as distinct from contract maturity date fee payments). The function draws principally on the data-files ADMIN, and HISTORY. Fee payment parameters are maintained in data-file ADMIN. These parameters are applied against the day's new records already written to HISTORY. Debits and credits for fees so determined are written to PAYACC SHADOW with summary information written to INFO and HISTORY.
Bilateral obligations netting. This subprocess, flowcharted in FIG. 33, effectively maintains an up-to-date matrix of the present values of expected future entitlement (and other) obligations between pairs of participating ordering parties and counterparties (as well as other participating CONTRACT APP and INVENTCO stakeholders), continually adjusted on the basis of required current consideration, entitlement and other payments/receipts as they occur. As required, the function updates the above-described matrix in two stages. First, with the most recent contract revaluation figures contained within INTREG. And second, with the end-of-day payment/receipt amounts contained within PAYACC SHADOW. Consideration/entitlement transfer entity transfers from/to applicable entities are determined (according to the application-promoter specified parameters for so doing) on the basis of whether or not any/all of the adjusted bilateral present value figures are in excess of their allowable limits. These entries are written to PAYACC SHADOW, with the data-files BILAT OBLIG NET, INTREG, HISTORY, and INFO being subsequently updated.
Multilateral obligations netting. This subprocess, flowcharted in FIG. 34, is essentially the same as the bilateral netting function except that a specified “clearing/trustee” entity is effectively interposed between all bilateral counterparties and, as such, netted obligations are only between the specified “clearing house/trustee” entity and each participating entity.
Bilateral payments netting. This subprocess, flowcharted in FIG. 35, is independent of the above-described bilateral and multilateral obligations netting subprocesses. The subprocess operates by producing a matrix of bilaterally netted payments/receipts based on records contained in the data-file, PAYACC SHADOW. Single netted payment/receipt figures are then rewritten to PAYACC SHADOW, with the data-files BILAT PYMTS NET, ADMIN, HISTORY and INFO being subsequently updated.
Multilateral payments netting. Like bilateral payments netting, this subprocess, flowcharted in FIG. 36, is independent of the above-described bilateral and multilateral obligations netting subprocesses. The subprocess operates by producing a matrix of bilaterally netted payments/receipts to/from the applicable “clearing house/trustee” entity based on records contained in the dats-file, PAYACC SHADOW. Single netted payment/receipt figures (to/from the “clearing house/trustee” entity) are then rewritten to PAYACC SHADOW, with the data-files MULTILAT PYMTS NET, ADMIN, HISTORY and INFO being subsequently updated.
“End-of-day” PAYACC management. This subprocess, flowcharted in FIG. 37, involves a three-stage process. First, the preparation of inter-consideration/entitlement transfer entity “balancing” transactions. Second, the transfer of the final contents of the PAYACC SHADOW data-file to the data-file, PAYACC FINAL. And third, the electronic transmission of the contents of PAYACC FINAL to the applicable consideration/entitlement transfer entities (external to INVENTCO). In turn, the subsidiary data-files, ADMIN, HISTORY, and INFO are updated.
Process 7
Process 7 handles non-CONTRACT APP-related obligation transfers between applicable INVENTCO stakeholders, that is, the transfer of ownership title over “assets” registered by INVENTCO—typically matched/confirmed contracts (recorded as CONTRACT APP INTREG records). and consideration/entitlement fransfer entity resources (recorded as PAYACC records). Both of the above-mentioned items have value to their holder. This process enables holders of these items to assign or lend any portion of their holdings to others at their will through initiating the appropriate transactions as NCAROT TRANS. The process accesses a relatively small number of data files (see FIG. 38). NCAROT TRANS received result in appropriate updates to the primary data-files, PAYACC SHADOW and INTREG. In turn, the subsidiary data files, HISTORY, ADMIN and INFO are updated.
Process 8
Process 8 (flowcharted in FIG. 39) handles CONTRACT APP (and other INVENTCO) stakeholder shared-access to specialist systems to assist them decide how best to interface with one or more aspects of INVENTCO. In the case of CONTRACT APP stakeholders, the most likely users of this process, one collection of such specialist systems are termed “decision support systems”. The purpose of these systems is to guide a user-stakeholder as to how it should react to/deal with the continually changing circumstances within the CONTRACT APP with which they are dealing. Different clusters of systems are applicable for different CONTRACT APP stakeholders. These systems involve a hierarchy of potentially any number of value-added components.
An example of one such system, useful to primary product ordering parties, is a system which helps an ordering party determine which of its prespecified, but as yet unmatched, orders it should withdraw and which of its potential new product orders it should submit. This system is in the form of a “utility optimization” mechanism which seeks to identify the best possible composition of outstanding orders (and thus, which existing, unmatched orders should be withdrawn and which new orders should be submitted) based on two things. First, an objective function which seeks to minimize the difference between a weighted sum of actual and desired values of a series of attributes (involving single or multiple products, covering the ordering party's “real business exposure” to each product, the ordering party's portfolio of contracts which have been “matched” but are not yet confirmed, orders which have been submitted but not yet matched, and potential yet-to-be-submitted orders (collectively termed “buyer's objective portfolio”), these attributes including, amongst other things: the “expected value” of the objective portfolio; the “standard deviation” of the objective portfolio; the “incremental cash outflow” attribute of the objective portfolio; the “maximum absolute loss” attribute of the objective portfolio; the “expected loss” attribute of the objective portfolio; the “implied minimum return on investment” of the objective portfolio; and the “implied expected return on investment” of the objective portfolio. And second, a series of constraints specifying, amongst other things: the required “minimum values” of each objective function attribute; and required minimum product-shares in the ordering party's overall product portfolio. The mathematical form of this “optimization” could take any of a number of alternative forms.
An optimization mechanism similar to the one described above can also aid potential counterparties in defining their pricing parameters for application against incoming product orders.
Effectively, systems of the above-described type are collectively maintained as a software “library” within applicable CONTRACT APP (although they may also be loaned by VIRPRO-authorised entities independent of INVENTCO and/or acquired by VIRPRO-authorised parties whether they are INVENTCO stakeholders or not). CONTRACT APP (and other INVENTCO) stakeholder requests to make use of software within this library are received by way of records in the file, SSA, TRANS. These requests result in the appropriate records in the file SSA being accessed and made available for use via AXSCO and the applicable entity's authorised electronic link to INVENTCO. Appropriate records of the utilization of SSA records are written to the data-files HISTORY, ADMIN and INFO.
Process 9
Process 9 (flowcharted in FIG. 40) handles CONTRACT APP (and other INVENTCO) stakeholder shared-access to a range of INVENTCO-facilitated value added services. These services can include: accounting, reconciliation, and information services; value added information reseller services; financial services of multiple types; and data processing and telecommunications services. Effectively, software relating to these services is maintained as a software “library” within the applicable CONTRACT APP (although they may also be loaned by VIRPRO-authorised entries independent of INVENTCO and/or acquired by VIRPRO-authorised parties whether they are INVENTCO stakeholders or not). CONTRACT APP (and other INVENTCO) stakeholder requests to make use of software within this library are received by way of records in the file, VAS TRANS. These requests in the appropriate records in the file VAS being accessed and made available for use via AXSCO and the applicable entity's authorised electronic link with INVENTCO. Appropriate records of the utilization of VAS records are written to the data-files HISTORY, ADMIN and INFO.
Process 2 Variables and Data Files
Listed below is the file name and description therefor.
Order Data Fields
OID Unique identification assigned by CONTRACT APP to every new order submitted.
BID Ordering part identification.
BREF Ordering party's own reference for this order.
PID Order filed specifying the required product.
PMAT Product maturity date.
PC/ED Product consideration/entitlement denomination.
PCUR Product currency denomination.
PNCUR Product national currency denomination.
PPARAM Product specification parameters (eg. minimum value (PMIN), maximum value (PMAX), and the step size (PSTEP)).
MAXCONSID Maximum consideration the ordering party will pay for this contract.
PAYFUNC Pay-off function type, contingent on one or more index variables.
PAYPARAM Parameters associated with the PAYFUNC.
ACC CONSID The ordering party account the consideration is to be paid from. Implied is the account consideration/entitlement, currency, national currency.
ACC ENTITL The ordering party account the contract entitlement is to be paid into. Implied is the account consideration/entitlement, currency, national currency.
RET LIM Retention time limit for the order, which sets an expiration time for the order whilst remaining un-matched.
OPRICE Price calculated and selected for this order (this value will be the matching price).
SPRICE Counterparty identification with which the order was matched.
PAY TRAN Payment transaction number.
DCID Defined circumstances identification.
OANON Anonymous flag, set by the ordering party when seeking to avoid manual authorisation requests by other stakeholders.
OMANUAL Manual authorisation request flag. If set, the ordering party requires manual authorisation before the matched order is fully confirmed.
DTID Deal type identification which codes a combination of miscellaneous flags such as collateralisation, bilateral and multilateral netting requirements.
Counterparty Short List Arrays
PRICEFUNC(SID) Pricing function: function type and associated parameters.
ELFUNC(SID) Expected loss determination function: function type and associated parameters.
EVFUNC(SID) Expected value determination function: function type and associated parameters.
CR(SID) Commission rate to be used for the current defined circumstances.
DR(SID) Discount rate to be used for the current defined circumstances.
PRICE(SID) price calculated by each counterparty.
EL(SID) Expected loss calculated for the current order by each counterparty.
AL(SID) Absolute loss calculated for the current order by each counterparty.
EV(SID) Expected values determined for the current order by each counterparty.
MCC(SID) maximum composition any contract (as an expected loss) can have of the entire portfolio.
MC(SDID) maximum composition the product (as an expected loss) can have of the entire portfolio.
ELL1(SID) Order expected loss limit.
ELL2(SID) Expected loss limits set by the counterparty for the product.
ELL3(SID) Expected loss limits set by the counterparty for equivalent maturity date products.
ELL4(SID) Expected loss limits set by the counterparty for the same month maturity products.
ELL5(SID) Expected loss limits set by the counterparty for orders in all products.
CEL2(SID) Current accumulated expected losses for the product.
CEL3(SID) Current accumulated expected losses for equivalent maturity date products.
CEL4(SID) Current accumulated expected losses for same month maturity products.
CEL5(SID) Current accumulated expected losses for orders in all products.
ALL1(SID) Absolute loss limit function for each contract.
ALL2(SID) Absolute loss limit function set for the product.
CAL2(SID) Current absolute limit function accumulated for the product.
EVL1(SID) Expected value limit on each order.
C-C/EDXCHANG(SID) Counterparty consideration/entitlement denomination exchange rates which convert the ordering party's consideration denomination of ACC CONSID (and MAXCONSID) into the product's consideration denomination.
C-CXCHANG(SID) Counterparty currency exchange rates which convert the ordering party's currency of ACC CONSID (and MAXCONSID) into the product's denominated currency.
C-NCXCHANG(SID) Counterparty national currency exchange rates which convert the ordering party's national currency of ACC CONSID (and MAXCONSID) into the product's denominated national currency.
E-C/EDXCHANG(SID) Counterparty consideration/entitlement denomination exchange rates which convert the ordering party's consideration denomination of ACC ENTITL into the product's consideration denomination.
E-CXCHANG(SID) Counterparty currency exchange rates which convert the ordering party's currency of ACC ENTITL into the product's denominated currency.
E-NCXCHANG(SID) Counterparty national currency exchange rates which convert the ordering party's national currency of ACC ENTITL into the product's denominated national currency.
Miscellaneous Variables
BPRICE Best price selected from the PRICE(SID) array.
SID The currently selected or viewed counterparty identification.
INDEX Index counter variable required for calculating order prices.
P1 Value calculated by a pricing function at an index point.
P2 Value calculated by a pay-off function at an index point.
Master Files
File Description/Contents
PORD NEW Holds details of all new orders submitted by ordering parties.
BID Ordering party identification.
BREF Ordering party's own reference for this order.
PID Order field specifying the required product.
MAXCONSID Maximum consideration the ordering party will pay for this contract.
PAYFUNC Pay-off function type, contingent on one or more index variables.
PAYPARAM Parameters associated with the PAYFUNC.
ACC CONSID The ordering party account the consideration is to be paid from.
ACC C/ED The ordering party account consideration/entitlement.
ACC CUR The ordering party account currency.
ACC NCUR The ordering party account national currency.
ACC ENTITL The ordering party the contract entitlement is to be paid into.
RET LIM Retention time limit for the order, which sets an expiration time for the order whilst remaining un-matched.
OANON Anonymous flag, set by the ordering party when seeking to avoid manual authorisation requests by other stakeholders.
OMANUAL Manual authorisation request flag. If set, the ordering party requires manual authorisation before the matched order is fully confirmed.
DTID Deal type identification which codes a combination of miscellaneous flags such as collateralisation, bilateral and multilateral netting requirements.
PORD QUEUE This master filed details of orders which have already been authorised, and have attempted to match once before. Fields as in ORD NEW plus some additional fields:
OID Unique identification assigned by P-CONTRACT to every new order submitted.
PMAT Product maturity date.
C/ED Product consideration/entitlement denomination.
PCUR Product currency denomination.
PNCUR Product national currency denomination.
PPARAM Product specification parameters (eg. minimum value (PMIN), maximum value (PMAX), and the step size (PSTEP)).
DCID Defined circumstances identification.
PORD REJ All rejected orders reside in this field. Fields as in ORD QUEUE plus some additional fields:
ERRCODE Error code indicating why the order was rejected.
PORD CONF When an order is matched and fully confirmed, full details are stored in this master file. Fields as in ORD QUEUE plus some additional fields:
OPRICE Price calculated and selected for this order. This value will be the matching price.
SPRICE Counterparty identification with which the order was matched.
PAY TRAN Payment transaction number.
PPRODUCT This master file holds information (definition details) about each product known to the system:
PID Product identification.
PMAT Product maturity date.
PC/ED Product consideration/entitlement denomination.
PCUR Product currency denomination.
PNCUR Product national currency denomination.
PPARAM Product specification parameters (eg. minimum value (PMIN), maximum value (PMAX), and the step size (PSTEP)).
PDEAL LIST This file holds a list of the ordering party/product/counterparty tuples of allowable deals to occur. Thus by specifying an ordering party (BID) and product (PID), a list of counterparties who are prepared to enter into a deal with the ordering party/product combination, can be obtained:
BID Ordering party identification
PID Product identification
SID Counterparty identification
ANON All stakeholder identifications requiring anonymous confirmation.
MANUAL All stakeholder identifications requiring manual authorisation
PSEL DC This file allows counterparties to define identifications for sets of potential order parameters.
Any order data field can be used to define an order.
Each defined circumstance identification is then used to set unique pricing parameters:
DCID Defined circumstances identification.
BID Ordering party identification
PAYFUNC Pay-off function type, contingent on one or more index variables.
PAYPARAM Parameters associated with the PAYFUNC.
ACC CONSID The ordering party account the consideration is to be paid from.
ACC ENTITL The ordering party account the contract entitlement is to be paid into.
DTID Deal type identification.
PC/ED Product consideration/entitlement denomination.
PCUR Product currency denomination.
PNCUR Product national currency denomination.
PSEL PRICE Contains all counterparty pricing parameters, including commission rates, discount rates and exchange rates:
SID Counterpart identification
PID Product identification
DCID Defined circumstances identification
PRICEFUNC Pricing function: function type and associated parameters.
CR Commission rate to be used for the current ordering party in the current product.
DR Discount rate to be used for the current ordering party in the current product.
C-C/EDXCHANG Counterparty consideration/entitlement denomination exchange rates which convert the ordering party's consideration denomination of ACC CONSID (and MAXCONSID) into the product's consideration denomination.
C-CXCHANG Counterparty currency exchange rates which convert the ordering party's currency of ACC CONSID (and MAXCONSID) into the product's denominated currency.
C-NXCHANG Counterparty national currency exchange rates which convert the ordering party's national currency of ACC CONSID (and MAXCONSID) into the product's denominated national currency.
E-C/EDXCHANG Counterparty consideration/entitlement denomination exchange rates which convert the ordering party's consideration denomination of ACC ENTITL into the product's consideration denomination.
E-CXCHANG Counterparty currency exchange rates which convert the ordering party's currency of ACC CONSID into the product's denominated currency.
E-NCXCHANG Counterparty national currency exchange rates which convert the ordering party's national currency of ACC ENTITL into the product's denominated national currency.
PSEL LIMIT Holds all counterparty portfolio limits and current accumulated exposures in the various mathematical forms allowed by the system:
SID Counterparty identification
PID Product identification
DATE Product maturity date.
MCC Maximum composition any contract (as an expected loss) can have of the entire portfolio.
MC Maximum composition the product (as an expected loss) can have of the entire portfolio.
ELL1 Order expected loss limit.
ELL2 Expected loss limits set by the counterparty for the product.
ELL3 Expected loss limits set by the counterparty for equivalent maturity date products.
ELL4 Expected loss limits set by the counterparty for same month maturity products.
ELL5 Expected loss limits set by the counterparty for orders in all products.
CEL2 Current accumulated expected losses for the product.
CEL3 Current accumulated expected losses for equivalent maturity date products.
CEL4 Current expected losses for same month maturity products.
CEL5 Current accumulated expected losses for orders in all products.
ALL1 Absolute loss limit function for each contract.
ALL2 Absolute loss limit function set for the product.
CAL2 Current absolute limit function accumulated for the product.
EVL1 Expected value limit on each order.
PAYACC Payment accounts for all registered stakeholders (inc. balances and previous SHADOWtransactions), are stored in this master file:
ID Stakeholder identification.
NO Account number.
ACC C/ED The ordering party account consideration/entitlement.
ACC CUR The ordering party account currency.
ACC NCUR The ordering party account national currency.
BALANCE Available funds.
GID Stakeholder identification guaranteeing the account.
Risk Management Contracts
Risk management contracts is a term used to refer to one type of contractual obligation which can be, but does not need to be, traded/exchanged/transferred, and subsequently processed and settled, using an INVENTCO system. Risk management contracts consist of “primary” isk management contracts; “secondary” risk management contracts; “derivative-primary” risk management contracts; and “derivative-secondary” risk management contracts.
“Primary ” risk management contracts can be “simple” and “complex” in nature (“simple” contracts being derivatives of “complex” contracts).
A “simple” primary risk management contract is a tradeable or untradeable contract conveying an obligation on an entity, upon that entity being granted a consideration another entity (or a pledge to be granted a consideration by the other entity), to make an entitlement to that other entity depending on the value of a defined phenomenon, determined at a defined time in the future.
A “complex” primary risk management contract is a tradeable or untradeable contract conveying an obligation on either or both of two entities, upon one entity [usually] being granted a consideration by the other entity (or accepting a pledge to be granted a consideration by the other entity), to make an entitlement to pay/receive an entitlement from on another, depending on the value of a defined phenomenon, determined at a defined time in the future. A “complex” contract may, in turn, be “basic” or “advanced” in nature: a “complex-basic+ contract being one that does not involve ordering party and/or matched order counterparty “collateralisation payments” to a third-party trustee or clearing entity during the life of a contract; and a “complex-advanced” contract being one that does involve ordering party and/or matched order counterparty “collateralisation payments” to a third-party trustee or clearing entity during the life of the contract.
“Secondary” risk management contracts are pre-existing “primary” risk management contracts offered for trade (individually or as a portfolio) by a “risk-counterparty” stakeholder to the underlying contract.
“Derivative-primary” risk management contracts are options contracts, or futures contracts, or forward contracts, or forward rate agreements, or swaps, or like financial instruments based on specified, but yet-to-be-established, primary risk management contracts.
“Derivative-secondary” risk management contracts are options contracts, or futures contracts, or forward contracts, or forward rate agreements, or swaps, or like financial instruments based on pre-existing primary risk management contracts (which may have been traded since they were first established), including instruments based on: specified, but yet-to-be established, secondary risk management contracts; and the intended tertiary trading/exchange/transfer of specified, established, secondary risk management contracts.

## Claims

1. A data processing system to enable the exchange of an obligation between parties, the system comprising:
a data storage unit having stored therein information about a shadow credit record and shadow debit record for a party, independent from a credit record and debit record maintained by an exchange institution; and
a computer, coupled to said data storage unit, that is configured to (a) receive a transaction; (b) electronically adjust said shadow credit record and/or said shadow debit record in order to effect an exchange obligation arising from said transaction, allowing only those transactions that do not result in a value of said shadow debit record being less than a value of said shadow credit record; and (c) generate an instruction to said exchange institution at the end of a period of time to adjust said credit record and/or said debit record in accordance with the adjustment of said shadow credit record and/or said shadow debit record, wherein said instruction being an irrevocable, time invariant obligation placed on said exchange institution.

2. The data processing system of claim 1, wherein said exchange obligation arises out of a transaction linked to a share price.

3. The data processing system of claim 1, wherein said exchange obligation arises out of a transaction linked to a weather event.

4. The data processing system of claim 1, wherein said exchange obligation arises out of a transaction linked to a market event.

5. The data processing system of claim 1, wherein said exchange obligation involves the transfer of shares in financial or physical assets.

6. The data processing system of claim 1, wherein said exchange obligation involves a wager.

7. The data processing system of claim 1, wherein said exchange obligation involves the transfer of a commodity.

8. The data processing system of claim 1, wherein said exchange obligation arises out of a transaction involving money for goods, services, promises, credits or warrants.

9. The data processing system of claim 1, wherein said period of time is a part of a day.

10. The data processing system of claim 1, wherein each said adjustment takes place in chronological order.

11. The data processing system of claim 1, wherein said instruction represents one or more credits and/or one or more debits netted throughout a period for said party with respect to transactions of that period of time.

12. The data processing system of claim 1, wherein said exchange institution is a credit card company.

13. The data processing system of claim 1, wherein said exchange institution is a debit card company.

14. The data processing system of claim 1, wherein said exchange institution is a bank.

15. The data processing system of claim 1, wherein said exchange institution is a central bank.

16. The data processing system of claim 1, wherein said exchange institution is a guarantor offering credit to one or more parties involved in said exchange obligation.

17. The data processing system of claim 1, wherein said exchange institution is a party offering credit to one or more other parties involved in said exchange obligation.

18. The data processing system of claim 1, wherein said exchange obligation arises out of a currency exchange transaction.

19. The data processing system of claim 1, wherein two or more exchange institutions operate in different time zones.

20. The data processing system of claim 1, wherein two or more exchange institutions have different account processing cycles.

21. The data processing system of claim 1, wherein said transaction arises out of a collateralization payment obligation.

22. The data processing system of claim 1, wherein said data storage unit has stored therein a balance for said shadow credit record and/or said shadow debit record obtained from said exchange institution.

23. The data processing system of claim 1, wherein at least one credit record and one debit record is maintained with another exchange institution.

24. The data processing system of claim 23, wherein said another exchange institution operates in a different time zone than said exchange institution.

25. The data processing system of claim 23, wherein said another exchange institution has a different account processing cycle than said exchange institution.

26. The data processing system of claim 1, wherein said exchange institution is a non-bank clearing house or depository.

27. The data processing system of claim 1, further comprising means for allowing said party to acquire an item from another party, wherein the exchange obligation relates to said item.

28. A data processing system to enable the exchange of an obligation between parties, the system comprising:
a data storage unit having stored therein information about a shadow record for a first party, independent from an account maintained by an exchange institution; and
a computer, coupled to said data storage unit, that is configured to (a) receive a transaction; (b) electronically adjust said shadow record in order to effect an exchange obligation arising from said transaction, allowing only those transactions that do not result in a value of said shadow record being less than a zero; and (c) generate an instruction to said exchange institution at the end of a period of time to adjust said account in accordance with the adjustment of said shadow record, wherein said instruction being an irrevocable, time invariant obligation placed on said exchange institution.

29. The data processing system of claim 28, wherein the account pertains to shares in financial or physical assets.

30. The data processing system of claim 28, wherein the account pertains to participation rights in wagers.

31. The data processing system of claim 28, wherein the account pertains to goods.

32. The data processing system of claim 28, wherein the account pertains to services.

33. The data processing system of claim 28, wherein the account pertains to central bank exchange settlement account deposits.

34. The data processing system of claim 28, wherein the account pertains to financial instrument deposits.

35. The data processing system of claim 28, wherein the account pertains to credit extended to/from a party or to/from a guarantor of a party.

36. The data processing system of claim 28, wherein the account includes an overdraft or line-of-credit with said exchange institution.

37. The data processing system of claim 28, wherein said first party holds one or more accounts with more than one exchange institution.

38. The data processing system of claim 28, wherein the system and exchange institution are legally and/or geographically domiciled in different countries.

39. The data processing system of claim 28, wherein said first party is a buyer and a second party is a seller.

40. The data processing system of claim 28, further comprising debiting and/or crediting said shadow record based on said transaction.

41. The data processing system of claim 28, wherein said exchange obligation arises out of a collateralization payment obligation.

42. The data processing system of claim 28, wherein said transaction involves a weather event.

43. The data processing system of claim 28, wherein said transaction involves a market event.

44. The data processing system of claim 28, wherein said transaction involves a wager.

45. The data processing system of claim 28, wherein said transaction involves an exchange of money for goods, services, promises, credits or warrants.

46. The data processing system of claim 28, wherein said exchange institution is a credit card company.

47. The data processing system of claim 28, wherein said exchange institution is a debit card company.

48. The data processing system of claim 28, wherein said exchange institution is a party offering credit to one or more other parties involved in said exchange obligation.

49. The data processing system of claim 28, wherein said data storage unit has stored therein a balance for said shadow record obtained from said exchange institution.

50. The data processing system of claim 28, wherein a second party maintains an account with an exchange institution that is different from said exchange institution that maintains the account for said first party.

51. The data processing system of claim 50, wherein two or more exchange institutions operate in different time zones.

52. The data processing system of claim 50, wherein two or more exchange institutions have different account processing cycles.

53. The data processing system of claim 28, wherein said period of time is a part of a day.

54. The data processing system of claim 28, wherein said exchange obligation arises out of a currency exchange transaction.

55. The data processing system of claim 28, wherein said instruction represents adjustments netted throughout a period of time.

56. The data processing system of claim 28, wherein said exchange institution is a bank.

57. The data processing system of claim 28, wherein said exchange institution is a central bank.

58. The data processing system of claim 28, wherein two or more exchange institutions have different account processing cycles.

59. The data processing system of claim 28, further comprising means for allowing said first party to acquire an item from another party, wherein the exchange obligation relates to said item.

60. A data processing system to enable the exchange of a payment obligation of a currency exchange transaction between banks, the system comprising:
a data storage unit having stored therein information about a shadow credit record and shadow debit record for a bank, independent from a credit record and debit record maintained by a central bank; and
a computer, coupled to said data storage unit, that is configured to (a) receive a currency exchange transaction; (b) electronically adjust said shadow credit record and/or said shadow debit record in order to effect an exchange obligation arising from said currency exchange transaction, allowing only those currency exchange transactions that result in a net positive shadow record balance; and (c) generate an instruction periodically to said central bank to adjust said credit record and/or said debit record in accordance with the adjustment of said shadow credit record and/or said shadow debit record, wherein said instruction being an irrevocable, time invariant obligation placed on said central bank.

61. The data processing system of claim 60, wherein each said adjustment takes place in chronological order.

62. The data processing system of claim 60, wherein said data storage unit has stored therein a balance for said shadow credit record and/or said shadow debit record obtained from said central bank.

63. The data processing system of claim 60, wherein said instruction is provided at an end of a processing cycle.

64. A data processing system to enable a purchase between a buyer and a seller, the system comprising:
a data storage unit having stored therein information about a shadow record for a buyer or a seller, independent from an account maintained by a bank; and
a computer, coupled to said data storage unit, that is configured to (a) receive a transaction; (b) electronically adjust said shadow record in order to effect a purchase arising from said transaction between said buyer and said seller, allowing only those purchases that do not result in a value of said shadow record being less than zero; and (c) generate an instruction to said bank at the end of a period of time to adjust said account in accordance with the adjustment of said shadow record, wherein said instruction being an irrevocable, time invariant obligation placed on said bank.

65. The data processing system of claim 64, wherein said data storage unit has stored therein a balance for said shadow record obtained from said bank.

66. The data processing system of claim 64, wherein said period of time is a part of a day.

67. The data processing system of claim 64, further comprising means for allowing said buyer to acquire an item from said seller, wherein the purchase relates to said item.

68. A data processing system to enable the exchange of an obligation between parties, the system comprising:
a data storage unit having stored therein (a) information about a first account for a first party, independent from a second account maintained by a first exchange institution, (b) information about a third account for a second party, independent from a fourth account maintained by a second exchange institution; and
a computer, coupled to said data storage unit, that is configured to (a) receive a transaction; (b) electronically adjust said first account and said third account in order to effect an exchange obligation arising from said transaction between said first party and said second party after ensuring that said first party and/or said second party have adequate value in said first account and/or said third account, respectively; and (c) generate an instruction to said first exchange institution and/or said second exchange institution to adjust said second account and/or said fourth account in accordance with the adjustment of said first account and/or said third account, wherein said instruction being an irrevocable, time invariant obligation placed on said first exchange institution and/or said second exchange institution.

69. The data processing system of claim 68, wherein said first and/or second exchange institution is a central bank.

70. The data processing system of claim 69, wherein said exchange obligation involves currency.

71. The data processing system of claim 70, wherein said first exchange institution and said second exchange institution operate in different time zones.

72. The data processing system of claim 68, wherein said first exchange institution and said second exchange institution are the same.

73. The data processing system of claim 68, wherein said second account and said fourth account are the same account.

74. The data processing system of claim 68, wherein said exchange obligation involves currency.

75. The data processing system of claim 68, wherein said first and/or second exchange institution is a non-bank clearing house or depository.

76. The data processing system of claim 68, wherein adequate value requires that said first account and/or said third account have a positive balance.

77. The data processing system of claim 68, wherein said period of time is a part of a day.

78. The data processing system of claim 68, wherein said instruction to said first exchange institution and/or said second exchange institution represents adjustments to said first and said third account netted throughout a period of time.

79. The data processing system of claim 68, further comprising means for allowing said first party to acquire an item from said second party, wherein the exchange obligation relates to said item.

80. A data processing system to enable a purchase between a first party and a second party, the system comprising:
a data storage unit having stored therein information about a first account for the first party or the second party, independent from a second account maintained by a bank; and
a computer, coupled to said data storage unit, configured to enable the purchase, including (a) electronically adjusting said first account in order to effect the purchase between said first party and said second party, allowing only those purchases that do not result in a value of said first account being less than zero; and (b) generating an instruction to said bank to adjust said second account in accordance with the adjustment of said first account, wherein said instruction being an irrevocable, time invariant obligation placed on said bank.

81. The data processing system of claim 80, wherein said data storage unit has stored therein a balance for said first account obtained from said bank.

82. The data processing system of claim 80, wherein said instruction is generated at the end of a day.

83. The data processing system of claim 80, wherein said first account holds funds for said first party and said second party.

84. The data processing system of claim 80, further comprising means for allowing said first party to acquire an item from said second party, wherein said purchase relates to said item.