Indirect burdens

Indirect burden codes are used to create indirect expenses for administration and overhead fees based on project direct costs. If you use front end split functionality, generate front end split distributions after global ledger posting and before generating indirect burdens. Generate Indirect Burdens and Journalize Indirect Burdens use the finance dimension 2 from the originating GLTransactionDetail.

See Front end split.

General ledger transactions are used as the driver and the source for selecting expenditure transactions. The general ledger transaction is queried by the posting date and project. Expense transactions are skipped if the dates of the originating expense are not valid for the posting project. There is no indication if a transaction is skipped.

Each GLTransactionDetail is read and summarized to that record. This list contains the information that is verified:

  • The Indirect Burden field to verify that it is in process and has a project amount.
  • The To Accounting Entity field on the GLTransactionDetail record is compared to the run-time parameters.
  • The selection group is verified and the include/exclude field for all active Project Indirect Burden records for the project.
  • Indirect burdens do not inherit the auto reversing status from the originating transactions. The auto reversing field is false for any transactions that are generated by Project Ledger.

Indirect burdens that are created from transactions that are on AP hold for billing are also created with the AP Hold for Billing. After the AP transaction is paid and the Update AP Hold job is run, the original AP transaction is removed from AP hold for billing but the Indirect Burden remains on AP Hold for billing.

Remove Burden AP Hold is used to find ProjectIndirectBurdenTransaction records where these are true:

  • The generated GLTransactionDetail’s AP Paid field is Hold For Billing
  • The originating expense’s AP Paid field is Eligible
  • The generated transaction is updated to Eligible

When the originator is held, the generated burden is skipped regardless of its AP status.