Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner ...dbmanagement.info/Books/MIX/8.EBS_R12.1_AR_Implement_Customer... · Oracle E-Business Suite R12.1 Accounts

<Insert Picture Here><Insert Picture Here>

-1-

Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner

Boot Camp Training Courseware

The following is intended to outline our general

product direction. It is intended for information

Safe Harbor Statement

product direction. It is intended for information

purposes only, and may not be incorporated into any

contract. It is not a commitment to deliver any

material, code, or functionality, and should not be

relied upon in making purchasing decisions.

The development, release, and timing of any

features or functionality described for Oracle’s

products remains at the sole discretion of Oracle.

-2-For Oracle employees and authorized partners only. Do not distribute to third parties.

© 2009 Oracle Corporation – Proprietary and Confidential

products remains at the sole discretion of Oracle.

Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:

1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and

copy the information, documents, and the online training courses (collectively, “Materials") found on this

Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s

Oracle Training Materials – Usage

Agreement

Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s

employees only. The Materials may not be used for training, promotion, or sales to customers or other

partners or third parties.

2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other

third party at no time has any right to resell, redistribute or create derivative works from the Materials.

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any

Materials. Materials are provided "as is" without warranty of any kind, either express or implied,

including without limitation warranties of merchantability, fitness for a particular purpose, and non-

infringement.



4. Under no circumstances shall Oracle or the Oracle Authorized Delivery Partner be liable for any loss,

damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site

of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against

any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys'

fees) arising out of Partner’s use of the Materials.

5. Reference materials including but not limited to those identified in the Boot Camp manifest can not be

redistributed in any format without Oracle written consent.

Key Content Contributors

Contributing Companies



• Order to Cash Lifecycle overview

• Overview of Oracle Receivables Process

• Managing Parties and Customer Accounts

Bootcamp Objectives

• Process Invoices Using Auto Invoice

• Process Invoices

• Bill Presentment Architecture

• Credit Management

• Implement Customer Invoicing

• Receipts

• Implement Receipts



• Implement Receipts

• Tax Processing

• Period Closing Process

• Annexure

Section Objectives

Setup information related to invoicing

Major implementation considerations for customer invoicing Major implementation considerations for customer invoicing



Transactions: Required Setup

Before you can use customer invoices, you must complete these setups:

•Customers

•Receivables Transaction Types•Receivables Transaction Types

• AutoAccounting

• Billing Cycles

• Payment Terms

• Transaction Sources

•Remit-To Addresses

• System and Profile Options



Transaction types determine:

• Transaction class: debit memo, credit memo, on-account credit,

chargeback, commitment, invoice, bills receivable.

Receivables Transaction Types

•Natural Application setting.

• If the transaction can be posted to General Ledger

• If the transaction is an open receivable, that is, updates customer balances

for debit memos, credit memos, chargebacks, and on-account credits.

• If the transaction excludes late charges.

• If freight can be entered.



• If a tax classification code defaults to the transaction line.

•Default credit memo type for an invoice.

•Default invoice type for a commitment.

•Creation sign.

Receivables Transaction Types



Invoice

Salesperson = Joe AdamsTransaction Type = Invoice1. Wrist Pad 2 @ 1,000

Revenue Account = 01-100-4505-201

Auto Accounting


Account Type = RevenueSegment Constant Value Table Name

CO 01

CC Salesreps

Account Trans. Types

Salesperson = Joe Adams




Account Trans. Types

Product Standard Line

Transaction Type = Invoice

Revenue Account = 02-000-4505-100Standard Line = Wrist Pad


Auto Accounting



Balance Forward Billing Cycle



Payment Terms



Transaction Sources



Remit-to Addresses



System Options



Profile Options

• AR: Allow Update of Existing Sales Credits

• AR: Change Customer on Transaction

• AR: Default Exchange Rate Type

• AR: Override Adjustment Activity Account Option

• AR: Transaction Batch Source



• AR: Use Invoice Accounting For Credit Memos

Transactions: Optional Setup

The following are optional setup steps for customer invoices:

• Accounting Rules

• Salespeople

• Standard Memo Lines

• Document Sequencing

• Statements



• Statements

• Balance Forward Billing

• Tiered Interest Rates

Accounting Rules



Standard Memo Lines



Document Sequencing

Steps to enable document sequencing:

• Enable the sequence numbering profile option• Enable the sequence numbering profile option

• Define sequences

• Assign sequences to categories



Statements: Aging Bucket



Statements: Statement Cycles



Statements: Standard Messages



Section Objectives

Setup information related to invoicing

Major implementation considerations for customer invoicing Major implementation considerations for customer invoicing



Transaction types to be defined in the following order:

•Credit Memo

• Invoice

Implementation Consideration: Transaction Types

•Debit Memo

•Chargeback

•Bill Receivables

•Deposit

•Guarantee



Implementation Considerations: Transactions

Payment Terms:

• Discounting?• Discounting?

• Balance Forward Billing?

• Split Payment Terms?

• Allocating Tax and Freight?AutoAccounting

Source of Table

Transaction Batch Source?



Oracle SystemAutoInvoice

ID

Non Oracle Systems

Value

Implementation Considerations: Remit-to Address

• Define lockbox addresses as remit-to addresses to let customers know

where to send payment.

• To catch any missing assignments, set up a remit-to address assigned

to a default location. If you enter or import an invoice with an address

that does not correspond to any of your assignments, it uses the

default remit-to address.



Implementation Considerations: Function Security

Function Name

Transactions: Complete

Activities That Can Be Restricted

Complete transactions

Transactions: Dispute

Transactions: Copy

Transactions: Print

Inv: View

Inv: Enter

Place transactions in dispute

Copy transactions

Print transactions

View invoices



Inv: Enter

Inv: Update

Inv: Delete

Enter invoices

Update invoices

Delete invoices

Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner ...dbmanagement.info/Books/MIX/8.EBS_R12.1_AR_Implement_Customer... · Oracle E-Business Suite R12.1 Accounts

Documents