The below given query provides the SQL Data extract for Credit Memo Balance Due.

SELECT HZ_ACCT.ACCOUNT_NUMBER, NVL (SUM (AR_PAY_SCH.AMOUNT_DUE_REMAINING), 0) CM_BALANCE_DUE
FROM
HZ_CUST_ACCOUNTS_ALL HZ_ACCT,
HZ_CUST_ACCT_SITES_ALL HCASA,
HZ_CUST_SITE_USES_ALL HCSU,
HZ_PARTY_SITES HPS,
HZ_LOCATIONS LOC,
RA_CUSTOMER_TRX_ALL RCTA,
RA_CUST_TRX_LINE_GL_DIST_ALL RA_CUS_TRX_GL_DIST,
AR_PAYMENT_SCHEDULES_ALL AR_PAY_SCH,
GL_CODE_COMBINATIONS CC
WHERE 1=1
AND AR_PAY_SCH.CUSTOMER_ID = HZ_ACCT.CUST_ACCOUNT_ID
AND AR_PAY_SCH.CUST_TRX_TYPE_ID = RCTA.CUST_TRX_TYPE_ID
AND HCASA.PARTY_SITE_ID = HPS.PARTY_SITE_ID
AND LOC.LOCATION_ID = HPS.LOCATION_ID
AND HZ_ACCT.CUST_ACCOUNT_ID = HCASA.CUST_ACCOUNT_ID
AND HCASA.CUST_ACCT_SITE_ID = HCSU.CUST_ACCT_SITE_ID
AND AR_PAY_SCH.CUSTOMER_ID = HCASA.CUST_ACCOUNT_ID
AND AR_PAY_SCH.CUSTOMER_SITE_USE_ID = HCSU.SITE_USE_ID
AND RCTA.CUSTOMER_TRX_ID = AR_PAY_SCH.CUSTOMER_TRX_ID
AND RCTA.CUSTOMER_TRX_ID = RA_CUS_TRX_GL_DIST.CUSTOMER_TRX_ID
AND RA_CUS_TRX_GL_DIST.CODE_COMBINATION_ID = CC.CODE_COMBINATION_ID
AND RA_CUS_TRX_GL_DIST.ACCOUNT_CLASS = 'REV'
AND NVL (HCSU.STATUS, 'A') = 'A' 
AND AR_PAY_SCH.CLASS = 'CM'
AND AR_PAY_SCH.status = 'OP'
AND HCSU.SITE_USE_CODE = 'BILL_TO'
AND TRUNC (AR_PAY_SCH.GL_DATE) <= :P_ENTER_DATE
AND AR_PAY_SCH.TRX_DATE <= :P_ENTER_DATE
AND HZ_ACCT.ACCOUNT_NUMBER = :P_ENTER_ACCT_NUMBER
GROUP BY HZ_ACCT.ACCOUNT_NUMBER,AR_PAY_SCH.AMOUNT_DUE_REMAINING

 

The blog provides the Oracle EBS R12 SQL to check Customer Transaction Balances. The Oracle EBS R12 Account Receivable AR Invoices with Outstanding Customer Transaction Balances, AR Invoices which Over Due date are retrieved for AR Reconciliation

The below given SQL Query provides the data extract to check Customer Transaction Balances

