Receivable AutoLockbox for receipt import in Oracle Apps R12

What is auto lockbox in oracle applications?

Lockbox is a service provided by banks by which your company gets the customers payments directly to a lockbox interface tables and creates receipt for the payments deposited into your account. If you have an Auto Lockbox, the bank records the information that you request such as check number, check amount, numbers and amount for the invoices to be paid.
Oracle provides you with the tools to:
* Oracle interface tables for the data received from the bank
* Validate the data to see if it is accurate, complies with the controls provided
* Correct the data
* Apply the receipts to the customer’s open invoices.


A typical Lockbox transmission contains various different records, each with relevant data. Controls are provided at each level to ensure that the transmission was successful and to verify that the count and dollar amounts are consistent with what the bank indicated. These controls are at the transmission, Lockbox, batch and receipt levels. The records also contain information such as your bank account (by Lockbox) and the details for the receipts the bank received. The Lockbox may be used for checks, wires and any other receipts that you receive. You define what the data from the bank will look like and how you will use it.
Oracle Accounts Receivables Module provides the feature such that the customer can directly make the payment for their invoices in the Bank.The Bank would send a datafile in a  agreed transmission format which we we import in Receivables through AutoLockbox.After successful import the Receipts get created in the final stage.
This is a three step process
1) Validate the data file
2) Import the data file which created the Post Batch
3) Run the Post Batch  (ie Post Quick Cash) which would actually create the Receipts and applies against the Invoice on the Information provided in the data file.
Following are the main tables for auto lockbox

AR_PAYMENTS_INTERFACE_ALL
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_RCPT_LINES_ALL
AR_CASH_RECEIPTS_ALL
AR_CASH_RECEIPT_HISTORY_ALL
AR_DISTRIBUTIONS_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
AR_PAYMENT_SCHEDULES_ALL

Setup:

We  need to setup the following before running the Lockbox process:

1) Bank and Bank Accounts: You define your internal bank accounts in Accounts Receivables. This is the bank account where the customer payments are deposited.

2) Receipt Class: The Receipt Class determines the processing steps for the receipts and you assign Receipt Methods to your Receipt Class. The processing steps for any Receipt include confirmation, remittance and reconciliation.

3) Receipt Method: Receipt Method is assigned to a receipt class and it determines how to account for the receipts using the Receipt Class. For one Receipt Class, you can have more than one Receipt Methods. You associate bank accounts and the GL account combinations for Cash, Remittance, and Bank Charges etc with the Receipt Method.

4) Receipt Source: You define Receipt Batch Sources to provide default values for Receipt Class, Receipt Method and the Remittance Bank Account. Your Receipt Source also determines if the batch numbering system is manual or automatic.

5) Lockbox: Define a lockbox for your Lockbox service from each bank. The lockbox setup includes a Lockbox number (You get a Lockbox number from your bank).

6) Lockbox Transmission Formats: Oracle Receivables AutoLockbox uses the Transmission format while importing the data from the lockbox file into Receivables. Transmission formats indicate how the data in the Lockbox file is organized.

7) AutoCash Rule Sets: AutoCash Rule Sets determines the sequence of AutoCash Rules that Post QuickCash program uses to apply the receipt amount to the customer account open items.

8) Control file: A Control file is a sql loader file to load the lockbox file in Receivables payment interface table (ar_payments_interface_all). This file should have the ‘.ctl’ extension and should be placed in the $AR_TOP/bin directory.

AutoCash

AutoCash Rule Sets determines the sequence of AutoCash Rules that Post QuickCash program uses to apply the receipt amount to the customer account open items. If none of the AutoCash Rules apply, the remaining amount is placed as Unapplied or On-Account depending on the Remaining Remittance Amount option specified in your

AutoCash Rule Set.

You can provide more than one AutoCash Rule with a sequence number. Oracle Receivables will try to apply the AutoCash Rules in the order of the Sequence Number. The available AutoCash Rules are as follows:

• Clear the Account: Post QuickCash uses this rule only if your customer's account balance exactly matches the amount of the receipt. If the receipt amount does not exactly match this customer's account balance, Post QuickCash uses the next rule in the set.

