REGISTRY OF U3 IDENTIFIERS

• US 20120185373A1
• Filed: 01/26/2012
• Published: 07/19/2012
• Est. Priority Date: 10/14/2005
• Status: Abandoned Application

• Current Assignee: Financial Intergroup Holdings Limited
• Original Assignee: Financial Intergroup Holdings Limited
• Inventors: Grody, Allan D.
• Application Number:
  US13/359,367
• Publication Number:
  US 20120185373A1
• 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

An identifier for an entity is generated by receiving, at a participant computer, a prefix from a regulatory entity; receiving, at the participant computer, a suffix from a market participant; and appending, by the participant computer, the prefix to the suffix to generate the identifier. The identifier may be sent from the participant computer to a name server computer that is part of a publicly accessible network of computers

Claims

1-2. -2. (canceled)

3. A method for processing a financial transaction, comprising:

providing, by a computer at a central source operating according to a computer program, initial reference data for the financial transaction to a first party for storage in a first data repository and to a second party for storage in a second data repository, the first data repository being different from the second data repository,

receiving, by the central source computer, a first order from the first party, the first order created from the initial reference data by the first party,

generating, by the central source computer, a first unique tag based on the first order,

associating, by the central source computer, the first unique tag with the first order to create a validated first order,

storing the validated first order at the central source computer,

sending, by the central source computer, the validated first order to the first party,

receiving, by the central source computer, a second order from the second party, the second order created from the initial reference data by the second party,

generating, by the central source computer, a second unique tag based on the second order,

associating, by the central source computer, the second unique tag with the second order to create a validated second order,

storing the validated second order at the central source computer,

sending, by the central source computer, the validated second order to the second party,

receiving, by the central source computer, an execution notice from a market that created an executed trade based on the first order and the second order,

generating, by the central source computer, an execution unique tag based on the execution notice,

associating, by the central source computer, an execution unique tag with the execution notice to create a validated execution,

storing the validated execution at the central source computer,

sending, by the central source computer, the validated execution to the first party and the second party,

receiving, by the central source computer, a clearance confirmation based on the executed trade,

generating, by the central source computer, a clearance unique tag based on the clearance confirmation,

associating, by the central source computer, the clearance unique tag with the clearance confirmation to create a validated clearance confirmation,

storing the validated clearance confirmation at the central source computer, and

sending, by the central source computer, the validated clearance confirmation to the first party and the second party,

receiving, by the central source computer, additional reference data for the validated execution from one of the first party and the second party,

generating, by the central source computer, an augmented unique tag based on the validated execution and the additional reference data,

associating, by the central source computer, the augmented unique tag with the validated execution and the additional reference data to create a validated augmented execution,

storing the validated augmented execution at the central source computer,

sending, by the central source computer, the validated augmented execution to the one of the first party and the second party that sent the additional reference data to the central source computer,

wherein the central source, the market, the first party and the second party are different entities.

4. The method of claim 3, wherein the initial reference data identifies at least two of:

a security, a market where the security is traded, a currency, a price, a rate, an expiry date, a maturity date, a reset date, and a financial market participant.

5. The method of claim 4, wherein the security is a contract or a product.

6. The method of claim 4, wherein the financial market participant is a counterparty.

7. The method of claim 3, wherein the additional reference data identifies at least one of:

a financial market participant, an account traded for, regulatory fees, taxes, a trade date, a settlement date, a settlement account, a collateral account, a settlement location, a depository and a delivery location.

8. The method of claim 7, wherein the financial market participant is one of:

a counterparty, a broker, a dealer, an inter-dealer, an agent, a trading desk, an investment manager, a trading advisor, a pool, a fund, a custody agent, a clearing agent, a settling agent, and a prime broker.

9. The method of claim 3, further comprising indemnifying, by the central source computer, the first party from a loss due to faulty reference data.

10. A method for processing a financial transaction, comprising:

providing, by a computer at a central source operating according to a computer program, initial reference data for the financial transaction to a first party for storage in a first data repository and to a second party for storage in a second data repository, the first data repository being different from the second data repository,

receiving, by the central source computer, a first order from the first party, the first order created from the initial reference data by the first party,

generating, by the central source computer, a first unique tag based on the first order,

associating, by the central source computer, the first unique tag with the first order to create a validated first order,

storing the validated first order at the central source computer,