SELECT HZ_ACCT.ACCOUNT_NUMBER, NVL (SUM (AR_PAY_SCH.AMOUNT_DUE_REMAINING), 0) INVOICE_BALANCE
FROM
HZ_CUST_ACCOUNTS_ALL HZ_ACCT,
HZ_CUST_ACCT_SITES_ALL HCASA,
HZ_CUST_SITE_USES_ALL HCSU,
HZ_PARTY_SITES HPS,
HZ_LOCATIONS LOC,
RA_CUSTOMER_TRX_ALL RCTA,
RA_CUST_TRX_LINE_GL_DIST_ALL RA_CUS_TRX_GL_DIST,
AR_PAYMENT_SCHEDULES_ALL AR_PAY_SCH,
GL_CODE_COMBINATIONS CC
WHERE 1=1
AND AR_PAY_SCH.CUSTOMER_ID = HZ_ACCT.CUST_ACCOUNT_ID
AND AR_PAY_SCH.CUST_TRX_TYPE_ID = RCTA.CUST_TRX_TYPE_ID
AND HCASA.PARTY_SITE_ID = HPS.PARTY_SITE_ID
AND LOC.LOCATION_ID = HPS.LOCATION_ID
AND HZ_ACCT.CUST_ACCOUNT_ID = HCASA.CUST_ACCOUNT_ID
AND HCASA.CUST_ACCT_SITE_ID = HCSU.CUST_ACCT_SITE_ID
AND AR_PAY_SCH.CUSTOMER_ID = HCASA.CUST_ACCOUNT_ID
AND AR_PAY_SCH.CUSTOMER_SITE_USE_ID = HCSU.SITE_USE_ID
AND RCTA.CUSTOMER_TRX_ID = AR_PAY_SCH.CUSTOMER_TRX_ID
AND RCTA.CUSTOMER_TRX_ID = RA_CUS_TRX_GL_DIST.CUSTOMER_TRX_ID
AND RA_CUS_TRX_GL_DIST.CODE_COMBINATION_ID = CC.CODE_COMBINATION_ID
AND RA_CUS_TRX_GL_DIST.ACCOUNT_CLASS = 'REV'
AND NVL (HCSU.STATUS, 'A') = 'A'
AND AR_PAY_SCH.CLASS NOT IN ('CM', 'PMT')
AND HCSU.SITE_USE_CODE = 'BILL_TO'
AND TRUNC (AR_PAY_SCH.GL_DATE) <= :P_ENTER_DATE
AND AR_PAY_SCH.TRX_DATE <= :P_ENTER_DATE
AND HZ_ACCT.ACCOUNT_NUMBER = :P_ENTER_ACCT_NUMBER
GROUP BY HZ_ACCT.ACCOUNT_NUMBER,AR_PAY_SCH.AMOUNT_DUE_REMAINING

Hi All,

The below given SQL Query for Oracle Apps Receivables (AR)  provides the main columns from the table – RA_CUSTOMER_TRX_ALL and AR_PAYMENT_SCHEDULES_ALL to get the details for the Open Invoices for a particular Customer ( enter TRX_NUMBER) or for all Customers.