• Apply to the Oldest Invoice First: This rule matches receipts to debit and credit items starting with the oldest item first. This rule uses the transaction due date when determining which transaction to apply to first.

• Clear Past Due Invoices: This rule is similar to the 'Clear the Account' rule because it applies the receipt to your customer's debit and credit items only if the total of these items exactly matches the amount of this receipt. However, this rule only applies the receipt to items that are currently past due.

• Clear Past Due Invoices Grouped by Payment Term: This rule is similar to the 'Clear Past Due Invoices' rule, but it first groups past due invoices by their payment term, and then uses the oldest transaction due date within the group as the group due date. When using this rule, Receivables can only apply the receipt if the receipt amount exactly matches the sum of your customer's credit memos and past due invoices.

• Match Payment with Invoice: This rule applies the receipt to a single invoice, debit memo, or chargeback that has a remaining amount due exactly equal to the receipt amount.

Submit Autolockbox process

We submit the Lockbox Process to create receipts and apply them as per the Lockbox data file. The Lockbox is a three step process. Step 1 is importing the data file into Oracle Receivables. Step 2 is validation of the data and Step 3 is the PostQuick Cash process. You can run all these three steps individually or at the same time.

Step 1: Import Process

• New Transmission: If you are importing a new file, check the New Transmission check box. If you are resubmitting an existing transmission, leave this check box unchecked.

• Transmission Name: Provide a transmission name to your Lockbox Submission. If it is not a new transmission, select the Transmission Name from the List of values.

• Submit Import: Check the Submit Import check box to import the lockbox file.

• Data File: Provide the entire path of the location where the Lockbox file is placed.

• Control File: Name of the control file. Do not suffix the file name with .ctl. The control file should be present in the $AR_TOP/bin directory

• Transmission Format: Select the required Transmission Format from the List of values.

Step 2: Validation Process

• Submit Validation: Check this check box if you want to submit the Validation process.

• Lockbox: Specify the lockbox number if Submit Validation is Yes and the lockbox number is not specified in your lockbox file. If your transmission format includes the Lockbox Number, Oracle Receivables skips this field.

• GL Date: Enter the date to post the receipt and batch records in this lockbox transmission to your general ledger in the GL Date field. If you defined your GL Date as 'Constant Date' in the Lockboxes window, you must enter a GL Date; if you specified a GL Date of 'Deposit Date' or 'Import Date', Receivables uses this as the GL date.

• Report Format: Specify All if you want a detail validation report of all records. Specify Rejects Only if you only want details of the records that failed validation

• Complete Batches Only: Check this option if you want Receivables to create receipts only if all the receipt records of the batch are valid. If this option is unchecked, receivables will create receipts for the valid records and the non valid records will be rejected.

• Allow Payment of Unrelated Invoices: Check this option if you want Receivables to apply Payments to unrelated Invoices (Invoices belonging to unrelated Customers)

• Post Partial Amount as unapplied: If this option is enabled, Lockbox process applies the Receipt to valid transactions and the remaining receipt amount that could not be applied because of invalid transaction numbers is considered as unapplied amount. This option is generally set to Yes.

• Reject Entire Receipt: If there are any invalid transaction numbers in the Lockbox file, the entire receipt is rejected. The receipts data remains in the ar_payments_interface_all table. You can update the invalid record using the Maintain Lockbox Transmission Data window.

Step 3: PostQuick Cash Process

• Submit PostQuick Cash: Check the Submit PostQuick Cash check box, if you want the Lockbox process to run PostQuick Cash process. When Receipts are created using AutoLockbox, Receivables stores the receipt information in interim tables. Running PostQuick Cash applies the receipt and updates your customer’s receivable balance.

Receipt API's in Oracle APPS R12

Receipt API in Oracle Receivables

Autolock box provides a functionality to create receipts using interface method. Recent versions of oracle applications, especially 11.5 onwards, Receipt API is getting used as they are flexible to the user’s need, and customization across all kinds of interfaces, loading.
Here are the receipt APIs used in 11i applications:

