# Patent

## Title
Billing workflow system for crediting charges to entities creating derivatives exposure

## Abstract

An automated billing workflow system receives credit valuation adjustment (CVA) amounts associated with derivatives trades. The automated billing workflow system interacts with an Accounting System in order to make appropriate Profit and Loss (P&L) entries for the CVA amounts. The CVA amounts are billed to the business units which actually created the risk. The invention employs a plurality of Workflow Queues. As an item makes it way through the billing workflow, it may be slotted in one or more of these queues where further action will take place.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application is a continuation of prior U.S. patent application Ser. No. 10/774,357, titled “Billing Workflow System for Crediting Charges to Entities Creating Derivatives Exposure”, filed on Feb. 6, 2004, which in turn claims the benefit of U.S. Provisional Application Ser. No. 60/529,498, titled “Billing Workflow System For Crediting Charges to Entities Creating Derivatives Exposure”, filed on Dec. 15, 2003. The entire disclosures of U.S. patent application Ser. No. 10/774,357 and U.S. Provisional Application No. 60/529,498 are hereby incorporated herein by reference.


FIELD OF THE INVENTION
The present invention relates generally to automated billing systems, and, more particularly, to an automated billing workflow system for crediting charges to entities creating derivatives exposure.
BACKGROUND OF THE INVENTION
Although profitable, trading in derivatives involves some degree of risk. For example, traders may act as market makers for certain derivatives and, in accumulating inventory, develop positions that result in market risk. The main risk is represented by the possibility of counterparty default, the estimation of which, on a per deal basis, is called the credit charge or bill (on the day of deal inception) and credit reserve movement (on following days, up to the expiration date of the deal).
Various analytical models exist that allow investment banks to estimate the risk associated with particular derivatives. Although it is possible to make estimates as to the risk and calculate an amount of reserve to set aside, one of the problems has been that financial institutions fail to appropriately credit an amount of the exposure to the actual business unit and trade creating the risk.
SUMMARY OF THE INVENTION
An automated billing workflow system receives reserve information associated with derivatives trades. The automated billing workflow system interacts with an Accounting System to make appropriate Profit and Loss (P&L) entries for reserve amounts. The reserve amounts are then billed to the business units that actually created the derivatives exposure.
The invention employs a plurality of Workflow Queues. As an item makes it way through the billing workflow, it may he slotted in one or more of these queues where further action will take place. This arrangement allows various employees to review the charges to determine whether they are appropriate, and to make adjustments before the amount is actually billed.
These and other aspects, features and advantages of the present invention will become apparent from the following detailed description of preferred embodiments, which is to be read in connection with the accompanying drawings.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of a computer processing system to which the present invention may be applied;
FIG. 2 is a block diagram showing an exemplary billing workflow for billing credit charges to entities executing derivatives; and
FIG. 3 illustrates various exemplary workflow queues that may be used in conjunction with the system shown in FIG. 2.