SELECT
RA_CUST_TRX.STATUS_TRX,
RA_CUST_TRX.TRX_NUMBER,
RA_CUST_TRX.TRX_DATE,
RA_CUST_TRX.BILLING_DATE,
RA_CUST_TRX.BATCH_ID,
RA_CUST_TRX.BATCH_SOURCE_ID,
RA_TERMS.NAME || '-' || RA_TERMS.DESCRIPTION   TERM_NAME,
RA_CUST_TRX.INVOICE_CURRENCY_CODE TRX_CURR,
APS.ORG_ID,
APS.CUSTOMER_ID,
APS.CUSTOMER_TRX_ID,
--APS.TRX_NUMBER,
--APS.TRX_DATE,
APS.GL_DATE,
APS.CLASS,
APS.GL_DATE_CLOSED,
APS.STATUS PAYMENT_STATUS,
APS.INVOICE_CURRENCY_CODE,
APS.EXCHANGE_DATE,
APS.EXCHANGE_RATE_TYPE,
APS.EXCHANGE_RATE,
APS.DUE_DATE,
APS.AMOUNT_DUE_ORIGINAL,
APS.AMOUNT_DUE_REMAINING,
APS.AMOUNT_LINE_ITEMS_REMAINING,
APS.AMOUNT_APPLIED,
APS.NUMBER_OF_DUE_DATES
FROM
HZ_CUST_ACCOUNTS HZ_ACCT,
HZ_PARTIES HP,
HZ_CUST_ACCT_SITES_ALL HCASA,
HZ_CUST_SITE_USES_ALL HCSUA,
HZ_PARTY_SITES HPS_BILL,
RA_CUST_TRX_LINE_GL_DIST_ALL RCT,
RA_TERMS RA_TERMS,
RA_CUSTOMER_TRX_ALL RA_CUST_TRX,
RA_CUSTOMER_TRX_LINES_ALL RA_TRX_LINES,
RA_CUST_TRX_TYPES_ALL RT,
AR_PAYMENT_SCHEDULES_ALL APS
WHERE 1 = 1
AND RA_CUST_TRX.CUSTOMER_TRX_ID = RA_TRX_LINES.CUSTOMER_TRX_ID
AND RA_CUST_TRX.CUSTOMER_TRX_ID = APS.CUSTOMER_TRX_ID
AND RA_CUST_TRX.CUST_TRX_TYPE_ID = RT.CUST_TRX_TYPE_ID
AND RA_CUST_TRX.BILL_TO_CUSTOMER_ID = HZ_ACCT.CUST_ACCOUNT_ID
AND RA_CUST_TRX.ORG_ID = APS.ORG_ID
AND RA_CUST_TRX.TERM_ID = RA_TERMS.TERM_ID
AND RCT.CUSTOMER_TRX_ID = APS.CUSTOMER_TRX_ID
AND RCT.CUSTOMER_TRX_ID = RA_CUST_TRX.CUSTOMER_TRX_ID
AND RCT.CUSTOMER_TRX_ID = RA_TRX_LINES.CUSTOMER_TRX_ID
AND RCT.CUSTOMER_TRX_LINE_ID = RA_TRX_LINES.CUSTOMER_TRX_LINE_ID
AND HP.PARTY_ID = HZ_ACCT.PARTY_ID
AND HCASA.CUST_ACCOUNT_ID = RA_CUST_TRX.BILL_TO_CUSTOMER_ID
AND HCASA.CUST_ACCT_SITE_ID = HCSUA.CUST_ACCT_SITE_ID
AND HCSUA.SITE_USE_ID = RA_CUST_TRX.BILL_TO_SITE_USE_ID
AND HPS_BILL.PARTY_SITE_ID = HCASA.PARTY_SITE_ID
AND APS.AMOUNT_DUE_REMAINING <> 0
AND APS.STATUS = 'OP'
AND HCSUA.SITE_USE_CODE = 'BILL_TO'
AND HZ_ACCT.STATUS = 'A'
AND HCASA.STATUS = 'A'
AND HCSUA.STATUS = 'A'
AND RA_CUST_TRX.COMPLETE_FLAG = 'Y'
AND RA_TRX_LINES.LINE_TYPE IN ('FREIGHT', 'LINE')
--AND HZ_ACCT.ACCOUNT_NUMBER = :P_ENTER_CUSTOMER_NUMBER
ORDER BY RA_CUST_TRX.TRX_NUMBER DESC,
RA_CUST_TRX.TRX_DATE DESC

The below given are the common AR setup to be done in Oracle Apps –  Oracle Receivables for the transaction processing.

Oracle Receivable Setup Description	Required ?
Define Sets Of Books	Yes
Use The Account Generator	Yes
Define System Item Flexfields Structure	Yes
Define Organizations	Yes
Define Territory Flexfield	No
Define Sales Tax Location Flexfields structure	Yes
Setup Flexible Address Formats	No
Maintain Countries & Territories	No
Define the Transaction Flexfield Structure	No
Define AutoCash Rule Sets	No
Define QuickCodes	No
Define AutoInvoice Line Ordering Rules	No
Define AutoInvoice Grouping Rules	No
Define System Options	Yes
Define Payment Terms	Yes
Define Accounting Rules	No
Maintain Accounting Periods	Yes
Define AutoAccounting	Yes
SetUpCash Basis Accounting	No
Define Transaction Types	Yes
Define Transaction Sources	Yes
Define Collectors	Yes
Define Adjustments Approval Limits	Yes
Define remittance Banks	Yes
Define distribution sets	No
Define receivable activities	Yes
Define receipts classes	Yes
Define Payment Methods	Yes
Define Receipts Sources	Yes
Define aging buckets	No
Define Statement cycles	No
Define Statement messages	No
Define dunning letters	No
Define dunning letters Sets	No
Define Territories	No
Define Sales persons	Yes
Define Profile options	Yes
Define tax codes and rate	Yes
Define customer profile classes	Yes
Define Customer	Yes
Define remit to address	Yes
Define customer relationship	No
Define Customer banks	No
Define Lock Boxes	No
Define the transmission formats	No
Define receipt programmes	No
Define UOM Classes	No
Define UOM	Yes
Define Standard memo lines	No
Define Item tax rate exceptions	No
Define tax exemptions	No
Define document sequences	No

The blog provides the steps to Create Oracle EBS R12 Account Receivables (AR) Receipt.

Oracle EBS R12 Account Receivables (AR) Receipt Types