ar_receipt_api_pub.Create_cash
ar_receipt_api_pub.Apply
ar_receipt_api_pub.Unapply
ar_receipt_api_pub.Reverse
ar_receipt_api_pub.Apply_on_account
ar_receipt_api_pub.Unapply_on_account
ar_receipt_api_pub.Activity_application
ar_receipt_api_pub.Activity_unapplication
ar_receipt_api_pub.Apply_other_account
ar_receipt_api_pub.Unapply_other_account
ar_receipt_api_pub.create_misc
ar_receipt_api_pub.set_profile_for_testing
ar_receipt_api_pub.Apply_Open_Receipt
ar_receipt_api_pub.Unapply_Open_Receipt

I already have added sample script for receipt creation and application in earlier post.
**********************************************************

The World of receipt API's
To integrate with Oracle apps there are 10 API's, such as:
a) Creating a cash receipt
b) Applying it to a debit item
c) Creating a cash receipt and applying it to a debit item in one pass
d) On-account application
e) Unapplying the On-Account application
f) Unapplying the receipt application to a particular transaction
g) Reversing the receipt
h) Create a Miscellaneous receipt
i) Create a cash receipt activity application
j) Unapplies a cash receipt activity application

The 10 Receipt API's:
1 AR_RECEIPT_API_PUB.CREATE_CASH : This is for creating a single cash receipt, as in case of manually created cash receipts.
2 AR_RECEIPT_API_PUB.APPLY : Applies a cash receipt if used in (1) to a particular installment
of a debit item. The application can also be a cross currency application.
3 AR_RECEIPT_API_PUB.CREATE_AND_APPLY : This API's can be used in place of 2 sepearte call as in (1) & (2) above. This will Creates a cash receipt and applies it to a specified installment of a debit item in one pass.
4 AR_RECEIPT_API_PUB.APPLY_ON_ACCOUNT : Does an On Account application for a cash receipt.
5 AR_RECEIPT_API_PUB.UNAPPLY_ON_ACCOUNT : Unapplies the On-account application on the specified receipt.
6 AR_RECEIPT_API_PUB.UNAPPLY : This unapplies the application of a particular installment of a debit item against the specified cash receipt.
7 AR_RECEIPT_API_PUB.REVERSE : This is used to reverses the specified receipt.
8 AR_RECEIPT_API_PUB.CREATE_MISC : This is used to creates a Miscellaneous receipt
9 AR_RECEIPT_API_PUB.ACTIVITY_APPLICATION : This is used to creates an activity application on a cash receipt
10 AR_RECEIPT_API_PUB.ACTIVITY_UNAPPLICATION : This API used to unapplies a particular activity application on a cash receipt.

Data Migration/Conversion of Invoices in Accounts Receivables(AR) in Oracle Apps R12

Whenever we are going in for implementation of Receivables module, we have to consider the necessity of bringing in customer open balances from the old system to Oracle Receivables.

Some of the key questions that needs to be addressed before we take up a conversion activity. This is just a sample list and not an exhaustive one:

1. What are the different types of invoices in existing system Provide invoice samples? (invoices, credit/ debit memos, commitments, chargebacks)
2. Do we need to migrate only open invoices?
3. Do we migrate closed invoices also, if yes, then for what time period?
4. Please explain the invoice numbering mechanism? Is it automatic?
5. What are the interfaces from/to your existing receivables system?
6. Will the old system still be in place for querying and reporting purpose?

One can adopt one of the following three strategies for conversion:

1. Consolidate all the open balances customer-wise and create a single open invoice for each customer in the new Oracle system. The advantage of this system is that it is quite easy and not data intensive and makes good business sense in case of small businesses with very few customers. The major demerit of this approach is that later on one cannot track the individual invoices which the customer had sent and can become an audit issue also. In case of dispute over payment, this invoice will remain open till the dispute is resolved. Also, aging of invoices and dunning history will be lost.

2. Bring in all the open and partially paid invoices, credit/debit memos into the new system. Migrate all the unapplied and partially applied receipts to the new system. The advantage of this process of conversion is that you can track all open invoices individually and apply the correct receipt to correct invoice. Also, the conversion effort will be moderately low compared to case if you migrate all open and closed invoices. The disadvantage of this approach is that you cannot have a track of closed invoices in the new system. Also, it would be tough to handle scenarios where there is a dispute regarding incorrect receipt application, etc. This is the most common approach taken for receivables invoice, credit/debit memo and receipt migration.

