Previous	Next		Contents	Index	Navigation	Glossary	Library

If you store burden costs as separate, summarized burden transactions, the burden transactions are created on the same project that incurred the costs. If you choose to store burden costs as a value along with raw cost on the expenditure item on the project that incurred the transactions, the burden transactions are created on the collection project and task used for collecting burden transactions intended for accounting by burden cost components only.

The burden transactions created by this process can be billable or non-billable, depending on the Transaction Control logic you have entered. See: Transaction Controls.

The process also computes the costs and determines the GL account to which to post the cost for the burden transactions that it creates.

Process Submission

Output Reports

• The Usage and Miscellaneous Cost Report. Lists all items that were successfully cost distributed. For each item, this report displays the resource and expenditure type that was used, the date on which the resource was used, the project and task to which the item is charged, the quantity of the usage utilized (measured by the units of the expenditure type), the cost rate of the resource, and total cost.

• The Usage and Miscellaneous Cost Exception Report. Lists all items that could not be processed by the Create and Distribute Summarized Burden Component Items process. This report lists the rejection reason for each of the items that fails cost distribution.

Note: You can also review rejection reasons from the Expenditure Items window by using the Show Field option in the Folder menu to display Cost Distr. Rejection. See: Performing a Project Expenditure Inquiry.