Defining a burden code (AC/BR/GM)

A burden code identifies the burden costs that you want to calculate, such as various types of General and Administrative Overhead, Fringe Benefits, and other burden costs. You can calculate multiple burdens from a single source transaction, and you can set up as many burden codes as you need. Use this procedure to define a burden code.

  1. Access Burden Codes (AC60.1).
  2. Define each burden code that you need. Use these guidelines to specify the field values:
    Burden Code

    Specify a name of up to five characters long for the burden code.

    Description

    Specify a description for the burden code.

    Post to Acct Cat

    Select the account category to which you want to post burden transactions created for the burden code. The activity in each burden transaction comes from the source transaction used to calculate the burden.

    Note: Use one or more separate burden account categories to help make analysis and reconciliation easier.
  3. Specify the step parameters to determine the order in which burdens are calculated. Use these guidelines to specify the field values:
    Step

    Specify a step number to let burden transactions be potential source transactions for subsequent burden calculations during Activity Posting (AC190). For example, burdens calculated for Step 1 burden codes can be potential source transactions for burden codes that are assigned in Step 2. Burdens calculated for Step 1 and Step 2 burden codes can be potential source transactions for Step 3 burden codes, and so on. You can assign the same step to multiple burden codes.

    If you leave the step field blank, then burden transactions created for the burden code are not eligible for subsequent burden calculations.

    Note: If you do not want to calculate burden on burdens, then do not assign steps to any burden codes.
    Step Var

    This field lets you apply burden calculation deviations. The default is blank, which provides no deviations from the burden step calculation order. You can also select:

    • Stand Alone to prevent the burden code from being considered in subsequent burden calculations.

    • Applies Only To Burden to identify specific burdens as the exclusive source transactions for the burden code. This excludes original cost transactions, as well as any burdens for codes other than the one you specify, from the potential source transactions. If you select this option, complete the Burden Code field.

    Burden Code

    If you selected Applies only to Burden in the Step Var field, then select a burden code to identify burdens that are possible source transactions for the burden code.

  4. In the Driver Type field, select a driver type to identify the transaction components that make a transaction eligible for burden calculation. Driver types also determine how you define burden pools and burden rates.
    For driver type Transaction eligibility is based on
    Work company and accounting unit The company and accounting unit in the source transaction.
    Employee company and accounting unit The default company and accounting unit for the employee in the source transaction. The employee's default company and accounting unit are defined on Employee (HR11.1).
    Activity company and accounting unit The default company and accounting unit for the activity in the source transaction. The activity's default company and accounting unit are defined on Activity (AC10).
    Activity The activity in the source transaction.
    Account category The account category in the source transaction.
    Employee The employee in the source transaction.
    Salary class The salary class associated with the employee in the transaction. The salary class for an employee is defined on Employee (HR11.1).
    Job code The job code in the source transaction. The job code must be established as an activity transaction attribute.
    Note: Driver types involving the employee-related information presume an employee will be present in the transaction. If the transaction does not contain an employee, then it is not eligible for burden.
  5. To create off-set burden transactions in Project Accounting or General Ledger, click More to access Additional Information (AC60.2).
  6. Use this sub-form to define information for off-set burden transactions. Use these guidelines to specify the field values:
    GL Information

    To create General Ledger burden transactions using the company and accounting unit in the source transactions, select an account and subaccount.

    To create General Ledger burden transactions using a different company and accounting unit than the activity burden transactions, select a GL Code that identifies the company, accounting unit, account, and subaccount.

    Activity Off-Set

    To create a balanced entry for burdens in Project Accounting, select the activity and account category you want in the off-set (contra) burden transactions.

    GL Off-Set Information

    To create General Ledger burden off-set transactions using the company and accounting unit in the source transactions, select an account and subaccount.

    To create General Ledger burden off-set transactions using a different company and accounting unit than the activity burden transactions, select a GL Code that identifies the company, accounting unit, account, and subaccount.

    Note: General Ledger postings for off-set burden transactions are summarized.

Related reports and inquiries

To Use
List burden codes Burden Code Listing (AC260)
Related topics