Post details for project transaction rules

Use a transaction rule to define which accounts to debit and credit for a step. For example, a step calculates a 30% indirect payroll cost and posts the value. The posted journal entry debits and credits the specified accounts on the Posting Details page.

How does the posted entry work?

Every step in a transaction rule has a value. Depending on the action, the value is the result of either processing the source transaction or adding the value of other steps.

• If the action is Process source transaction, the value is the source transaction (such as a timesheet entry), multiplied by the rate.
• If the action is subtotal previous lines, the value is the sum of the lines, multiplied by the rate.

If you select the Post checkbox for the step, the value of the step can be posted to the debit and credit accounts specified on the Posting Details page. For example, you might post an indirect payroll burden cost as follows:

• Debit Account: 7700: Payroll burden
• Credit Account: 8700: Indirect costs offset

Add posting details

1. Go to Projects > Setup > More > Transaction rules.
2. Select the rule in the Transaction Rules list and then select Edit.
3. Select the Post checkbox for a step, then select the icon to the right of it.
4. In Posting Details, select the Debit Account and Credit Account to be used for the resulting journal entry.
5. Optionally, to override the location, department, class, or project from the processed source transaction, select the corresponding values.

   The source transaction or (in the case of the customer) the project fills in other dimension information automatically.

6. To bill the transaction created by this transaction rule, select the Billable checkbox.

   To create a billable transaction rule:

   • Enable billable GL transactions when you Configure Projects
   • Enable the project billing flag on your General Ledger journal
7. Select Save to save the transaction.

Dimension values used for the posted transaction

If you leave the location, department, class, or project blank, the resulting journal entry posts automatically using the dimensions from the source transaction. For example, the transaction rule processes a timesheet entry for Project 100 in the North Suburbs location. If a step in the transaction rule posts a journal entry, the journal entry uses the same project and location.

For other dimensions, item, employee, and vendor are derived automatically from the source transaction. Customer is derived from either the project of the source transaction or (if you override the project on the Posting Details page) from the selected project.

If a transaction rule has already been used to process transactions, you can still edit the posting details and other information. However, your changes only apply to future transactions.