Defining Transaction Types for Invoice Processing
Oracle Projects generates draft invoices and uses Oracle Receivables features to post them to Oracle General Ledger, and maintain and track customer payments on them. Oracle Receivables uses transaction types to determine whether the transaction generates an open receivable balance and whether it posts to Oracle General Ledger.
Oracle Projects predefines two transaction types to process your invoices in Oracle Receivables:
- An invoice transaction type (Projects Invoice)
- An invoice credit memo transaction type (Projects Credit Memo)
Verify predefined PROJECTS INVOICES Batch Source values are correct
Before you make changes to the transaction types for invoicing, verify that the predefined PROJECTS INVOICES Batch Source is accurate. You should see the following values:
| Name:
| PROJECTS INVOICES
|
| Description:
| Project Accounting Invoices
|
| Type:
| Imported
|
| Active:
| Yes
|
| Automatic Batch Numbering:
| No
|
| Automatic Invoice Numbering:
| No
|
| Standard Transaction Type:
| Projects Invoice
|
| Credit Memo Batch Source:
| NULL
|
Oracle Projects assigns a transaction type to an invoice transaction in one of two ways, depending on how your business decides to process invoices:
Implementing Decentralized Invoicing
With decentralized invoicing, you allow organizations to process their own invoice collections. Oracle Projects and Oracle Receivables provide you with a way to easily report and query invoices in Oracle Receivables by organization.
When you interface draft invoices to the Oracle Receivables interface tables, Oracle Projects locates the project managing organization and moves up the organization hierarchy "tree" to the lowest-level Project Invoice Collection organization at or above the project managing organization to assign the appropriate transaction type to each invoice.
After validation, the AutoInvoice Import Program moves the draft invoices and their assigned transaction types into the Oracle Receivables invoice tables. When you use this method, you can run reports and process Oracle Receivables invoices by organization by selecting the Project Invoice Collection organization name for the transaction type parameter.
To implement decentralized invoicing:
1. Determine which organizations process invoices.
2. Define those organizations with the Project Invoice Collection Organization classification enabled. See: Organizations.
3. Define or update the Project/Task Owning Organization Hierarchy to include the relevant Project Invoice Collection organizations. See: Organization Hierarchy.
4. Disable the Centralized Invoice Processing check box when you define implementation options for Oracle Projects. See: Billing Implementation Options.
5. Run the IMP: Create Invoice Organization Transaction Types program. This program defines transaction types for you in Oracle Receivables with the same name as the project invoice collection organization. You can rerun this program any time you add new organizations or change organization names.
Attention: You must run the IMP: Create Invoice Organization Transaction Typesis program before you can successfully interface invoices from Oracle Projects if you specify an organization type in the Invoice Processing Organization Level of the Billing Implementation Options.
Implementing Centralized Invoicing
With centralized invoicing, one group or organization processes all invoices. All Oracle Projects invoices are created in Oracle Receivables with the same invoice type of Projects Invoice or Projects Credit Memo for the processing operating unit.
If you select Centralized Invoicing (the system default) in Oracle Projects Implementation Options, Oracle Projects assigns the default transaction types assigned to the invoice batch source specified in the Oracle Projects implementation options.
The predefined transaction types are the default transaction types of the Projects invoice batch source. After validation, AutoInvoice assigns the default values from the invoice batch source to invoices and copies those transaction types into the invoice tables.
AR Transaction Type Extension
You can also use the AR Transaction Type Extension to determine the AR transaction type when you interface invoices to Oracle Receivables. See: AR Transaction Type Extension. You can use this extension whether you use centralized or decentralized invoicing.
See Also
Create Invoice Organization Transaction Types
Implementation Options
Importing Transactions Using AutoInvoice
