The key difference between burden storage methods is how you view the burden costs on your project. You view the burden costs as another value on the same expenditure item or as a separate expenditure item.

The way you budget your projects may influence how you choose to store burden cost:

• If you budget burden components as separate elements in your budget, you would typically choose to view the actuals in a similar way (as a separate expenditure item).

• If you budget burdened costs as a calculation of the raw cost for a given resource, you would typically choose to view the actuals in a similar way (with the burdened costs as a value for the individual expenditure items).

  Note: To budget by burden cost component, you use the expenditure type assigned to the burden cost code during setup.

Regardless of which method you choose to store the burden cost, the total raw and burdened costs of the project do not change. The key difference is how you view the information. Also, these methods only apply to storing the cost amounts of the transactions. If you are using cost plus processing for revenue accrual and/or invoicing, then the revenue or invoice amounts are held as an amount along with the raw cost on the expenditure item. You cannot store the burden costs applied for revenue accrual and invoicing as separate summarized, burden transactions.