DESCRIPTION OF PREFERRED EMBODIMENTS
As depicted in FIG. 1, a computer system 100 includes at least one processor (hereinafter processor) 102 operatively coupled to other components via a system bus 104. A read-only memory (RUM) 106, a random access memory (RAM) 108, an I/O interface 110, a network interface 112, and external storage 114 are operatively coupled to the system bus 104. Although not shown, it is to be understood that the RAM 108 includes operating system software and software of the invention. Representative operating systems include Microsoft WINDOWS, LINUX and UNIX.
Various peripheral devices such as a display device, a disk storage device (e.g., a magnetic or optical disk storage device), a keyboard, and a mouse, may be operatively coupled to the system bus 104 by the I/O interface 110 or the network interface 112.
The computer system 100 may be a standalone system or he linked to a network via the network interface 112. The network interface 112 may be a hard-wired interface. However, in various exemplary embodiments, the network interface 112 can include any device suitable to transmit information to and from another device, such as a universal asynchronous receiver/transmitter (UART), a parallel digital interface, a software interface or any combination of known or later developed software and hardware. The network interface may be linked to various types of networks, including a local area network (LAN), a wide area network (WAN), an intranet, a virtual private network (VPN), and the Internet.
The external storage 114 may be implemented using a database management system (DBMS) managed by the processor 102 and residing on a memory such as a hard disk. However, it should be appreciated that the external storage 114 may be implemented on one or more additional computer systems.
Those skilled in the art will appreciate that other alternative computing environments may be used without departing from the spirit and scope of the present invention.
FIG. 2 illustrates an exemplary system for billing credit charges to entities trading derivatives. As depicted, a Derivatives Risk Allocation System 210 receives derivative trade information and calculates a credit valuation adjustment (CVA) amount for the trade. In general, the CVA is based on an estimation of exposure to counterparty default. This estimation of exposure to counterparty default is calculated using a complex Monte Carlo methodology modeled over the projected life of the trade. The Derivatives Risk Billing Workflow System 200 receives the calculated CVA, and can interact with an Accounting System 220 in order to make appropriate Profit and Loss (P&L) entries for the CVA. The Accounting System 220 is integrated with the Derivatives Risk Billing Workflow System 200. (Alternatively, the Accounting System 220 could exist as a separate system). The CVA amounts are billed to the business units which actually caused the risk and appear on billing reports.
Advantageously, the Derivatives Risk Billing Workflow System 200 includes a plurality of Workflow Queues 250 (shown in detail in FIG. 3) for holding an item for further review (or other purposes). As an item makes it way through the billing workflow, it may be slotted in one or more of the Workflow Queues 250 where further action will take place. This arrangement allows various employees to review credit charges to determine whether they are appropriate, and to make adjustments before the CVA is actually billed. Also, as mentioned, accounting adjustments for Profit and Loss (P&L) can also be automatically made.
As discussed above, once a derivatives trade is executed, the relative risk of the trade to the institution can be assessed, and an amount of risk-related reserve determined. For various reasons, this CVA may not be the actual amount billed. For example, the amount calculated may be disputed by a client or it may be deemed as being invalid. The present invention allows for additional levels of review, as well as for additional checks to be made before the bill is actually sent out.
As an initial matter, trade information can be checked to determine whether the trade is “frozen” or “excluded”. In general, a trade will be considered frozen or excluded based on its Universal Counterparty Number (UCN). The UCN can represent an individual legal entity, commercial grouping or commercial entity. Frozen trades can occur for many reasons (e.g., certain internal counter parties, temporary data quality issues). Counter parties can be marked as excluded for various reasons (e.g. counter party risk managed in a more specialized book).
If it is determined that the trade is “frozen” or “excluded”, the calculated CVA will be held in the Frozen/Excluded Queue 251. The trade will be held until its UCN becomes unfrozen or removed from the excluded list. In that case, the trade will be moved to the Unfrozen/UnExcluded Queue 253. As with the other queues, this Unfrozen/UnExcluded Queue 253 is intended to be “viewable”. That is, the contents of the queue may be browsed, or otherwise outputted, to appropriate personnel. For example, a user in the Accounting Department may use an on-line screen to examine the contents of the viewable queue. The user may adjust the content of the queue, or to take other specified action.
Assuming that the trade is not “frozen” or “excluded”, the CVA is assessed to determine whether it exceeds a predefined threshold amount. Trades that exceed the predefined threshold amount will be routed to a Failed Threshold Queue 254. Items in the Failed Threshold Queue 254 will be examined to determine whether the credit amount generated is indeed invalid. If the credit amount is determined to be valid, the credit amount will flow to the Business Queue 258. As will be discussed in more detail, items in the Business Queue 258 will eventually be routed to an Invoice Queue 259, and then appear on the billing statement. If the credit amount is not deemed valid, however, the amount will be reversed and forwarded to the Do Not Bill Queue 257. P&L for items in the Failed Threshold Queue 254 will be posted as “pending” until released to the Business Queue 258 or the Do Not Bill Queue 257. A “pending” indicator can be associated with these trades, for example.
Trades that have an event log that has been triggered will appear in an Event Queue 255 for analysis. The trigger can be a specified date or an event associated with a trader (e.g., an edit or unwind). A diary system will preferably be maintained to prompt users to do and record certain tasks, and to remind users of overdue tasks. For example, the diary might remind certain users that a trade has been moved to a queue for review by a specific department, and, if they have not reviewed this matter after a certain number of days, an email reminder would be sent.
Items that are being disputed can be sent to the Disputed Items Queue 256. For example, if a business unit does not agree with a particular charge in the Business Queue 258, the business unit can flag the item (using an on-line screen, for example), and add a comment including a reason for the disagreement. The flagged item can be reviewed to determine whether the item should be routed to the Disputed Items Queue 256 for further review. P&L for items in the Disputed Items Queue 256 will be reversed and posted as “pending” until released to the Business Queue 258 or the “Do Not Bill” Queue 257. The pending” indicator can also be used for trades in the Disputed Items Queue 256.
Items will flow to the “Do Not Bill Queue” 257 when the amount will not be charged. Trades can be sent to “Do Not Bill Queue” 257 from the Unfrozen/Unexcluded Queue 253, the Failed Threshold Queue 254, the Disputed items Queue 256, or the Business Queue 258. Any pending P&L will be reversed once items are designated “Do Not Bill”.
Contents of the Business Queue 258 may be viewed using any suitable means, such as, for example, a screen including a drop-down menu where each business unit is able to retrieve only items related to its particular business. Trades that pass the threshold check will generally flow directly to the Business Queue 258. At that point, P&L will be directly posted. Trades that have been in the Unfrozen/Unexcluded Queue 253, the Failed Threshold Queue 254, or the Disputed hems Queue 256 can be sent to the Business Queue 258 after review, and P&L will be posted for these items. Trades that are in the Business Queue 258 can also be moved to the “Do Not Bill” Queue 257. This will cause P&L to be reversed and show a zero charge amount.
As mentioned, once items reach the Business Queue 258, the business units will be able to review them. If a business unit disagrees with a charge, the business unit will have the ability to flag that item along with a comment about the reason for the dispute. Flagged items will he reviewed to decide whether to send the trade to the Disputed items Queue 256 for further review. P&L will be reversed for these deals and classified as pending. If the dispute is deemed invalid, an explanation may be associated with the item for the business unit to review. These trades will flow to the Invoice Queue 259.
Items that have entered the Business Queue 258 will be sent to the Invoice Queue 259 at the end of the billing period (except for those items that are sent back to the Disputed Items Queue 256 for further review). Preferably, invoices will be arranged by business unit, reflecting the following column screen headers:
1. Total Gross Credit Amount
2. Adjustments
3. Net Credit Amount
4. Post-billing adjustment
5. Proxy Re-balancing
6. Collateral/Netting rebates/charges
7. Miscellaneous adjustments
8. Total billed amount. Preferably, clicking on the Total Billed Amount column will provide details relating to that trade.
9. Editable Entry for the business unit to enter an expected amount to pay/receive.
10. Editable Entry for Accounting/Control to enter the amount actually received/paid.
11. Column/Field reflecting an outstanding amount (i.e., difference between the total bill amount and the amount that Accounting/Control indicated was actually received/paid).
12. Invoice Number.
Of course, the invoice may instead, or additionally, be outputted as a primed report.
It is to be appreciated that the above describes a somewhat simplified billing system. The system described above is meant to be illustrative of various embodiments of the present invention.
The invention will be clarified by the following examples.
EXAMPLES
1. Trade on Frozen List
In this case, the system recognizes the trade as having a frozen UCN. The trade is then routed to the Frozen/Excluded Queue 251 where it remains until “unfrozen”. The trade does not impact P&L and does not appear in the month's billing. Once the UCN is unfrozen, all bills generated during the frozen period will be reviewed to determine whether charges should be applied to the business unit. If the items that are being billed are items that originated in a prior month, they can be billed as “Post Bill Adjustments” in the current month.
2. Credit Valuation Amount Exceeds Threshold
The CVA associated with a trade will be checked to determine whether it exceeds a predefined threshold amount (e.g., $100,000). In this case, the trade will be routed to the Failed Threshold Queue 254. The charge will then be analyzed to determine whether it is valid or not. The credit amount can either be forwarded as billed, adjusted, or zeroed out. P&L will be posted as pending until the item is routed to the Business Queue 258 or the “Do Not Bill Queue 257.
3. Invoiced Trade From Prior Month is Contested by Business Unit
Let us assume that the trade resided in the invoice Queue 259 and the business unit decided to make an adjustment. If it is agreed that the adjustment should be made, the trade will be moved to the Disputed Items Queue 256. This will cause P&L to be reversed for the month it was “earned” and classified as a “Post-Bill adjustment.” This P&L amount will be pending while the item remains in the Disputed Items Queue 256. Once the adjustment is made, the trade will be sent back to the Business Queue 258, posting the new amount. The net between the reversal and the new amount will be reflected in the “P&L-Post-Bill Adjustment” column and recognized in the current month.
Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the invention.

