Overview of Account Receivables- 1

Oracle Receivables provides three integrated workbenches to perform most of the day-to-day Accounts Receivable operations.
Use the Receipts Workbench to perform receipt-related tasks
Use the Transactions Workbench to process invoices, debit memos, credit memos, on-account credits, chargebacks, and adjustments.
Use the Collections Workbench to review customer accounts and perform collection activities such as recording customer calls and printing dunning letters.
Use the Collections workbench to also place a customer account on credit hold, place items in dispute, view the dunning history for a transaction, and correspond with customers by recording customer calls.
Each workbench helps find critical information in a flexible way, see the results in a defined format, and selectively take appropriate action.
The Receipts and Transactions workbenches let you view records one at a time or as a group.
Detail windows display only one receipt or transaction at a time, but provide more information about the record because they contain more fields and tabbed regions.
Summary windows, by contrast, can display multiple records at once but require "drill down" to the detail window to view additional information about the current record.

Receipts Workbench: Receipts, Receipts Summary, Receipt Batches and Receipt Batches Summary
Transactions Workbench: Transactions and Transactions Summary, Transactions Batches and Transaction Batches Summary
In the Receipts and Transactions Workbenches, the Tools pulldown menu lets you perform operations in addition to those provided by the action buttons.
In the Receipts Workbench, view the sum of multiple receipts in the Receipt Totals window, and review the functional currency gain or loss resulting from a currency exchange rate adjustment in the Receipt History window.
In the Transactions window there is no Copy button, but still copy a transaction by choosing Copy To from the Tools menu.
Similarly, the Balances button does not appear in the Transactions Summary window, but can be displayed in the Transaction Balances window by choosing Balances from the Tools menu.
View the detail accounting lines for an item in the form of a balanced accounting entry (i.e., debits equal credits) by choosing View Accounting from the Tools menu.
View the detail accounting as t-accounts

Manaingng Customer

•Use all of the following methods to enter customer information, for example, addresses, phone numbers, contact names, and business purpose:
–Standard
–Quick
–Interface

Setting Customer Tax Attributes

•Standard: The taxing function refers to the tax tables to determine if the customer requires tax addition. If so, it selects the appropriate taxing method.
•Exempt: No tax addition; Manually enter the tax exemption number and reason
•Required: The taxing function always uses tax addition

Customer Addresses

•Allow multiple organization or person customers can do business at one location.
•Are global (not specific to operating units).
•Allow you to perform address validation using Vertex or TaxWare information.Have flexible address formatting with seeded and custom formats

Customer Accounts

•Customer accounts model relationships between an organization deploying Oracle Applications and an organization or person customer stored in the new customer model registry.
•Additional organizations or person customers can play roles in accounts. The new account model retains release 11i customer model features including:
–Credit profiles
–Terms of relationship (for example, discount terms)
–Customer bank accounts

Business Purposes

Business purposes describe which functions are performed at a particular customer site. Common Types of Business Purposes include:
Bill To: Send invoices to this address.
Drawee: A customer drawee is a customer site responsible for paying bills receivable.
Ship To: Send goods or services to this address. Can be different from this customer's Bill-To address.
Statements: Send customer statements to this address. Can only define one active statement business purpose for each customer.
Dunning: Send customer dunning letters to this address. Can only define one active dunning business purpose for each customer.
Legal: A legal site is responsible for all government reporting requirements.
Marketing: Send marketing collateral to this address.

Order Management Attributes in Customer Tables

Order Defaults
•Order Type
•Price List /GSA
•Item Identifier Type
•Request Date Type
•Put Lines in Sets

Scheduling Defaults

•Earliest Schedule Limit
•Latest Schedule Limit
•Push Group Schedule Date

Shipping Defaults

•Warehouse
•Freight Terms
•FOB
•Ship Method
•Over/Undership Preferences

Customer Relationships

Create customer relationships to control:
•Payment of unrelated invoices
•Sharing of pricing entitlements
•Consolidation of business addresses
•Link one customer to another.
•Enforce invoicing and receipt-application controls.
•Can only exist between two customers.
•Are not transitive: If A is related to B and B is related to C, A and C are not related.
•Can be reciprocal or nonreciprocal.
•Allow you to select a related customer’s ship-to address during order entry.

Party Relations
N) Customers->Relationships

Use the Party Relations window to view, update, and create relationships for parties. These relationships model the party registry as a realistic business world. Multiple relationships between any parties with the predefined relationship types can be created .

Object -Relationship types categorize relationships.

Profile Classes

•Use profile classes to describe and group customers with similar financial characteristics
•Use profile classes to enter new customers quickly and consistently
•When a customer is established , the customer processing function assigns it to the default (seeded) customer profile class.
•To assign the customer to a different profile class, select it from the list of values before saving.

Object Type -The party type of the object defaults in the Object Type field.

Customer Profile Class Characteristics

Credit/collections

•Credit check
•Collector
•Payment application
•Dunning letters
•Finance charges

Invoice and Statments

•Invoice line and tax printing
•Statement cycle
•Consolidated invoices

Payment Promptness
•Payment terms
•Discounts
•Grace days

Merge Customers
Merge customers to:
•Eliminate incorrect data and duplicate information
•Consolidate account site data
•Merge Customers or Sites
•Merge Individuals or Organizations
•Reflect customer account changes due to business consolidation
•Merging customer information combines all information for two customer accounts or account sites, striped by operating unit.
•Delete or inactivate the merge-from customer account and account sites uses.
•Customer Merge updates the customer information for all of the old customers transactions.

Merging Other Application Transactions

The system automatically merges all transactions associated with the merge candidates in these applications as well:
•Automotive
•Customer Service
•Inventory
•Master Scheduling /MRP Planning
•Order Management
•Payables
•Projects
•PurchasingSales and Marketing

Customers->Navigation

Use Customer Merge to consolidate any duplicate customers or transfer site use activity from a customer or site that is no longer active or has been taken over by another customer or site.