sending, by the central source computer, the validated first order to the first party,

receiving, by the central source computer, a second order from the second party, the second order created from the initial reference data by the second party,

generating, by the central source computer, a second unique tag based on the second order,

associating, by the central source computer, the second unique tag with the second order to create a validated second order,

storing the validated second order at the central source computer,

sending, by the central source computer, the validated second order to the second party,

receiving, by the central source computer, an execution notice from a market that created an executed trade based on the first order and the second order,

generating, by the central source computer, an execution unique tag based on the execution notice,

associating, by the central source computer, the execution unique tag with the execution notice to create a validated execution,

storing the validated execution at the central source computer,

sending, by the central source computer, the validated execution to the first party and the second party,

wherein the central source, the market, the first party and the second party are different entities.

11. The method of claim 10, wherein the initial reference data identifies at least two of:

a security, a market where the security is traded, a currency, a price, a rate, an expiry date, a maturity date, a reset date, and a financial market participant.

12. The method of claim 11, wherein the security is a contract or a product.

13. The method of claim 11, wherein the financial market participant is a counterparty.

14. The method of claim 10, further comprising

receiving, by the central source computer, new reference data from a data-providing entity,

determining, by the central source computer, that the new reference data is acceptable when the new reference data meets an acceptance threshold, to generate accepted reference data, and

storing the accepted reference data at the central source.

15. The method of claim 14, further comprising

associating, by the central source computer, syntax data with the accepted reference data, to generate structured reference data, and

storing the structured reference data at the central source computer.

16. The method of claim 14, further comprising sending, by the central source computer, the accepted reference data to the first party for storage in the first data repository.

17. The method of claim 14, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the accepted reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the accepted reference data should be sent to the first party, and

sending, by the router, the accepted reference data to the first party when the router determines that the accepted reference data should be sent to the first party.

18. The method of claim 10, further comprising

determining, by the central source computer, that a trigger event has occurred,

generating, by the central source computer, triggered reference data, and

storing the triggered reference data at the central source computer.

19. The method of claim 18, further comprising sending, by the central source computer, the triggered reference data to the first party for storage in the first data repository.

20. The method of claim 19, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the triggered reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the triggered reference data should be sent to the first firm, and

sending, by the router, the triggered reference data to the first party when the router determines that the triggered reference data should be sent to the first firm.

21. The method of claim 10, further comprising indemnifying, by the central source computer, the first party from a loss due to faulty reference data.

22. A method for processing a financial transaction, comprising:

providing, by a computer at a central source operating according to a computer program, initial reference data for the financial transaction to a first party for storage in a first data repository and to a second party for storage in a second data repository, the first data repository being different from the second data repository,

receiving, by the central source computer, an execution notice from a market that created an executed trade based on the first order and the second order, the first order created from the initial reference data by the first party, the second order created from the initial reference data by the second party,

generating, by the central source computer, a first unique tag based on the execution notice,

associating, by the central source computer, the first unique tag with the execution notice to create a validated execution,

storing the validated execution at the central source computer,

sending, by the central source computer, the validated execution to the first party and the second party,

receiving, by the central source computer, a clearance confirmation based on the executed trade,

generating, by the central source computer, a second unique tag based on the clearance confirmation,

associating, by the central source computer, the second unique tag with the clearance confirmation to create a validated clearance confirmation,

storing the validated clearance confirmation at the central source computer, and

sending, by the central source computer, the validated clearance confirmation to the first party and the second party,

wherein the central source, the market, the first party and the second party are different entities.

23. The method of claim 22, wherein the initial reference data identifies at least two of:

a security, a market where the security is traded, a currency, a price, a rate, an expiry date, a maturity date, a reset date, and a financial market participant.

24. The method of claim 23, wherein the security is a contract or a product.

25. The method of claim 23, wherein the financial market participant is a counterparty.

26. The method of claim 22, further comprising

receiving, by the central source computer, new reference data from a data-providing entity,

determining, by the central source computer, that the new reference data is acceptable when the new reference data meets an acceptance threshold, to generate accepted reference data, and

storing the accepted reference data at the central source.

27. The method of claim 26, further comprising

associating, by the central source computer, syntax data with the accepted reference data, to generate structured reference data, and

storing the structured reference data at the central source computer.

28. The method of claim 26, further comprising sending, by the central source computer, the accepted reference data to the first party for storage in the first data repository.