3. Migrate all open and closed invoices to the new system. Reapply the migrated receipts to invoices in the new system. This approach makes sense if your receivables data is quite small else the effort involved in migrating all closed invoices and credit memos to the new system does not make much business sense.

The next question that arises is how we should migrate the invoices, credit/debit memos and receipts to the new system. Oracle provides standard interfaces to load the same. We can also use tools like Dataloader or manually key in the data into Oracle.

In this article i will talk of invoice, credit/debit memo conversion only. Prior to invoice migration, customer migration should be over apart from other pre-requisites. Following is the list of pre-requisites that should be completed prior to invoice, credit/debit memo conversion:

•Set-up of Customer Payment Terms should be complete
•Set-up of Currencies should be complete (this is necessary in case you have foreign currency invoices also)
•Set-up of Transaction Types should be complete
•Set-up of Accounting Rules should be complete
•Set-up of Tax rates and Tax codes should be complete
•Set up for sales representative should be complete
•Set up for debtor area should be complete
•Set up for income category should be complete
•Automatic customer invoice numbering should be set to 'No'
•Customer and Customer address should be migrated in the system
•Disable the Invoice interface purge program so that the data successfully imported should not get purged in the interface table.
•Set up for invoice batch source name should be complete

In the next step extract Invoice data from the legacy files and using SQL loader populate the interface tables RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL. Submit the Auto Invoice open interface program. Data from the two interface tables will be uploaded to the following base tables using the Invoice open interface program:

•RA_CUSTOMER_TRX_ALL
•RA_CUSTOMER_TRX_LINES_ALL
•RA_CUST_TRX_LINE_GL_DIST_ALL
•RA_BATCHES_ALL
•RA_CUST_TRX_LINE_SALESREPS_ALL
•AR_RECEIVABLE_APPLICATIONS_ALL
•AR_PAYMENT_SCHEDULES_ALL
•RA_INTERFACE_ERRORS_ALL

Ensure that the Purge Interface check box is not checked when you submit the Autoinvoice program. In the Autoinvoice errors form you can see the error corresponding to failed records. Correct the errors in the interface table and rerun the Autoinvoice program. Submit the Autoinvoice Purge Program separately. Only records that have been successfully processed by Autoinvoice are purged.

Using autoinvoice you can migrate invoices, credit/debit memos and on-account credits into Oracle. However, you have to set grouping rules (Navigation > Setup > Transactions > Autoinvoice > Grouping Rule) to group lines to create one transaction and ordering rules (Navigation > Setup > Transactions > Autoinvoice > Line Ordering Rules) to determine the order of the transaction lines on a particular invoice. 

AR (Receivables) AutoInvoice FAQ in Oracle Apps R12

1. What is Auto Invoice?

A) Autoinvoice is a tool used to import and validate transaction data from other financial systems and create invoices, debit-memos, credit memos, and on account credits in Oracle receivables. Using Custom Feeder programs transaction data is imported into the autoinvoice interface tables.

Autoinvoice interface program then selects data from interface tables and creates transactions in receivables (Populates receivable base tables) . Transactions with invalid information are rejected by receivables and are stored in RA_INTERFACE_ERRORS_ALL interface table.

2. What are the Set up required for Custom Conversion, Autolockbox and Auto Invoice?

A) Autoinvoice program Needs AutoAccounting to be defined prior to its execution.

3. What is AutoAccounting?

A) By defining AutoAccounting we specify how the receivables should determine the general ledger accounts for transactions manually entered or imported using Autoinvoice. Receivables automatically creates default accounts(Accounting Flex field values) for revenue, tax, freight, financial charge, unbilled receivable, and unearned revenue accounts using the AutoAccounting information.

4. What are Autocash rules?

A) Autocash rules are used to determine how to apply the receipts to the customers outstanding debit items. Autocash Rule Sets are used to determine the sequence of Autocash rules that Post Quickcash uses to update the customers account balances.