In Oracle Receivables, Receipts can be created of 2 types:

1. Standard Receipts: Standard Receipts includes Cash or Check received from the Customer in the exchange of goods or services provided. These are termed as ‘Cash Receipts’ also.
2. Miscellaneous Receipts: Miscellaneous Receipts includes the revenue earned from the interest, refunds, investments or any other nonstandard item.

Points to Consider for Oracle EBS R12 AR Receipt Creation

1. Receipts can be applied to the transactions in the Open or Future Accounting Periods.
2. Charge back and adjustments can be created against the receipts
3. Receipts can be applied to Invoices, Debit Memos, Credit Memos, on-account credits and chargebacks.
4. Receipts can be applied partially or fully to a single Debit item or to several Debit items.
5. Receipts can be applied to other open receipts

Oracle EBS R12 AR Receipt Status

The Oracle EBS R12 provides the different Account Receivables (AR) Receipt status to retrieve the current state of the created AR Receipts and its reconciliation.

The Oracle Apps AR Receipt Status can be referred here Oracle Apps R12 AR Receipt Status

Transaction Source Setup describes the behavior for the  Account  Receivable (AR) transactions. Whenever a transaction is processed in Oracle Apps R12 and associated to the transaction source , it validates with the Transaction Source Setup to determine the  validations to be performed.

The below given are the field details for the Transaction Source Setup and the field validations in the Transaction Source Tabs to be provided:

1. Name :  Transaction Source Name

     2. Type:   Transaction Source type could be Manual / Imported

• Manual: Prefer manual batch sources with transactions that  has been entered  manually in the Transaction and Transactions Summary windows

• Imported: Prefer imported batch sources to import transactions into Receivables using Auto Invoice

3. Active :  Transaction Source can be made Inactive by unchecking the check box

4.  Automatic Batch Numbering:  If you need to automatically generate batch number for the transaction source, check the Automatic Batch Numbering check box and enter a Last Number.

5. Automatic Transaction Numbering:  If you need to automatically generate  number for new transactions for the transaction source, check the Automatic Transaction numbering check box and enter a Last Number.

6. Effective Dates:  The Start date is the current date when transaction source is being created and made Active . If  no end date is provided , then transaction batch source will be active indefinitely

Invalid Line: provides the option for how AutoInvoice to handle imported transactions with Invalid Lines by entering either ‘Reject Invoice’ or ‘Create Invoice’ .

Create Clearing : Select this option if you want to compare the revenue amount to be equal to  ( Unit Selling Prices X Quantity) for each transaction line.

GL Date in a Closed Period: provides the option for how AutoInvoice to handle imported transactions that have lines in the Interface Lines table which are in a closed period

• Adjust:  When selected this option, AutoInvoice automatically adjust the GL dates to the first GL date of the next open or future enterable period, enter ‘Adjust’ in the GL Date in a Closed Period field
• Reject: When selected this option, AutoInvoice  rejects the transactions

Grouping Rule: AutoInvoice uses the following hierarchy to determine which rule to use:

• The grouping rule specified in the Transaction Sources window for the batch source of the transaction line.

• The grouping rule specified in the Customer Profile Classes window for the bill-to customer and bill-to site of the transaction line.

• The grouping rule specified in the Customer Profile Classes window for the bill-to customer of the transaction line.

• The default grouping rule specified in the System Options window.

Customer Information – Values Passed (ID, Value, Segment)

• Bill To and Ship To
• Address
• Contact
• Payment Method
  The value of ‘Id’ or ‘Segment’ indicates if the AutoInvoice to be validated with  the identifier or the value for the Customer Information

Invoicing Rule:  indicates if  AutoInvoice will  validate the Invoicing Rule  for the batch source using identifiers or values

Accounting Rule:  indicates if  AutoInvoice will  validate the Accounting Rule  for the batch source using identifiers or values

Accounting Flexfield: indicates if  AutoInvoice will  validate the Accounting Flexfield  for the batch source using identifiers or values

Payment Terms : indicates if  AutoInvoice will  validate the Payment Terms for the batch source using identifiers or values

Revenue Account Allocation:  indicates if the AutoInvoice to validate the Revenue Account Allocation data for the batch source using Amount or Percent

The below given are the Account Receivables (AR) Tables used for AR Setup , AR Transactions.