## Claims

1. A computer system for allocating charges related to derivatives trading to a business unit in a business organization, comprising:
a computer memory configured to store reserve amount information based on an exposure associated with a derivative trade; and
a risk allocation computer operatively coupled to the computer memory, the risk allocation computer configured to calculate a credit valuation adjustment amount associated with a derivative trade; and
a workflow queue computer operatively coupled to the risk allocation computer, the workflow queue computer configured to hold the credit valuation adjustment amount for further review.

2. The system of claim 1, wherein the workflow queue computer comprises a frozen/excluded queue configured to hold the credit valuation adjustment amount if the derivative trade is on an excluded list.

3. The system of claim 1, wherein the workflow queue computer comprises a failed threshold queue configured to assess whether the credit valuation adjustment amount exceeds a predefined threshold amount.

4. The system of claim 1, wherein the workflow queue computer comprises a business queue configured to provide access to the credit valuation adjustment amount to an individual associated with a business unit involved in the derivative trade.

5. The system of claim 1, wherein the workflow queue computer comprises an invoice queue configured to bill the credit valuation adjustment amount to a business unit involved in the derivative trade.

6. The system of claim 1, wherein the workflow queue computer comprises a disputed item queue configured to bill the credit valuation adjustment amount to a business unit involved in the derivative trade.

