Accounting Rules

You define standard accounting entries, or rules for project-based transactions, based on a combination of these data elements:

• Project business unit.

• Analysis type.

• Contract.

• Project.

• Project GL business unit.

• Resource GL business unit.

• Activity.

• Other project-related ChartFields.

• Other project-related identifiers, such as project type, project transaction type, and project transaction code.

• GL ChartFields.

These rules are necessary to process any accounting from project transactions. You must enter values for the project business unit and resource GL business unit. You must also enter a value for the project GL business unit when you use transorganizational accounting. You can minimize the rules by entering a wildcard (the percent symbol) in all of the other listed fields. Alternatively, you can make the rules more specific by entering values for the listed fields.

For example, assume that a time sheet is priced and generates a billable row with a BIL analysis type and a cost row with an analysis type of CAC (Cost Sharing Actuals). These two rows (BIL and CAC) may require different accounting entries using two accounting rules—one for the BIL analysis type and one for the CAC analysis type. You can copy accounting rules to the various project business unit-and-resource GL business unit combinations that you require by clicking the Copy Accounting Entries To link on the Accounting Rules page and entering the new header criteria.

Note:

If you use the Government Contracting feature that is available with PeopleSoft Contracts, and you select the Separate Billing and Revenue option on the Installation Options - Contracts page, transactions with a Revenue (REV) analysis type use the accounting rules that are set up for the BIL analysis type. This ensures that the system uses same UAR for all billing and revenue accounting entries that are associated with cost plus contract lines.