AR Table Name	AR Table Description
AR Setup tables
RA_BATCH_SOURCES	AR Table for storing the transaction sources
RA_CUST_TRX_TYPES_ALL	The table stores information about each transaction type for all classes of transactions, for example, invoices, commitments, and credit memos
AR_RECEIPT_CLASSES	The table stores the different receipt classes that you define
AR_RECEIPT_METHODS	The table stores information about Payment Methods, receipt attributes that you define and assign to Receipt Classes to account for receipts and their applications
AR Transaction Tables
RA_CUSTOMER_TRX_ALL	AR Transaction Header table
RA_CUSTOMER_TRX_LINES_ALL	AR Transaction Lines table along with Tax lines
RA_CUST_TRX_LINE_GL_DIST_ALL	AR Distribution Table  for Transaction Lines
RA_CUST_TRX_LINE_SALESREPS_ALL	Salesrep information for Transaction Lines
AR Transaction Interface Tables
RA_INTERFACE_LINES_ALL	AR Transaction Lines interface
RA_INTERFACE_SALESCREDITS_ALL	AR Transaction Sales credit information
RA_INTERFACE_DISTRIBUTIONS_ALL	AR Transaction Distribution information
RA_INTERFACE_ERRORS_ALL	AR Transaction errors table
AR_PAYMENTS_INTERFACE_ALL	AR Interface table to import receipts
AR_INTERIM_CASH_RECEIPTS_ALL	AR Lockbox transfers the receipts that pass validation to the interim tables
AR_INTERIM_CASH_RCPT_LINES_ALL	AR Lockbox transfers the receipts that pass validation to the interim tables
AR Receipt Tables
AR_CASH_RECEIPTS_ALL	The Table provides  Cash Receipt Header details
AR_RECEIVABLE_APPLICATIONS_ALL	The Table provides AR Receipt Application details .
AR_PAYMENT_SCHEDULES_ALL	The table is updated when an activity occurs against an invoice, debit memo, charge back, credit memo, on-account credit, bills receivable . The table stores all of the activity that is contained for the life cycle of a receipt
AR_CASH_RECEIPT_HISTORY_ALL	The table provides the complete history of the receipt and each row represents a step for the receipt execution . The status field for that row tells you which step the receipt has reached. The  statuses could be Approved, Confirmed, Remitted, Cleared, and Reversed.

Transaction Types are used in Oracle Account Receivables (AR)  to define the accounting for the  debit memos, credit memos, on-account credits, chargebacks, commitments, and invoices which are created  in Oracle Account Receivables (AR) . Transaction types  are also used to determine whether transaction(s)  updates  customers’ balances and if the Account Receivables  (AR) posts the transactions to the General Ledger

Oracle Account Receivables (AR)  provides the following transaction types:

• Invoice
• Credit Memo ,
• Projects Credit Memo ,
• Projects Invoice ,
• Intercompany

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Transaction Types

Field details for the Transaction Types Setup :

Operating Unit:  OU which will use these transaction type

Name : Name of the Transaction Type

Description:  Description of the Transaction Type

Class:   Invoice, Chargeback, Credit Memo, Debit Memo, Deposit, or Guarantee

Legal Entity: provide the Legal Entity Name

Open Receivables: Select if transactions with the defined  type is to be used to  update customer balances

Post to GL: Select if transactions with the defined  type is to be posted to General Ledger  . The check box must be checked if the class is Deposit or Guarantee. If  transaction is defined as  a ‘void’ transaction type, do not check this box

Create Sign :  For Credit Memo , set value as  Negative Sign , for others set value as Positive Sign

Printing Option:  Default Printing Option for the transaction type

Transaction Status :  Open / Closed / Pending / Void

Natural Application: The check box must be checked if the class is Deposit or Guarantee

Allow Freight :  To allow freight to be entered for transactions with this transaction type, check the Allow Freight check box

Receivable Account : Provide the  Receivable Account for transactions with the transaction type. Receivables uses it with  AutoAccounting definition, to determine the receivable accounts for transactions with these transaction types. Receivables creates a receivables transaction record using this account so you can transfer to your general ledger and create a journal entry if Post To GL is Yes for this transaction type.

For guarantee transaction types, provide the Accounting Flexfield for the Unbilled Receivable account

For Guarantee and Deposit transaction types, provide the Accounting Flexfield for the Unearned Revenue account if Allow Freight is set to No