29. The method of claim 26, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the accepted reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the accepted reference data should be sent to the first party, and

sending, by the router, the accepted reference data to the first party when the router determines that the accepted reference data should be sent to the first party.

30. The method of claim 22, further comprising

determining, by the central source computer, that a trigger event has occurred,

generating, by the central source computer, triggered reference data, and

storing the triggered reference data at the central source computer.

31. The method of claim 30, further comprising sending, by the central source computer, the triggered reference data to the first party for storage in the first data repository.

32. The method of claim 31, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the triggered reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the triggered reference data should be sent to the first firm, and

sending, by the router, the triggered reference data to the first party when the router determines that the triggered reference data should be sent to the first firm.

33. The method of claim 22, further comprising indemnifying, by the central source computer, the first party from a loss due to faulty reference data.

34. A method for processing a financial transaction, comprising:

providing, by a computer at a central source operating according to a computer program, initial reference data for the financial transaction to a first party for storage in a first data repository and to a second party for storage in a second data repository, the first data repository being different from the second data repository,

receiving, by the central source computer, an execution notice from a market that created an executed trade based on the first order and the second order, the first order created from the initial reference data by the first party, the second order created from the initial reference data by the second party,

generating, by the central source computer, an execution unique tag based on the execution notice,

associating, by the central source computer, the execution unique tag with the execution notice to create a validated execution,

storing the validated execution at the central source computer,

sending, by the central source computer, the validated execution to the first party and the second party,

receiving, by the central source computer, additional reference data for the validated execution from one of the first party and the second party,

generating, by the central source computer, an addition unique tag based on the validated execution and the additional reference data,

associating, by the central source computer, the additional unique tag with the validated execution and the additional reference data to create a validated augmented execution,

storing the validated augmented execution at the central source computer,

sending, by the central source computer, the validated augmented execution to the one of the first party and the second party that sent the additional reference data to the central source computer,

wherein the central source, the market, the first party and the second party are different entities.

35. The method of claim 34, wherein the initial reference data identifies at least two of:

a security, a market where the security is traded, a currency, a price, a rate, an expiry date, a maturity date, a reset date, and a financial market participant.

36. The method of claim 35, wherein the security is a contract or a product.

37. The method of claim 35, wherein the financial market participant is a counterparty.

38. The method of claim 34, wherein the additional reference data identifies at least one of:

a financial market participant, an account traded for, regulatory fees, taxes, a trade date, a settlement date, a settlement account, a collateral account, a settlement location, a depository and a delivery location.

39. The method of claim 38, wherein the financial market participant is one of:

a counterparty, a broker, a dealer, an inter-dealer, an agent, a trading desk, an investment manager, a trading advisor, a pool, a fund, a custody agent, a clearing agent, a settling agent, and a prime broker.

40. The method of claim 34, further comprising

receiving, by the central source computer, new reference data from a data-providing entity,

determining, by the central source computer, that the new reference data is acceptable when the new reference data meets an acceptance threshold, to generate accepted reference data, and

storing the accepted reference data at the central source.

41. The method of claim 40, further comprising

associating, by the central source computer, syntax data with the accepted reference data, to generate structured reference data, and

storing the structured reference data at the central source computer.

42. The method of claim 40, further comprising sending, by the central source computer, the accepted reference data to the first party for storage in the first data repository.

43. The method of claim 40, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the accepted reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the accepted reference data should be sent to the first party, and

sending, by the router, the accepted reference data to the first party when the router determines that the accepted reference data should be sent to the first party.

44. The method of claim 34, further comprising

determining, by the central source computer, that a trigger event has occurred,

generating, by the central source computer, triggered reference data, and

storing the triggered reference data at the central source computer.

45. The method of claim 44, further comprising sending, by the central source computer, the triggered reference data to the first party for storage in the first data repository.

46. The method of claim 45, further comprising

receiving, by the central source computer, a profile from the first party,

storing, by the central source computer, the profile in a router that is part of the central source computer,

providing, by the central source computer, the triggered reference data to the router,

comparing, by the router, the stored profile to the accepted reference data to determine whether the triggered reference data should be sent to the first firm, and

sending, by the router, the triggered reference data to the first party when the router determines that the triggered reference data should be sent to the first firm.

47. The method of claim 34, further comprising indemnifying, by the central source computer, the first party from a loss due to faulty reference data.