Project Billing

1. Invoices
Event Billing
• With event billing, you invoice projects based on predefined amounts that are not
directly related to detail expenditure items.
• You define the events (also referred to as milestones) to specify:
• How much to bill
• When to bill (can specify future dates)
• An invoice is generated after the scheduled event date.

2. EAS – Oracle Apps
Invoices
Entering Events
(N) Billing—>Events—>Project (B) Open
Specify the information in
four regions:
•Project/Top Task: Indicates
the project or top task name
and number
•Status: Displays the
revenue and billing status
•Date Ranges: Indicates the
creation and completion
date of event
•Event: Indicates the event
type and classification, the
amount of revenue to
accrue, the amount to bill,
and the event number
Enter events at either project-level or top-level tasks.

3. Invoices
Invoice Flow
Interface
invoice
to AR
Approve invoice
Generate
draft
invoice
Review,
adjust
invoice
Approve
invoice
Release
invoice
Print
invoice
Send
invoice to
customer

4. EAS – Oracle Apps
Invoices
Invoice Summary
(N) Billing—>Invoice Review

5. EAS – Oracle Apps
Invoices
Invoice Review
(N) Billing—>Invoice Review (B) Open

6. EAS – Oracle Apps
Invoices
Interfacing Invoices to AR
• Oracle Projects interfaces invoices to Oracle Receivables.
• This flow uses the same type of processes as costing and revenue: Interface, Import, and Tieback.
• Use Interface Streamline option to interface invoices to AR.
• Integration with Oracle Receivables
• Invoices are interfaced to Oracle Receivables using the AR AutoInvoice Import program - Invoice Batch
Source: PA Invoices
• All accounting transactions, except for tax, are determined by Oracle Projects AutoAccounting. AR
AutoAccounting rules are not used.
• Invoices and revenue are interfaced to Oracle Receivables and Oracle General Ledger in either order
running the following processes:
– PRC: Interface Invoices to Receivables
– PRC: Interface Revenue to General Ledger
• Audit details in Oracle Projects link project invoices in Oracle Projects to invoices in AR.
• The AR Transaction Type Extension can be used to determine the AR transaction type when invoices
are interfaced to Oracle Receivables.

7. AR interface
Revenue
distributed costs
AR invoices
Generate
draft invoice
Interface to
Receivables
Tieback invoices
Approve/release
invoice
AR AutoInvoice
Oracle Receivables
Events
Adjustments

8. EAS – Oracle Apps
Invoices
Invoice Statuses
Invoice Status
Unapproved Approved Released Interfaced Accepted
Invoice Flow
Interface
invoice
to AR
Approve invoice
Generate
draft
invoice
Review
and adjust
invoice
Approve
invoice
Release
invoice
Print
invoice
Send
invoice to
customer
Tieback
invoice