Credit Memo transaction types Receivable Account is not required

SQL Query to get the list of Active Transaction Types in Oracle Apps R12 AR:

SELECT RCTTA.ORG_ID,RCTTA.NAME , RCTTA.DESCRIPTION, RCTTA.POST_TO_GL, RCTTA.STATUS, RCTTA.ACCOUNTING_AFFECT_FLAG, RCTTA.DEFAULT_STATUS ,  RCTTA.ALLOW_FREIGHT_FLAG, RCTTA.ALLOW_OVERAPPLICATION_FLAG, RCTTA.START_DATE, RCTTA.TAX_CALCULATION_FLAG,RCTTA.SET_OF_BOOKS_ID FROM RA_CUST_TRX_TYPES_ALL  RCTTA WHERE RCTTA.STATUS =’A’

Oracle Account Receivables (AR) defines Payment Terms Setup for the Customers in Oracle Apps R12.  Payment terms are used to determine the amount of each installment. Oracle Account Receivables allows to distribute tax and freight charges across all installments, or allocate all freight and tax amounts in the first installment of a split term invoice. Oracle Account Receivables shows all the active payment terms defined in the setup  as list of values (LOV)  in the Customers, Customer Profile Classes, and Transactions windows.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Payment Terms

Oracle Account Receivables (AR) provides two predefined payment terms:

• 30 NET: The balance of the transaction is due within 30 days.
• IMMEDIATE: The balance of the transaction is due immediately (i.e. on the transaction date).  These payment terms can be user  with Chargebacks and Debit memos

Please find below the details for the fields being used in the Payment Terms Setup

Name :  Name provided for the Payment Term

Description:  provides the purpose for what payment term is being defined

Installment Options:  Include tax and freight in first installment

Base Amount :  Default value is 100 but can be changed as per requirement.

If the Relative Amount is different than the Base Amount , then Account Receivables uses the below given equation to determine the original amount due for each installment of invoices to which you assign the payment term

Amount Due = Relative Amount/Base Amount * Invoice Amount

If  Installment Options Include tax and freight’ as the First Installment field value for a payment term, the base amount and the relative amounts  indicate how the original line amounts of the invoices  are distributed across different installments

Amount Due = (Relative Amount/Base Amount * Base Line Amount) + Base Freight Amount + Base Tax Amount

Print Lead Days : If  transactions assigned to the payment term to be printed before the due date, enter a number of Print Lead Days

Discount Basis:   Account Receivables uses this value  when calculating discounts for the invoices

•  Invoice Amount:                    Calculate the discount amount based on the sum of the tax, freight charges, and line amounts of your invoices.
• Lines Only:                             Calculate the discount amount based on only the line amounts of your invoices.
• Lines, Freight Items and Tax: Calculate the discount amount based on the amount of line items, freight, and tax of your invoices, but not freight and charges at the invoice header level.
• Lines and Tax, not Freight Items and Tax: Calculate the discount amount based on the line items and their tax amounts, but not the freight items and their tax lines, of your invoices

Effective Date:  Range of Effective Dates for this payment term. If no end date provided, the payment term will be active indefinitely

Receivables uses the following hierarchy to determine the default payment term for your transactions, stopping when one is found:

• Bill-to site, defined at the Site level profile of the customer record
• Customer, defined  at the Account level profile of the customer record
• Transaction Type

NOTE:  Once a payment term has transactions associated to it, it cannot be updated.  A new payment term would need to be created.

SQL Query to get the defined Payment Terms in Oracle Apps R12:

SELECT RA.TERM_ID, RA.NAME PAYMENT_TERM_NAME , RA.DESCRIPTION DESCRIPTION , RA.BASE_AMOUNT, RA.PREPAYMENT_FLAG, RA.CYCLE_NAME FROM APPS.RA_TERMS  RA

The blog provides the Oracle EBS R12 Navigation Path for the main AR Windows