5. What are Grouping Rules? (Used by Autoinvoice)

A) Grouping rules specify the attributes that must be identical for lines to appear on the same transaction. After the grouping rules are defined autoinvoice uses them to group revenues and credit transactions into invoices debit memos, and credit memos.

6. What are Line Ordering Rules? (Used by Autoinvoice)

A) Line ordering rules are used to order transaction lines when grouping the transactions into invoices, debit memos and credit memos by autoinvoice program. For instance if transactions are being imported from oracle order management , and an invoice line ordering rule for sales_order _line is created then the invoice lists the lines in the same order of lines in sales order.

7. In which table you can see the amount due of a customer?

A) AR_PAYMENT_SCHEDULES_ALL

8. How do you tie Credit Memo to the Invoice?

At table level, In RA_CUSTOMER_TRX_ALL, If you entered a credit memo, the PREVIOUS_CUSTOMER_TRX_ID column stores the customer transaction ID of the invoice that you credited. In the case of on-account credits, which are not related to any invoice when the credits are created, the PREVIOUS_CUSTOMER_TRX_ID column is null.

9. What are the available Key Flex Fields in Oracle Receivables?

A) Sales Tax Location Flex field, It’s used for sales tax calculations.

Territory Flex field is used for capturing address information.

10. What are Transaction types? Types of Transactions in AR?

A) Transaction types are used to define accounting for different transactions such as Debit Memo, Credit Memo, On-Account Credits, Charge Backs, Commitments and invoices.

11. What are the different statuses for Receipts?

A)  Unidentified – Lack of Customer Information

      Unapplied – Lack of Transaction/Invoice specific information (Ex- Invoice Number)

      Applied – When all the required information is provided.

      On-Account, Non-Sufficient Funds, Stop Payment, and Reversed receipt.

12. What is Autolockbox?

A) Auto lockbox is a service that commercial banks offer corporate customers to enable them to out source their account receivable payment processing. Auto lockbox can also be used to transfer receivables from previous accounting systems into current receivables. It eliminates manual data entry by automatically processing receipts that are sent directly to banks. It involves three steps

• Import (Formats data from bank file and populates the Interface Table),
• Validation(Validates the data and then Populates data into Interim Tables),
• Post Quick Cash(Applies Receipts and updates Balances in BaseTables).

13. What is Transmission Format?

A) Transmission Format specifies how data in the lockbox bank file should be organized such that it can be successfully imported into receivables interface tables. Example, Default, Convert, Cross Currency, Zengen are some of the standard formats provided by oracle.

AR (Receivables) Key Table in Oracle APPS R12

1. What is TCA? Tables?

A) Trading Community Architecture. It is a centralized repository of business entities such as Partners, Customers, and Organizations etc. It is a new framework developed in Oracle 11i.

HZ_PARTIES: The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might establish with another party. Although a record in the HZ_PARTIES table represents a unique party, multiple parties can have the same name. The parties can be one of four types:

Organization   for example, Oracle Corporation
Person            for example, Jane Doe
Group              for example, World Wide Web Consortium
Relationship    for example, Jane Doe at Oracle Corporation.

HZ_LOCATIONS: The HZ_LOCATIONS table stores information about a delivery or postal address such as building number, street address, postal code, and directions to a location. This table provides physical location information about parties (organizations and people) and customer accounts.

HZ_PARTY_SITES: The HZ_PARTY_SITES table links a party (see HZ_PARTIES) and a location (see HZ_LOCATIONS) and stores location-specific party information. One party can optionally have one or more party sites. One location can optionally be used by one or more parties. This party site can then be used for multiple customer accounts within the same party.

HZ_CUST_ACCT_SITES_ALL

HZ_CUST_SITE_USES_ALL

HZ_CUST_CONTACT_POINTS

2. What are Base Tables or Interface Tables for Customer Conversions, Autolockbox, Auto Invoice?

A) Customer Conversion:

Interface Tables       : RA_CUSTOMERS_INTERFACE_ALL, RA_CUSTOMER_PROFILES_INT_ALL,

RA_CONTACT_PHONES_INT_ALL,