7. The system of claim 1, wherein the workflow queue computer comprises an event queue configured to store information relating to a derivative trade having an associated event.

8. The system of claim 1, wherein the workflow queue computer comprises a do not bill queue configured to receive a derivative trade for which the credit valuation adjustment amount is not charged to a business unit involved in the derivative trade.

9. A method for managing a credit valuation adjustment amount related to a derivative trade to a business unit in a business organization, comprising:
receiving, by a computer processor, derivative trade information;
calculating, by the computer processor, a credit valuation adjustment amount based on the derivative trade information; and
providing, by the computer processor, the derivative trade information and credit valuation adjustment amount to at least one of a plurality of workflow queues configured to facilitate further review or processing of the derivative trade information and the credit valuation adjustment amount.

10. The method of claim 9, wherein the at least one of the plurality of work flow queues comprises a frozen,/excluded queue configured to hold the credit valuation adjustment amount if the derivative trade is on an excluded list.

11. The method of claim 9, wherein the at least one of the plurality of workflow queues comprises a failed threshold queue configured to assess whether the credit valuation adjustment amount exceeds a predefined threshold amount.

12. The method of claim 9, wherein the at least one of the plurality of work flow queues comprises a business queue configured to provide access to the credit valuation adjustment amount m an individual associated with a business unit involved in the derivative trade.

13. The method of claim 9, wherein, the at least one of the plurality, of workflow queues comprises an invoice queue configured to bill the credit valuation adjustment amount to a business unit involved in the derivative trade.

14. The method of claim 9, wherein the at least one of the plurality of workflow queues comprises a disputed item queue configured to bill the credit valuation adjustment amount to a business unit involved in the derivative trade.

15. The method of claim 9, wherein the at least one of the plurality of workflow queues comprises an event queue configured to store information relating to a derivative trade having an associated event.

16. The method of claim 9, wherein the at least one of the plurality of workflow queues comprises a do not bill queue: configured to receive a derivative trade for which the credit valuation adjustment amount is not charged to a business unit involved in the derivative trade.

17. A program storage device readable by a machine, tangibly embodying a program of instructions executable on the machine to perform method steps for crediting charges to entities creating derivatives exposure, the method steps comprising:
receiving reserve information associated with a derivative;
identifying an entity creating the derivative exposure; and
generating billing information for the entity creating the derivative exposure.