Window Name	Navigator Path
Account Details	Collections->Account Details
Account Overview	Collections->Account Overview
Accounting Calendar	Set Up->Financials->Calendars-> Periods
Accounting Periods	Accounting->Open/Close Periods
Aging	Collections->Aging
Alternate Name Receipt Matches	Customers->Alternate Name Matches
Adjustment Approval Limits	Set Up->Transactions->Adjustment Limits
Aging Buckets	Set Up->Collections->Aging Buckets
Aging	Collections->Aging
Approve Adjustments	Control->Adjustments->Approve Adjustments
Assign Flexfield Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Assign Key Flexfield Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Assign Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
AutoCash Rule Sets	Set Up->Receipts->AutoCash Rule Sets
AutoInvoice Grouping Rules	Set Up->Transactions->AutoInvoice ->Grouping Rules
Automatic Accounting	Set Up->Transactions-> AutoAccounting
Automatic Payment Programs	Set Up->Receipts->Receipt Programs
Bank Charges	Set Up->Receipts->Bank Charges
Banks	Set Up->Receipts->Bank
Category Codes	Set Up->Transactions->Item-> Category->Define->Category
Category Sets	Set Up->Transactions->Item-> Category Define->Default Sets
Clear/Risk Eliminate	Receipts->Clear/Risk Eliminate
Collectors	Set Up->Collections->Collectors
Completed Requests	Control->Requests->View
Concurrent Requests Summary	Control->Concurrent
Conversion Rate Types	Set Up->Financials->Currencies-> Rates->Types
Copy Transactions	Transactions->Copy
Correspondence	Collections->Correspondence
Countries and Territories	Set Up->System->Countries
Create AutoAdjustments	Control->Adjustments->Create AutoAdjustments
Credit Transactions	Transactions->Credit Transactions
Cross Validation Rules	Set Up->Financials->Flexfields-> Key-> Rules
Currencies	Set Up->Financials->Currencies-> Define
Customer Accounts	Collections->Customer Account
Customer Calls	Collections->Record A Call
Customer Interface	Interfaces->Customer
Customer Merge	Customers->Merge
Customer Profile Classes	Customers->Customer Profile Classes
Customers Quick	Customers->Customer Quick
Customers Standard	Customers->Customer Standard
Customers Summary	Customers->Customer Summary
Daily Rates	Set Up->Financials->Currencies-> Rates->Daily
Default Category Sets	Set Up->Transactions->Item-> Category->Define->Sets
Define Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Descriptive Flexfield Segments	Set Up->Financials->Flexfields-> Descriptive->Segments
Distribution Sets	Set Up->Receipts->Distribution Sets
Document Sequences	Application->Document->Define (use System Administrator responsibility)
Dunning History	Collections->Account Details. Choose Dunning History button.
Dunning Letter Sets	Set Up->Print->Dunning Letter Sets
Dunning Letters	Set Up->Print->Dunning Letters
F4 Define Organization	Set Up->System->Organization
Freight Carriers	Set Up->System->QuickCodes-> Freight
GL Accounts	Set Up->Financials->Combinations
Interface: Customer	Interfaces->Customer
Interfaces: AutoInvoice	Interfaces->AutoInvoice
Inventory Delete Items	Set Up->Transactions->Item->Delete Items
Invoice Line Ordering Rules	Set Up->Transactions->AutoInvoice ->Line Ordering
Invoicing and Accounting Rules	Set Up->Transactions->Rules
Item Status Codes	Set Up->Transactions->Item->Status
Item Tax Rate Exceptions	Set Up->Tax->Exceptions
Key Flexfield Security Rules	Set Up->Financials->Flexfields->Key ->Security->Define
Lockbox Transmission History	Receipts->Lockbox->Transmission History
Lockboxes	Set Up->Receipts-> Lockbox->Lockbox
Lockbox Transmission Data	Receipts->Lockbox->Maintain Transmission Data
Memo Lines	Set Up->Transactions->Memo Lines
Open/Close Accounting Periods	Accounting->Open/Close Periods
Payment Methods	Set Up->Receipts->Receipt Classes
Payment Programs	Set Up->Receipts->Receipt Programs
Payment Terms	Set Up->Transactions->Payment Terms
Period Rates	Set Up->Financials->Currencies-> Rates->Period
Period Types	Set Up->Financials->Currencies-> Rates->Type
Print Accounting Reports	Reports->Accounting
Print Dunning	Print->Documents->Dunning
Print Invoices	Print->Documents->Invoices
Print Statements	Print->Documents->Statements
Profile User Values	Control->Profile Options
Quick Codes Demand Class	Set Up->System->QuickCodes-> Demand Class
Quick Find by Alternate Name	Customers->Quick Find by Alternate Name
Receipt Batches Summary	Receipts->Receipts Summary
Receipt Batches	Receipts->Batches
Receipt Classes	Set Up->Receipts->Receipt Classes
Receipt Sources	Set Up->Receipts->Receipt Sources
Receipts Summary	Receipts->Receipts Summary
Receipts	Receipts->Receipts
Receivables Activities	Set Up->Receipts->Receivable Activity
Receivables Quick Codes	Set Up->System->QuickCodes-> Receivable
Remit-To Addresses	Set Up->Print->Remit To Addresses
Remittances Summary	Receipts->Remittances
Remittances	Receipts->Remittances
Request Sets (User Mode)	Control->Requests->Set
Requests Accounting	Reports->Accounting
Requests Collection	Reports->Collections
Requests Listing	Reports->Listing
Requests Other	Reports->Other
Requests Submit	Control->Requests->Run
Run AutoInvoice	Interfaces->AutoInvoice
Run Customer Interface	Interfaces->Customer
Run General Ledger Interface	Interfaces->General Ledger
Run Revenue Recognition	Control->Accounting->Revenue Recognition
Run Tax Rate Interface page	Interfaces->Tax Rate
Sales Tax Rates	Set Up->Tax->Sales Tax Rates
Salespersons	Set Up->Transactions->Salespersons
Scheduler	Collections->Scheduler
Segment Values	Set Up->Financials->Flexfields-> Descriptive->Values
Set of Books	Set Up->Financials->Books
Shorthand Aliases	Set Up->Financials->Flexfields->Key ->Aliases
Standard Memo Lines	Set Up->Transactions->Memo Lines
Standard Messages	Set Up->Print->Standard Messages
Statement Cycles	Set Up->Print->Statement Cycles
Submit Lockbox Processing	Interfaces->Lockbox
System Options	Set Up->System->System Options
Tax Authorities	Set Up->Tax->Authorities
Tax Codes and Rates	Set Up->Tax->Codes
Tax Exemptions	Set Up->Tax->Exemptions
Tax Locations and Rates	Set Up->Tax->Locations
Tax Options	Set Up->Tax->GL Tax Assignments
Territories	Set Up->Transactions->Territories
Transaction Batches Summary	Transactions->Batches Summary
Transaction Batches	Transactions->Batches
Transaction Overview	Collections->Transaction Overview
Transaction Sources	Set Up->Transactions->Sources
Transaction Summary	Transactions->Transaction Summary
Transaction Types	Set Up->Transactions->Transaction Types
Transactions	Transactions->Transactions
Transactions Summary	Transactions->Transactions Summary
Transmission Formats	Set Up->Receipts->Lockbox Transmission
Units of Measure Classes	Set Up->System->UOM->Class
Units of Measure	Set Up->System->UOM->UOM
Viewing Requests	Other->Requests->View