RA_CUSTOMER_BANKS_INT_ALL,

RA_CUST_PAY_METHOD_INT_ALL

    Base Tables             : RA_CUSTOMERS, RA_ADDRESSES, RA_SITE_USES_ALL,

                                    RA_CUSTOMER_PROFILES_ALL, RA_PHONES etc

B) Auto Invoice:

    Interface Tables       : RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL

RA_INTERFACE_SALESCREDITS_ALL, RA_INTERFACE_ERRORS_ALL

    Base Tables             : RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL,

RA_CUST_TRX_LINE_GL_DIST_ALL, RA_CUST_TRX_LINE_SALESREPS_ALL, RA_CUST_TRX_TYPES_ALL

C) AutoLockBox:

    Interface Tables       : AR_PAYMENTS_INTERFACE_ALL (POPULATED BY IMPORT PROCESS)

    Interim tables                       : AR_INTERIM_CASH_RECEIPTS_ALL (All  Populated by Submit Validation)

           : AR_INTERIM_CASH_RCPT_LINES_ALL,

            AR_INTERIM_POSTING

    Base Tables             : AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL,

                                       AR_PAYMENT_SCHEDULES_ALL ( All Populated by post quick cash)

3. What are the tables in which Invoices/transactions information is stored?

A) RA_CUSTOMER_TRX_ALL, The RA_CUSTOMER_TRX_ALL table stores invoice, debit memo, commitment, bills receivable, and credit memo header information. Each row in this table includes general invoice information such as customer, transaction type, and printing instructions.

RA_CUSTOMER_TRX_LINES_ALL, The RA_CUSTOMER_TRX_LINES_ALL table stores information about invoice, debit memo, credit memo, bills receivable, and commitment lines (LINE, FREIGHT and TAX).

RA_CUST_TRX_LINE_SALESREPS_ALL, The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. If Receivables bases your invoice distributions on sales credits, a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table.

The RA_CUST_TRX_LINE_GL_DIST_ALL table stores the accounting records for revenue, unearned revenue, and unbilled receivables for each invoice or credit memo line. Oracle Receivables creates one row for each accounting distribution, and at least one accounting distribution must exist for each invoice or credit memo line. Each row in this table includes the General Ledger account and the amount of the accounting entry.

The RA_CUST_TRX_LINE_SALESREPS_ALL table stores sales credit assignments for invoice lines. If Receivables bases your invoice distributions on sales credits, a mapping exists between the sales credit assignments in this table with the RA_CUST_TRX_LINE_GL_DIST_ALL table.

4. What are the tables In which Receipt information is stored?

A) AR_PAYMENT_SCHEDULES_ALL, The AR_PAYMENT_SCHEDULES_ALL table stores all transactions except adjustments and miscellaneous cash receipts. Oracle Receivables updates this table when activity occurs against an invoice, debit memo, chargeback, credit memo, on-account credit, or receipt.

Transaction classes determine if a transaction relates to either the RA_CUSTOMER_TRX_ALL table or the AR_CASH_RECEIPTS_ALL table. Using the CUSTOMER_TRX_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table joins to the RA_CUSTOMER_TRX_ALL table for non-payment transaction entries, such as the creation of credit memos, debit memos, invoices, chargebacks, or deposits. Using the CASH_RECEIPT_ID foreign key column, the AR_PAYMENT_SCHEDULES_ALL table joins to the AR_CASH_RECEIPTS_ALL table for invoice-related payment transactions.

AR_CASH_RECEIPTS_ALL, The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, such as miscellaneous receipts, Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table.

AR_RECEIVABLE_APPLICATIONS_ALL, The AR_CASH_RECEIPTS_ALL table stores one record for each receipt that you enter. Oracle Receivables concurrently creates records in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, such as miscellaneous receipts, Receivables creates records in the AR_MISC_CASH_DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ALL table. Cash receipts proceed through the confirmation, remittance, and clearance steps. Each step creates rows in the AR_CASH_RECEIPT_HISTORY table.

5. What are the tables in which Accounts information is stored?

RA_CUST_TRX_LINE_GL_DIST_ALL