3.8.3.9.6 Updating Transaction Summary Tables

To update a Transaction Summary Table with unit costs held in your Management Ledger, perform the following steps:

Construct an Allocation Rule that uses the Volume column of your Transaction Summary Table as its Source, that uses the Management Ledger statistics as your driver (using the Simple method), and that debits the Cost Column in your Transaction Summary Table. In the debit specification, use < Match Source & Driver > for the Activity dimension and < Same as Source > for every other Key Processing Dimension. The (Management Ledger resident) unit cost drivers are stored under a user-defined Financial Element (one unit cost for each Activity).

Note:

For each Activity, you might have different unit costs for different products. If the statistics were stored under a single Financial Element, but varied by Activity and by Product, you can construct your cost to < Match Source & Driver > for both Activity and Product.

The sample list of Activities used in this discussion has a Channel orientation. You might wish to construct a smaller list of more fundamental Activities that vary by channel. For example, the list of activities presented above could be re-expressed as follows:

• Inquiries
• Debits Processed
• Credits Processed
• Other Transactions
• Reversals Processed
• Statements Processed

Under this smaller set of Activities, you could choose to store your unit costs in Management Ledger by Activity and by Channel (another user-defined Key Processing Dimension). In this scenario, you would define your Transaction Summary Table to utilize both Activity and Channel to differentiate it from its parent Instrument Table.

Note that this example uses a Dynamic Driver Allocation Rule to update the Transaction Summary Table. In this example and the examples of updates to Instrument Tables, you could also use Static Driver Table Allocation Rules. Even if your unit costs are the same from month-to-month, they generally need to be stored for every month in Management Ledger (although you can store your unit costs under a fixed month, for example, January, and then hard code your Allocation Rules to “always use the January balance”). For additional examples of using Static Driver Table Allocation Rules, see the Static Table Drivers section.