Professional Documents
Culture Documents
Cathy Lavender
I will explain the effect on invoices when receipts Quick Cash provides a way to enter
are applied, and what contributes to higher record receipts into an interim table that becomes
count volumes on the Receivable Applications input to your Quick Cash Posting job.
tables. This provides an extra step to the approval
process before the Receipts are entered
You will see examples of applications of receipts
into the main AR_CASH_RECEIPTS
including Unidentified, Unapplied, and On
table
Account transactions.
Using this information will help you predict and Quick Cash Posting reads an interim table
plan appropriate table sizing. of Cash Receipts and processes the data
by creating receipt transactions on
Introduction AR_CASH_RECEIPTS.
Knowing what is involved in the storage of receipts
and their activity against the invoice tables will aid Receipt Application Types
you in implementing and designing your systems.
This will also assist in diagnosing data problems There are four application types:
and will shorten resolution time from Oracle
Worldwide Customer Support because you will be Unidentified – This is a receipt that has
able to provide support detailed information to help been entered, but not identified to a
resolve your issues. particular customer. Status is UNID.
……………………………………………………………………………………………………………………
AR_CASH_RECEIPT_HISTORY
This table contains the steps for the life cycle of a receipt. Each row represents one step. The status field tells
you which step the receipt has reached.
Cash_receipt_history_id Identifier of the cash receipt history
Cash_receipt_id Foreign key to AR-CASH_RECEIPTS
Status One of the following:
APPROVED, CONFIRMED, REMITTED, CLEARED, REVERSED
First_posted_record_flag Y – when this is the first row that has been posted
Gl_date The gldate that is used when debiting the
account_code_combination_id (CASH)
Current_record_flag Indicates which row is the current one for the cash receipt id (Y or N)
Reversal_gl_date This is the gl_date that is used to credit the
account_code_combination_id. It also signifies that this row has been
reversed
Posting_control_id Receivables posting batch identifier. –3 means that it is not posted, a
positive number means that it has been posted
Reversal_posting_control_id -3 means it has not been posted. This should be null if the
reversal_gl_date is null
Acctd_amount This is the amount in the functional currency
Amount Amount in transaction currency. It indicates the amount for this step
of the life cycle of the receipt. Most of the amounts will be similar to
the original amount of the cash receipt but the cleared amount might
be different from the remitted, due to any charges the bank took
AR_DISTRIBUTIONS table is used to store the different steps in the applications’ life cycle
Source_id Cash_receipt_history_id
Code_combination_id This is the account that we create the journal entry for. Example Cash, or Cash
clearing
Acctd_amount_cr Functional_currency
AR_PAYMENT_SCHEDULES
Payment_schedule_id Identifies the payment schedule row
Status OP for open, CL for closed. A closed receipt is one that is fully
applied. A closed invoice/debit memo is one whose
amount_due_remaining has become zero.
Class PMT for payment, INV for invoice, DM for debit memo, CM for
credit memo
Gl_date_closed The accounting date on which the schedule was closed. Default value
for open ones are ‘31-DEC-4712’
Gl_date
Credit Memo applications don’t have rows of status UNAPP. Credit Memos only show a status of APP
Amount_applied Total amount of the application including line, tax, freight and
receivables’ charges.
Gl_date
Applied_customer_trx_line_id Identifies the line of the invoice the application applies to.
Application Samples
The number of records created on AR_RECEIVABLE_APPLICATIONS will differ depending on the
transaction For example:
If we were to change the UNIDENTIFIED to UNAPPLIED, these would be the entries (in total):
Application Amount Payment Applied Cash GL_date Posting
Type Applied Schedule Id Payment Receipt Id Control Id
Schedule Id
UNID 1.98 Payment Null Cash receipt receipt_date -3
schedule id id
of the
receipt
UNID -1.98 Payment Null Cash receipt todays date -3
schedule id id
of the
receipt
UNAPP 1.98 Payment Null Cash receipt todays date -3
schedule id id
of the
receipt
Receipt Applications
When a receipt is initially created, a row is created in this table that has a status of UNAPP, or UNIDENTIFIED
for the amount of the cash receipt. Each subsequent application creates two rows – one with a status of APP for
the amount which is being applied to the invoice and one with status UNAPP or UNID for the negative of the
amount which is being applied. If you reverse an application of cash, a row with status APP with the inverse
amount of the original application (the negative of the original application amount) is created. The
corresponding UNAPP rows are also created which will have a positive amount (the same amount as the
application being reversed).
The sum of the amount_applied column should always equal the amount of the cash receipt.
Receipt Applications
Here is an example of an unidentified receipt,followed up by choosing a customer, and then placing the receipt
on account, and finally applying to an invoice. NOTE: (It is not necessary to first place the receipt as
UNIDENTIFIED, this is just an example)
If customer is unknown, place on Unidentified
Application Amount Payment Applied Cash Receipt GL_date Posting
Type Applied Schedule Id Payment Id control id
Schedule Id
Here is an example of a receipt entered, with the customer chosen, specific application
chosen..
Application Amount Payment Applied Cash Gl_date Posting
Type Applied Schedule Id Payment Receipt Id Control Id
Schedule Id
UNAPP 1.98 Payment Null Cash receipt todays date -3
schedule id id
of the receipt
UNAPP -1.98 Payment Null Cash receipt todays date -3
schedule id id
of the receipt
APP 1.98 Payment Payment Cash receipt todays date -3
schedule id schedule id id
of the receipt of the invoice
Reversals –duplicate all the original entries with the opposite signs.
An example – You will see the original entries, followed by the additional entries created for the reversal. The
reversal entries have the opposite signs of the original entries
Original Entries
Application Amount Payment Applied Cash GlDate Posting
Type Applied Schedule Id Payment Receipt Id Control Id
Schedule Id
UNAPP 1.98 Payment Null Cash receipt todays date -3
schedule id id
of the
receipt
UNAPP -1.98 Payment Null Cash receipt todays date -3
schedule id id
of the
receipt
APP 1.98 Payment Payment Cash receipt todays date -3
schedule id schedule id id
of the of the
receipt invoice
Reversal Entries
Application Amount Payment Applied Cash GlDate Posting
Type Applied Schedule Id Payment Receipt Id Control Id
Schedule Id
UNAPP -1.98 Payment Null Cash receipt Todays date -3
schedule id id
of the
receipt
UNAPP +1.98 Payment Null Cash receipt Todays date -3
schedule id id
of the
receipt
APP -1.98 Payment Payment Cash receipt Todays date -3
schedule id schedule id id
of the of the
receipt invoice
RE-APPLICATIONS remove applications of receipts from one set of invoice to others. This is an example of
one invoice, payment schedule id 306, which has 1.01 applied to it. We will remove this application.
Original
Application Amount Payment Applied Cash Gl_date Posting
Type Applied Schedule Id Payment Receipt Id Control Id
Schedule Id
UNAPP 1.98 100 Null 10178 01-JAN-98 9878
UNAPP -1.98 100 Null 10178 01-JAN-98 9878
APP 1.01 100 306 10178 01-JAN-98 9878
APP .87 100 309 10178 01-JAN-98 9878
APP .10 100 399 10178 01-JAN-98 9878
For example,
on AR_CASH_RECEIPT_HISTORY