In Oracle EBS R12 , Account Receivables (AR) Receipts could have the below given status during the AR transaction processing phase.

Oracle EBS R12 AR Receipt Approved Status

The status ‘APPROVED’ indicates that the receipt has been approved for automatic receipt creation. This status is only valid for automatic receipts.

Oracle EBS R12 AR Receipt Confirmed Status

The status ‘CONFIRMED’ indicates that the customer has approved the application of this receipt and their account balances have been updated within Receivables.
The status ‘CONFIRMED’ is only valid for automatic receipts.

Oracle EBS R12 AR Receipt Remitted Status

The status ‘REMITTED’ indicates that  the receipt has been remitted. The status ‘REMITTED’ is valid for both automatic and manually entered receipts.

Oracle EBS R12 AR Receipt Cleared Status

The status ‘CLEARED’ indicates that payment of this receipt was transferred to bank account and the bank statement has been reconciled within Receivables. The status ‘CLEARED’  is valid for both automatic and manually entered receipts

Oracle EBS R12 AR Receipt Reversed Status

The status ‘REVERSED’ indicates that receipt has been reversed. You can reverse a receipt when the customer stops payment on a receipt or could be a wrong entry    being     done manually.  if a receipt comes from an account with non-sufficient funds or if you want to re-enter and reapply it in Receivables , then Receipt needs to be ‘REVERSED’.

You can reverse cash receipts and miscellaneous transactions