5.3.1.3.9.4 From Management Ledger to Instrument

As seen in Example #1 and Example #2 above, Dynamic Driver Allocation Rules can also update balance or rate columns at the Instrument level. The following example uses the Management Ledger as a Source while using an Instrument column as Driver to post to the Instrument level.

In this example, your objective is to distribute Item Processing expenses from your Management Ledger to individual Customer Account Records. If each of your individual Customer Account records for every demand Deposit Account carried a statistic called Number of Items Processed, that statistic would make an excellent Percent Distribution driver for item processing expense; your target column for such a rule would be a user-defined Instrument column called Item Processing Expense. For this rule, you would likely utilize < Match Driver > for each Key Processing Dimension in your Output. Note that Instrument-level allocations can only alter the target balance or rate column. Instrument level allocations cannot alter Key Processing Dimension Values; the Instrument-level Key Processing Dimensions can only be used as lookup keys. If you use either < Same as Source > or < Match Source & Driver > on one dimension, your rule is forced to exclude any Instrument rows that did not match your Management Ledger for the dimension in which you chose < Match Source & Driver >.