Note:

Revenue and Billing Information

When you enter revenue information for your project, you specify a revenue distribution rule for the

revenue accrual method and the billing method for this project. When you enter billing information,

you specify invoice formats, bill cycle days, and other invoicing information.

The project type determines which revenue distribution rule appears as the default value for this

field, and which other revenue distribution rules you can choose from. Oracle Projects predefines the

following revenue distribution rules:

Cost/Cost

Accrue revenue and bill using the ratio of actual cost to budgeted cost (percent

spent).

Cost/Event

Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), and

bill based on events.

Cost/Work

Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), and

bill as work occurs.

Event/Event

Accrue revenue and bill based on events.

Event/Work

Accrue revenue based on events, and bill as work occurs.

Work/Event

Accrue revenue as work occurs, and bill based on events.

Work/Work

Accrue revenue and bill as work occurs.

Note:

* Allow Revenue Budget Entry. Indicates if you allow entry of revenue budget types. You may choose

to not allow entry of revenue budgets for indirect or capital projects. You must enter a revenue

budget for a contract project before it can accrue revenue and be billed.

Incorrect:

Not A: Task types assign default attributes to tasks and control how Oracle Projects processes tasks.

Task types specify basic task attributes.

Not C: Work types represent a classification of work. You use work types to classify both actual and

scheduled work.

Not E: Oracle Projects uses start and finish dates to control processing, indicate estimated and

scheduled duration, and serve as tools to evaluate project performance.

The start and finish dates at the project level are:

Actual: Actual dates when work on the project started and finished. You can use these dates to drive

future timecard and earned value functionality.

(not E) Scheduled: Scheduled start and finish dates for the project.

Target: The expected lifespan of the project.

Estimated: A task manager's estimate of when work on the project will be started and finished.

Baseline: The baselined schedule

Invoice

When you run the program to interface invoices to Oracle Receivables, Oracle Projects runs

AutoAccounting to determine the appropriate default accounts. If the invoice fails AutoAccounting,

then the program marks the draft invoice with an error. See: Overview of AutoAccounting, Oracle

Projects Implementation Guide.

The following table shows entries Oracle Projects creates when the Interface Invoices to Oracle

Receivables process is run:

Account

Debit

Credit

Receivables

200.00

Unbilled Receivables and/or Unearned Revenue

200.00

Reference:

Oracle Project Billing User Guide