Computer-based system and method for confirming failed trades of securities

• US 20050216394A1
• Filed: 05/18/2005
• Published: 09/29/2005
• Est. Priority Date: 12/16/2003
• Status: Abandoned Application

• Current Assignee: Chapdelaine MBS LLC
• Original Assignee: Chapdelaine MBS LLC
• Inventors: Fiorentino, James, Monteleone, Leonard C.
• Application Number:
  US11/131,287
• Publication Number:
  US 20050216394A1
• Time in Patent Office: Days
• US Class Current: 705/37
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

The present invention provides a novel system and method for confirming failed trades. In securities trading, and particularly mortgage backed securities trading, there can be a desire to provide market liquidity by allowing trading of securities by parties, even where party does not actually have the securities necessary to satisfy the trade, on the view that the party will acquire the necessary securities to satisfy the trade in advances of the settlement date. However, market instability can result from actual failures to satisfy the trade. The present system and method provide a means for reducing such instability by confirming such failed trades.

Claims

1. A computer-based method for confirming failed trades comprising:

receiving data representing fail information from a plurality of traders, said fail information identifying a plurality of trades that failed to settle;

matching corresponding portions of said fail information between said traders;

generating a fail confirmation report reporting said corresponding portions to respective ones of said traders.

2. The method of claim 1 further comprising the step of validating said fail information prior to performing said matching step.

3. The method of claim 2 wherein said validating step comprises, for each record in said fail information:

determining whether a format of said record is recognized;

rejecting said record if said format is not recognized;

determining, if said format is recognized, whether said record is standardized;

performing standardization operation on said record if said record is not recognized.

4. The method of claim 3 wherein said standardization operation is performed on a contra party identifier within said fail information, said standardization operation comprises the steps of:

accessing a plurality of pointers associated with the one of said trader'"'"'s that originated said fail information;

locating said contra party identifier corresponding to one of said pointers;

substituting said contra party identifier with a standardized contra party identifier corresponding to said one of said pointers.

5. The method of claim 1 wherein said matching step comprises the steps of:

accessing a first set of said fail information respective to a first one of said traders;

accessing a first record within said first set;

accessing a second set of fail information respective to a second one of said traders;

searching said second set for a second record having trading characteristics substantially corresponding to said first record;

recording a failed trade between said second record to said first record.

6. The method of claim 5 wherein said records include a CUSIP;

a contra party identifier;

a net proceeds and a buy/sell indicator for a particular failed trade.

7. The method of claim 6 wherein, as part of said searching step, said records have identical CUSIPs, opposite contra party identifiers, substantially equal net proceeds and opposite buy/sell indicators.

8. The method of claim 7 wherein said net proceeds are within twenty dollars of each other.

9. The method of claim 5 wherein said records include a CUSIP;

a contra party identifier;

at least one of a trade date and a settlement date, and a buy/sell indicator for a particular failed trade.

10. The method of claim 9 wherein, as part of said searching step, said records have identical CUSIPs, opposite contra party identifiers, substantially equal dates and opposite buy/sell indicators.

11. The method of claim 5 comprising the additional steps of:

removing said first and said second records from said sets of fail information;

repeating said foregoing steps for at least a portion of remaining records in said fail information.

12. A fail confirmation engine implemented in a computing environment including at least one processing unit, random access memory, a storage device and a network interface all interconnected;

said at least one processing unit operable to receive fail information from workstations connected to said network interface;

said at least one processing unit operable to examine said fail information and match failed trades between said fail information files;

said at least one processing unit further operable to generate fail-confirmations from said matched failed trades and for passing said fail confirmations to back to respective workstations.

13. The engine of claim 12 wherein said processing unit is operable to execute an interface object for receiving said fail information and for passing said fail confirmations back to said workstations;

said processing unit further operable to execute a matching object to examine said fail information and match said failed trades.

14. The engine of claim 13 wherein said processing unit is further operable to execute a preprocessing object for examining said received fail information;

rejecting records in said received fail information that are not recognizable; and

, if necessary, standardizing said received fail information where said received fail information is non-standardized.

15. The engine of claim 14 wherein said preprocessing object is operable to examine each record in said fail information and determines whether a format of said record is recognized;

reject said record if said format is not recognized;

determine, if said format is recognized, whether said record is standardized;

perform a standardization operation on said record if said record is not recognized.

16. The engine of claim 15 wherein said standardization operation is performed on a contra party identifier within said fail information, said standardization operation comprises the steps of:

accessing a plurality of pointers associated with the one of said trader'"'"'s that originated said fail information;

locating said contra party identifier corresponding to one of said pointers;

substituting said contra party identifier with a standardized contra party identifier corresponding to said one of said pointers.

17. The engine of claim 13 wherein said matching object is operable to access a first set of said fail information respective to a first one of said traders;

access a first record within said first set;

access a second set of fail information respective to a second one of said traders;

search said second set for a second record having trading characteristics substantially corresponding to said first record; and

record a failed trade between said second record to said first record.

18. The engine of claim 17 wherein said records include a CUSIP;

a contra party identifier;

a net proceeds and a buy/sell indicator for a particular failed trade.

19. The engine of claim 18 wherein, as part of said search, said records have identical CUSIPs, opposite contra party identifiers, substantially equal net proceeds and opposite buy/sell indicators.