ORACLE RECEIVABLES - PROCESSING CUSTOMER

DEDUCTIONS
Release 10
When you receive a payment from a customer that includes one or more deductions that are not tie to
s!e"i#i" in$oi"es and that do not refer to existing credit memos, use the following manual procedure to
create the appropriate items in Oracle Receivables.
Prior to applying or completing the application of the payment:
1 !etermine the total amount of "unauthori#ed$ deductions that the customer too%, the related reference
numbers and the amount and reference number for each deduction that made up this total.
& 'reate O() credit memo using the Enter Creit Me%os or the &'i"( Transa"tion Entr) screen for
the total amount the customer deducted:
*Navigate Memo +tandard ,)nter 'redit -emos or
*Navigate Invoice &uic% ,.uic% /ransaction )ntry
-emo (umber 0 '-,and the chec% number
/ype 0 'ustomer !eduction 'redit -emo ,'lass 0 'redit -emo
1mount 0 total of the deductions ,negative
Reference 0 '2,and the chec% number
3ine /ype4!escription 0 'ustomer !eduction
3ine 1mount 0 total of the deductions ,negative
5 'reate one !ebit -emo for )1'6 deduction that the customer too% using the Enter In$oi"es screen
or the &'i"( Transa"tion Entr) screen:
*Navigate Invoice Standard ,)nter 7nvoices or
*Navigate Invoice &uic% ,.uic% /ransaction )ntry
(umber 0 !- ,and the customer$s reference number
/ype 0 'ustomer !eduction !ebit -emo ,'lass 0 !ebit -emo
1mount 0 the amount of the deduction ,positive
Reference 0 '2,and the chec% number
3ine /ype4!escription 0 'ustomer !eduction ,note that this uses the same 83 account that you used for
the credit memo 9 so this is a wash entry
Reason 0 use .uic%Pic% to select the appropriate reason
3ine 1mount 0 the amount of the deduction ,positive
: 1pply the credit you created ,along with the payment received to the invoices as indicated by the
customer on the remittance advice. ;se the )nter Receipts screen:
*Navigate Receipt Manual Standard
)nter or <uery the payment
-ove to the Receipt 1pplications or -ass Receipt 1pplications #one
+elect the credit memo you created in step &
,this will increase the amount you have available in your unapplied amount
apply the receipt and the credit as indicated on the remittance advice

What you have done is:
a created items with a #ero net effect on the customer balance
b created offsetting 83 entries ,provided that you use the same 83 accounts for the debits and the
credits
c created separate debit memos for each deduction so you can individually research and resolve them
d created documents ,debit memos that you can print and send to the customer to notify them that the
deduction,s were not allowed
e paid the open invoices as indicated on the remittance advice
7t is often easier to perform this process prior to starting your cash application. /hat way the credit will be
available for use when applying the payments according to the remittance advice.

RELATED SETUPS*
/ransaction /ypes ,*Navigate Setup Invoice Type+
for: ='ustomer !eduction 9 'redit -emo= and
='ustomer !eduction 9 !ebit -emo= 9 use the appropriate Receivables 1ccounting >lexfield ,note that
this generally will be the same account for the debit memo and for the credit memo
+tandard 3ines ,*Navigate Setup Memo Line
for: ='ustomer !eduction= 9 use the appropriate 'learing 1ccounting >lexfield ,note that this is generally
the same account for the debit memo and the credit memo. 7t is helpful to define a special account which
will only be used for this type of activity. 7f you find an open balance for the special account 99 you %now
that you have a problem
Reasons ,*Navigate Setup +ystem &uic%'odes Receivables
/ype 0 'redit -emo Reason and 7nvoicing Reason
verify that you have defined appropriate reasons for the customer deductions
?e sure to use a ?atch +ource that allows manually numbering of transactions, if you do not already have
such a ?atch +ource, you will need to create one.
(O/): if the customer deduction relates to a single, specific invoice 9 you can utili#e the 'hargebac%
feature in the Enter Re"ei!ts screen to more easily accomplish this.
@ou can O(3@ use the &'i"( Transa"tion Entr) screen 7> you do not need to override any of the default
segments for the Receivables or clearing 1ccounting >lexfields, as defaulted using your 1uto1ccounting
rules.
A""o'ntin, -or Ora"le Re"ei$a.les
'athy 'a%ebread, 'onsultant
1lmost everything you do in Oracle Receivables has an accounting impact, but you may be unsure of
what that impact is, where to find the information and where the values came from. 3earn how
1uto1ccounting wor%s, the accounting transactions associated with the standard activities, and which
setups determine the values. When 7 am illustrating how the accounting wor%s, 7 have noted the source of
the value in the parenthesis , .

-lo/ o# A""o'ntin, In#or%ation
>irst, it is important to understand where the values come from, how you pass the values to Oracle
8eneral 3edger and how to verify the values.
7f you are using Oracle Order )ntry ,without customi#ations, no accounting information is available until
you run 1uto7nvoice. @ou pass the transactions to Oracle Receivables using the Receivables 7nterface.
@ou then run 1uto7nvoice which creates the actual transactions and uses 1uto1ccounting to derive the
segment values for the 83 1ccounts. 7f you are using Oracle ProAects the account segment values are
derived by a ProAects$ process also called 1uto1ccounting and passed as values to Oracle Receivables
via the +treamline process, also using 1uto7nvoice.
Whether you are manually entering your receipts or processing them through 1uto3oc%box, the
accounting information is automatically determined by Oracle Receivables when you create and apply the
receipts ,not when it is still a =.uic%'ash= batch. /he values used are based on the setup values for the
ban% where the receipts were deposited and the invoices they are paying.

General Le,er Inter#a"e
@ou pass accounting information from Oracle Receivables to Oracle 8eneral 3edger using the 8eneral
3edger 7nterface. 7f you have properly set up Oracle Receivables, you should never have to create
manual Aournal entries in your 8eneral 3edger and the two systems should always be in sync.
When you invo%e the 8eneral 3edger 7nterface process, you initiate multiple programs that:
>inds all of the records for the period you specified that have not yet been passed to the 8eneral
3edgerB
!etermines if the debits e<ual the creditsB
Passes the data to 83 for editingB and
-ar%s the records as having been passed ,so they will not pass twice.
7f you have specified that you want the Cournal 7mport to also run, this process verifies that the
individual segments and combinations of segments are valid. Only when the Cournal 7mport
completes successfully are the Cournals available for posting.
Ti!* 1lways run the 8eneral 3edger 7nterface using the starting date of the period through the last day of
the period. /his is applicable no matter when you are running the process or if you %now you will never
have activity for that date, since sometimes the system uses dates other than the dates you expect.
!epending on which patches you have applied, you may or may not see the Un!oste Ite%s Re!ort. 7f
this report does run, always chec% each page to ensure that you have no items that could not be passed
to the 8eneral 3edger. 7f anything besides headings appears, wor% with your 7/ department to resolve
,since this is usually caused by a bug.
Derify that the amounts in the General Le,er Inter#a"e Re!ort are reasonable and that the debits e<ual
the credits.
Derify that the Cournal 7mport has a status of =+;'')++.= 7f not, you had a problem that will need to be
resolved or none of the items in the batch will be available for posting. 8enerally you have a problem if an
account was valid when the activity was created, as you %now, you cannot save with invalid values but,
someone has since disabled either a segment or the combination. 1n example of this is your 1ccounts
Receivable account that may have been valid when the invoice was originally created but it is not longer
valid, and a receipt was Aust applied against it. When you apply a receipt to an invoice it always causes an
offsetting entry against the original 1ccounts Receivable account.
+hould this occur, 7 suggest that you:
1. Re9enable the segment or combinationB
&. Re9run the Cournal 7mport ,in 83 99 be sure to include the applicable idB
5. 'reate a manual Aournal entry ,also in 83 to move the activity from the bad account to
the proper account ,this is my one exception to never creating manual Aournal entriesB
and
:. Re9disable the segment or combination.
?y ma%ing the corrections in this way you are able to %eep your 83 in sync with your 1R activity and you
have an audit trial of what you did to ma%e the correction. @ou have the option to correct in the 7mport
'orrections form ,in 83, but you lose the audit trail of what you did and why. 7 also recommend noting
what you did and why and storing the notes in a handy binder so you will be prepared when the auditors
as% why you did what you did.

0o'rnal Entries Re!orts
/he Cournal )ntries reports are the best way to verify the actual accounting for Oracle Receivables$
activities and the only way to view the accounting for the foreign currency gains and losses. /here are
actually four reports that give you varying levels of details regarding the Aournal entries you will be
creating or have already created. /hese reports may be run at anytime before or after you run the
8eneral 3edger 7nterface. @our options are: !etail by 1ccount ,very large, +ummary by 1ccount, !etail
by 'ategory ,also large and +ummary by 'ategory.
Ti!* 7 always recommend that you at least run the +ummary by 'ategory and review to insure that there
are no invalid or illogical accounts, prior to running the 8eneral 3edger 7nterface. 7f you find funny
accounts, you can correct or create offsetting entries prior to posting. Run the !etail by 'ategory ,Aust for
that category and account to see which specific activities used the funny account. 'orrect the activity if
possible. 7f not possible ,i.e., adAustment, create an offsetting entry using the proper account.
Ti!* 7f you run this report for ;nposted 7tems only, you must leave the Posted !ate range blan% or nothing
will appear on the report.

Perio Close Pro"e'res
Ti!* 7 suggest that you never have more than one 1R period open at one time. /here have been problems
with entries appearing partially in one period and partially in another. 1lso, you may accidentally enter
activities in a period other than the period you intended.
'reate a chec%list to insure that you always %now where you are and what you have to do next, so you
will not forget anything.
?alance your 1R activity to the 1ging:

Old 1ging ?alance ,1ged /rial ?alance 9 E ?uc%ets by 1ccount
F
F
(ew 7nvoices
!ebit -emos
,/ransaction Register
,/ransaction Register
F 'hargebac%s ,/ransaction Register
9 'redit -emos ,/ransaction Register
9 Receipts 1pplied ,1pplied Receipts Register
F49 ;napplied 1ctivity ,;napplied Receipts Register
F49 1dAustments ,1dAustment Register
9 7tems (ot 1ged ,7nvoice )xceptions Report

99999999999999999999999


(ew 1ging ?alance ,1ged /rial ?alance 9 E ?uc%ets by 1ccount
1lso balance your 1R activity to your 83 activity using the Cournal )ntries Report 9 +ummary by 'ategory
and the 1ccount 1nalysis report ,in 83. (ote any manual Aournal entries that used =your= accounts.

A""o'ntin, Details
/he 83 1ccounts may or may not appear on the form ,depending on what you are doing but almost
every activity you perform has an accounting impact. 7n order to understand this impact it is necessary to
%now:
1 what accounts are impacted by each transactionB
& what are the related set upsB
5 what you may change and4or override and what is out of your control.

A'toA""o'ntin,
1uto1ccounting a very powerful setup feature that tells Oracle Receivables how to determine the
individual segment values for your /ransactions ,invoices, debit memos, credit memos, chargebac%s and
commitments using the rules that you specify. @ou may use this feature when creating /ransactions
manually or through 1uto7nvoice. /he types of accounts impacted by 1uto1ccounting include:
,1ccounts Receivable
Revenue
/ax
>reight
;nearned Revenue ,for deferred revenue recognition
;nbilled Receivable ,for deferred receivables recognition
1uto7nvoice 'learing ,for problems with extended amount
Possible sources of this information are the values you set up for the following:
/ransaction /ypes
+alesreps
+tandard 3ines ,7tems or -emo 3ines
/axes
1nd4or hard coded values.
@ou may get one segment value for one type of account from a different place than for another. +ee
1ppendix 1 for an example of a typical 1uto1ccounting setup.
@ou can use a similar wor%sheet to test the setup of your 1uto1ccounting rules. 3ist your 1ccounting
>lexfield segments in the left column. >or each type of account select the source of each segment ,based
on the list of available sources and fill in that box. /est your theory by listing what all the setup accounts
would be for a Transa"tion T)!e1 Salesre!1 Ite%1 Ta2 and Me%o Line. /hen use a white9board and fill
in each segment, for each type of account, with the values from each of the related sources. Derify that
the combinations are actually valid, if not, redesign how they will be set up or redefine your
1uto1ccounting rules. Once you are satisfied with the results, enter your 1uto1ccounting rules into your
test system and start creating manual invoices. Derify that you have not created invalid account values as
the defaults.
Ti!* 7 prefer to assign all segments to sources versus using hard coded values. /his seems more flexible
for future changes.

In$oi"es
When you create an invoice either through 1uto7nvoice or manually, you ta%e advantage of
1uto1ccounting to provide the default 1ccounting >lexfield values. >or manual invoices you have the
option to override the default values.
>or a standard 7nvoice:
DR 1R ,1uto1ccounting 9 may
override
CR Revenue ,1uto1ccounting 9
may override

/ax ,1uto1ccounting 9 may
override

>reight ,1uto1ccounting 9
may override

@ou may also create invoices with special accounting and invoicing rules that allow you to defer revenue
recognition for the percentage and number of periods that you specify. /he following is an example of an
invoice created with deferred revenue recognition for G1&,HHH split evenly over 1& periods:
>or invoices with deferred revenue:
When first created:
DR 1R ,1uto1ccounting 9 may
override 1&HHH
CR ;nearned Revenue
,1uto1ccounting 1&HHH

;nearned Revenue
,1uto1ccounting 1HHH

Revenue ,1uto1ccounting 9
may override 1HHH
>or each of the next 11 periods:
DR ;nearned Revenue
,1uto1ccounting 1HHH
CR Revenue ,1uto1ccounting
1HHH

7f you are using deferred revenue recognition, you need to run the revenue recognition process for each
period ,R'n Re$en'e Re"o,nition+ and runs automatically as part of the 8eneral 3edger 7nterface.
Ti!* /o reduce the time it ta%es to close the period, run Revenue Recognition prior to the time when you
are actually closing ,e.g., the night before the close. /his will process the maAority of the updates prior to
the actual close.
Recurring 7nvoices ,/ransaction 'opy are treated li%e regular invoices, except they have different 83
dates. Once you have created an invoice copy, it really is Aust another invoice with different dates.

De.it Me%os
!ebit memos wor% Aust li%e standard invoices ,you even create them on the same forms 99 ta%ing
advantage of A'toA""o'ntin, but with overridable segments. 7f you defined -emo 3ines for use with
your debit memos, they will provide the default accounting segments if you have set up 1uto1ccounting to
use +tandard 3ines values for your Revenue accounts.

Creit Me%os An On A""o'nt Creits
/here are two types of credit memos: credit memos that you create to offset an individual invoice are
called ='redit -emos.= 'redit memos that impact a customer$s account but are not initially tied to a
specific invoice are called =On91ccount 'redits.= On9account credits may be tied to invoice,s using the
Re"ei!ts A!!li"ations /ino/1 at any time. /he accounting for 'redit -emos usually offsets the
applicable accounts from the original invoice ,if you set your +ystem Profile option 1R: ;se 7nvoice
1ccount >or 'redit -emo to =@es=. 'redit memos and on9account credits that are created using
1uto7nvoice ta%e advantage of A'toA""o'ntin, and4or hard coded values. @ou may override the default
values if you are entering manually.
'redit -emo tied to an invoice:
DR Revenue ,from the related
invoice 9 may override
CR 1R ,from the related
invoice 9 may override

/ax ,from the related
invoice 9 may override


>reight ,from the related
invoice 9 may override


On9account credits ta%e advantage of A'toA""o'ntin, and +tandard 3ines ,Me%o Lines depending on
how you set up your 1uto1ccounting rules for the default credit and debit 83 1ccounts. @ou may override
the default values at entry time if you are entering manually.
DR Revenue ,-emo 3ine 9
may override
CR 1R ,1uto1ccounting 9 may
override

When you apply an on9account credit to invoice,s, you debit the credit account you used when you
created the on9account credit. /he 1ccounts Receivable account for the invoice being offset is credited.
@ou may not override these values.
DR 1R ,from the On91ccount
'redit
CR 1R ,from the invoice
Cash Re"ei!ts 3E2"l'in, Mis"ellaneo's Re"ei!ts+
/he accounting for receipts, except for -iscellaneous Receipts, is totally controlled behind the scenes by
Oracle Receivables. /he 83 1ccounts are determined by the values you defined in Re"ei!t Class for the
batch.
(O/): @ou have one 'ash, ;napplied, On91ccount, ;nidentified, )arned !iscount and ;nearned
!iscount account for each ban% and class, which does not allow you to split the ;napplied, etc. accounts
for the applicable cost center or division.
@ou may set up different values for each ban% and class that you use ,especially important for the cash
account. Or, you may share the 83 1ccounts for multiple ban% accounts ,i.e., the unapplied and discount
accounts. /he %ey accounts are:
@our cash account ,the default debit account for that ban% accountB
Ti!* Often 1P and 1R share the same ban% account but it is helpful to use a different but se<uential 83
account for each. /his eases the reconciliation but you can roll together for >+8 reporting.
@our unapplied payments account ,the default used until you match the payment to an invoiceB
@our on9account account ,used to account for pre9payments until you apply them to invoice,sB
@our unidentified account ,used for receipts where you do not %now which customer sent the
receiptB
Ti!* Often companies use the same 83 1ccount for unapplied, on9account and unidentified. /his
is fine as long as: the account is not used for anything else and it is not an 1ccounts Receivable
or cash account.
@our earned and unearned discount accounts ,used when a client pays invoices in accordance
with the early payment terms. /hese are also often the same. )arned discounts are for payments
made within the discount terms, unearned discounts are paid after the discount term but are
allowed anyway.
When you match a receipt to an invoice, the cash account ,debit defaults from the Receipt 'lass for the
Receipt batch. /he 1ccounts Receivable account ,credit defaults from the invoice that is being paid.
(O/): )ven if you instantly match a payment to an open invoice, Oracle still creates credits and debits to
the unapplied account.
Payment applied to an invoice without discount terms:
DR 'ash ,Receipt 'lass CR ;napplied ,Receipt 'lass

;napplied ,Receipt 'lass

1R ,from the invoice
Payment applied to an invoice with discount terms:
DR 'ash ,Receipt 'lass CR ;napplied ,Receipt 'lass

;napplied ,Receipt 'lass

1R ,from the invoice

!iscount ,Receipt 'lass

When you leave a receipt as unapplied:
DR 'ash ,Receipt 'lass CR ;napplied ,Receipt 'lass
When you identify a receipt is as a pre9payment or deposit:
DR 'ash ,Receipt 'lass CR On91ccount ,Receipt
'lass
>or unidentified receipts:
DR 'ash ,Receipt 'lass CR ;nidentified ,Receipt
'lass
When you apply unapplied, on9account or unidentified receipts, the accounting is determined by the
original status. /he accounts used are based on the accounts you currently are using for the Receipt
'lass. /he 1ccounts Receivable account still comes from the invoice.
DR ;napplied ,Receipt 'lass
On91ccount ,Receipt
'lass
or ;nidentified ,Receipt
'lass
CR 1R ,from the invoice
When you unapply a receipt, the accounting is Aust the opposite of the application accounting. @ou debit
the 1R account for the original invoice and credit the unapplied account based on the current unapplied
account for the Receipt 'lass:
DR 1R ,from the invoice CR ;napplied ,Receipt 'lass

When you reverse a receipt, you have two possible options: re9open the invoices you previously paid or
create a debit memo for the amount of the reversed payment. 7f you re9open the invoices, the system
offsets the accounts used when you originally applied the payment ,from the invoice and the cash
account. (ote that this process also impacts the unapplied account.
DR ;napplied ,Receipt 'lass CR 'ash ,Receipt 'lass

1R ,from the invoice

;napplied ,Receipt 'lass
7f you create a debit memo, you credit the original cash account but debit the 1ccounts Receivable
1ccount for the !ebit -emo type you selected. @ou may override the 1ccounts Receivable account when
you enter the payment reversal.
DR 1R ,/ransaction /ype 9
may override
CR 'ash ,Receipt 'lass
Char,e.a"(s
@ou create 'hargebac%s when you are applying cash to close the original invoice and create a new
invoice for the amount that the customer short paid. ?y definition, there is a one to one relationship
between a 'hargebac% and the original invoice. @ou need to set up values for 'hargebac%s in 5 places:
Re"ei$a.les A"ti$it) where you specify the =wash= account used when creating a 'hargebac%.
Transa"tion T)!es where you specify the default 1R account. 1 Me%o Line 34Char,e.a"( Line4+ is
seeded by Oracle but it is Aust used for the line description when you print the 'hargebac% and has no
accounting impact. /he 1ccounts Receivable account for the new invoice is based on the 1ccounts
Receivable account for the 'hargebac% but you may override it at entry item. Oracle credits the 1ccounts
Receivable account for the original invoice ,note that these two accounts may be different.
7n the 'ategory of 1dAustment:
DR 'hargebac% 1dAustment
,Receivables 1ctivity
CR

7n the 'ategory of 1dAustment ,1R:
DR

CR 1R ,from the original invoice
7n the 'ategory of 'hargebac%:
DR

CR 'hargebac% 1dAustment ,Receivables
1ctivity
7n the 'ategory of 'hargebac% ,1R:
DR 1R ,from the chargebac% 9
you may override
CR


7n the 'ategory of /rade Receipts:
DR 'ash ,Receipt 'lass CR

7n the 'ategory of /rade Receipts ,1R:
DR ;napplied ,Receipt 'lass CR 1R ,from the original invoice

;napplied ,Receipt 'lass

Mis"ellaneo's Re"ei!ts
-iscellaneous Receipts are any receipts that are not for open receivables. )xamples include 'obra
payments, /9shirt sales, utility refunds, and returns on investments. !ue to the nature of this activity, you
may need to credit any account within the chart of accounts. /he !istribution Window in the Receipts
form allows you to do Aust that. @ou may run into an 1ccount +ecurity Rule set up to restrict usage of
accounts by application. 7f you find that you may not use an account that you need, wor% with your
+ystem 1dministrator to change the 1ccount +ecurity Rules.
@ou may pre9define the credit accounts that you usually use to speed entry ,using Re"ei$a.les A"ti$it)
but you also have the flexibility to override the values at entry time. @ou also have the ability to split a
single receipt into multiple accounts ,you may also pre9define those accounts using !istribution +ets.
7f you will always be splitting the accounts, you should define a Distri.'tion Set. 1 distribution set is a
name and one or more 83 1ccounts and percentages that you define. @ou must create a Receivable
1ctivity that refers to the !istribution +et.
When you enter -iscellaneous Receipts, you refer to the Receivables 1ctivities that you defined above.
6owever, you may override the default 83 1ccounts, the individual segments, the percentages and4or the
amounts. /he cash account used defaults based on the Receipt 'lass for the ban% you specified on the
?atch +creen, and you may not override or view the value.
DR 'ash ,Receipt 'lass CR -iscellaneous 1ccount,s
,Receivables 1ctivity or
!istribution +et 9 may
override

Re"ei$a.le A5'st%ents
Receivable 1dAustments are generally write9offs, or changes to the invoice balance due for over9 or under9
payment by the customer, or the addition of finance charges. Pre9define commonly used adAustment types
using the Re"ei$a.les A"ti$it) form. /his speeds entry, but you may override the default values as you
enter the adAustments. (O/): 1lways define a 83 1ccount and not a !istribution +et when you define
Receivable 1ctivities for adAustments.
Ti!* When entering an adAustment, never use an 1ccounts Receivable 1ccount. Oracle Receivables
already automatically offsets the 1R account for the invoice being adAusted and you will create a wash
entry.
1 Receivables 1dAustment is always applied to a specific invoice so it impacts the 1ccounts Receivable
account for that invoice. Receivables adAustments may either be positive ,debit 1R, and increase the
invoice balance or negative ,credit 1R and decrease the invoice balance. )xamples include:


1dd a finance charge ,note that this is a positive adAustment that increases the balance due:
DR 1R ,from the invoice CR >inance 'harges
,Receivables 1ctivity 9
may override
Reduce the freight amount:
DR >reight ,Receivables
1ctivity 9 may override
CR 1R ,from the invoice
Write9off the invoice balance:
DR 'ost of !oing ?usiness
,Receivables 1ctivity 9
may override
CR 1R ,from the invoice
@ou may use 1uto1dAustments to perform mass cleanup of open invoices and on9account credits. /he
1ccounts Receivable account credited is the 1ccounts Receivable account for the transaction. /he
account debited is based on the Receivables 1ctivity you select when you submit the 1uto1dAustment
process. (ote that 133 adAustments made during this process will use that exact same =write off= account
even if the original invoices are for different companies, or cost centers. /his may be a consideration in
determining if you can actually utili#e 1uto1dAustments, or if you want to run multiple passes of
1uto1dAustment by /ransaction /ype and 1dAustment 1ctivity.

-orei,n C'rren") Gains an Losses
/ransactions that are not in your base currency may cause gains or losses to occur due to fluctuations in
the exchange rates. /his is automatically accounted for by Oracle Receivables. When you enter the
/ransaction, the applicable exchange rate for the date you enter it is stored with the transaction. When
you enter the related receipt the applicable exchange rate for the date you enter the receipt is stored with
the receipt. /he gain or loss is determined based on the difference in the value of the money ,in your
base currency between when the invoice was created and when the receipt was created. /he gain and
loss accounts are derived based on the values in your S)ste% O!tions and how you set up >lexbuilder.
(ote that most companies use the default setup for -le2.'iler. (ote that there is no gain or loss if you
apply an adAustment since both the adAustment and the invoice use the same rate. @ou can predict 8ains
and 3osses using the Pro5e"te Gains6Losses Re!ort. @ou can only view the gain4loss accounting
activity by running the 0o'rnal Entries Re!ort.
8ain 9 now worth more:
DR 'ash ,Receipt 'lass at the
receipt rate
CR 1R ,from the invoice at the
invoice rate

;napplied ,Receipt 'lass
at the receipt rate

;napplied ,Receipt 'lass
at the receipt rate

8ain ,+ystem Options 9
difference between the
invoice and receipt values

3oss 9 now worth less:
DR 'ash ,Receipt 'lass at the
receipt rate
CR 1R ,from the invoice at the
invoice rate

;napplied ,Receipt 'lass
at the receipt rate

;napplied ,Receipt 'lass
at the receipt rate

3oss ,+ystem Options 9
difference between the
invoice and receipt values


Con"l'sion
?y %nowing the sources and the accounting impact of each activity and the ways to trac% and reconcile
that activity, you have greater control over the outcome of your data and greater confidence that the
processes wor% as you expect.

A.o't the A'thor
'athy 'a%ebread 99 'onsultant
7 am an independent consultant speciali#ing in implementing and upgrading Oracle >inancials, primarily
Oracle Receivables. 7 have over twenty years experience in designing, developing and implementing
financial software and 7 was one of the original designers of Oracle Receivables and Revenue
1ccounting. 7 have been an independent consultant since 1IIH.

1PP)(!7J1:

ORACLE RECEIVABLES
AUTOACCOUNTING 7OR8S9EET -- E:AMPLE
Release 1H
ACCOUNTING
-LE:-IELD
SEGMENTS
AUTO
INVOICE
CLEARING
-REIG9T RECEIVABLE REVENUE TA: UNBILLED
RECEIVABLE
UNEARNED
REVENUE
,Possible !efault
+ources
9+alesrepsK
9 +tandard
3ines
9/ransaction
/ypes
9 +alesreps
9 +tandard
3ines
9/ransaction
/ypes
9+alesreps
9/ransaction
/ypes
9+alesreps
9+tandard
3ines
9/ransaction
/ypes
9 +alesrepsK
9 +tandard
3inesK
9 /axes
9/ransaction
/ypes
9+alesrepsK
9+tandard 3ines
9/ransaction
/ypes
9+alesrepsK
9+tandard
3ines
9/ransaction
/ypes
'ompany /ype /ype /ype /ype /ax /ype /ype
?usiness ;nit /ype /ype +alesrep +alesrep /ax /ype /ype
'ost 'enter
,division
/ype /ype +alesrep +alesrep /ax /ype /ype
1ccount /ype /ype /ype 3ine /ax /ype /ype
+ubaccount /ype /ype /ype 3ine /ax /ype /ype
1ctivity /ype /ype /ype 3ine /ax /ype /ype
3ocation /ype /ype /ype 3ine /ax /ype /ype

+pecial use 1uto7nvoice 9
where
revenue not 0
<ty K price

9 ?ill in 1rrears
9 8uarantees
9 ?ill in
1dvance
9 8uarantees
9 !eposits
POSSIBLE SOURCES O- IN-ORMATION INCLUDE*
SALESREPS
TRANSACTION T;PES
STANDARD INVOICE LINES
TA: RECORDS
< = not reall) #ille in on those s"reen
Loading
Home
Articles
Video Tutorials
Finance
Accounting
Account Payables
API's
Account Receivables
Cash Management
racle Payments
!eneral Ledger
"#$ L%&!%R ACC#'TI'!
"CM
Inventory
AL
Purchasing
rder Management
PM
i"u((liers
Technical
PL")L
")L
API's
racle Alerts
*or+,o-
#se.ul
Monday/ A(r i l 01/ 0232
Accounting entries in R12 Account
Receivables
Invoices4
*hen you enter a regular invoice through the Transactions -indo-/ Receivables
creates the .ollo-ing 5ournal entry4
&%$IT Receivables
CR%&IT Revenue
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
I. you enter an invoice -ith a $ill in Arrears invoicing rule -ith a three month 96ed
duration accounting rule/ Receivables creates the .ollo-ing 5ournal entries4
In the 9rst (eriod o. the rule4
&%$IT #nbilled Receivables
CR%&IT Revenue
In the second (eriod o. the rule4
&%$IT #nbilled Receivables
CR%&IT Revenue
In the third and 9nal (eriod o. the rule4
&%$IT #nbilled Receivables
CR%&IT Revenue
&%$IT Receivables
CR%&IT #nbilled Receivables
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
I. you enter an invoice -ith a $ill in Advance invoicing rule/ Receivables creates the
.ollo-ing 5ournal entries4
In the 9rst (eriod o. the rule4
&%$IT Receivables
CR%&IT #nearned Revenue
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
&%$IT #nearned Revenue
CR%&IT Revenue
In all (eriods o. the rule .or the (ortion that is recogni:ed;
&%$IT #nearned Revenue
CR%&IT Revenue
Credit Memos4
*hen you credit an invoice/ debit memo/ or chargebac+ through the Credit
Transactions -indo-/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Revenue
&%$IT Ta6 7i. you credit ta68
&%$IT Freight 7i. you credit .reight8
CR%&IT Receivables 7Credit Memo8
&%$IT Receivables 7Credit Memo8
CR%&IT Receivables 7Invoice8
*hen you credit a commitment/ Receivables creates the .ollo-ing 5ournal entries4
&%$IT Revenue
CR%&IT Receivables
*hen you enter a credit memo against an installment/ Receivables lets you choose
bet-een the .ollo-ing methods4 LIF/ FIF/ and Prorate; *hen you enter a credit
memo against an invoice -ith invoicing and accounting rules/ Receivables lets you
choose bet-een the .ollo-ing methods4 LIF/ Prorate/ and #nit;
I. the (ro9le o(tion AR4 #se Invoice Accounting .or Credit Memos is set to <es/
Receivables credits the accounts o. the original transaction; I. this (ro9le o(tion is
set to 'o/ Receivables uses AutoAccounting to determine the Freight/ Receivables/
Revenue/ and Ta6 accounts; Receivables uses the account in.ormation .or on=
account credits that you s(eci9ed in your AutoAccounting structure to create your
5ournal entries;
Receivables lets you u(date accounting in.ormation .or your credit memo a.ter it
has (osted to your general ledger; Receivables +ee(s the original accounting
in.ormation as an audit trail -hile it creates an o>setting entry and the ne- entry;
Commitments4
*hen you enter a de(osit/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Receivables 7&e(osit8
CR%&IT >set Account
#se the AR4 &e(osit >set Account "ource (ro9le o(tion to determine ho-
Receivables derives the >set Account to credit .or this de(osit;
*hen you enter an invoice against this de(osit/ Receivables creates the .ollo-ing
5ournal entries4
&%$IT Receivables 7Invoice8
CR%&IT Revenue
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
&%$IT >set Account 7such as #nearned Revenue8
CR%&IT Receivables 7Invoice8
*hen you a((ly an invoice to a de(osit/ Receivables creates a receivable
ad5ustment against the invoice; Receivables uses the account in.ormation that you
s(eci9ed in your AutoAccounting structure to create these entries;
*hen cash is received against this de(osit/ Receivables creates the .ollo-ing 5ournal
entry4
&%$IT Cash
CR%&IT Receivables 7&e(osit8
*hen you enter a guarantee/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Receivables
CR%&IT Revenue
Receivables uses the Receivable Account and Revenue Account 9elds on this
guarantee's transaction ty(e to obtain the accounting ,e69elds .or the #nbilled
Receivables and #nearned Revenue accounts/ res(ectively;
*hen you enter an invoice against this guarantee/ Receivables creates the .ollo-ing
5ournal entry4
&%$IT Receivables 7Invoice8
CR%&IT Revenue
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
&%$IT Revenue
CR%&IT Receivables
*hen you a((ly an invoice to a guarantee/ Receivables creates a receivable
ad5ustment against the guarantee; Receivables uses the account in.ormation you
s(eci9ed in your AutoAccounting structure to create these entries;
*hen cash is received against this guarantee/ Receivables creates the .ollo-ing
5ournal entry4
&%$IT Cash
CR%&IT Receivables 7Invoice8
Recei(ts4
*hen you enter a recei(t/ Receivables creates the .ollo-ing 5ournal entries4
&%$IT Cash
CR%&IT Receivables
*hen you .ully a((ly a recei(t to an invoice/ Receivables creates the .ollo-ing
5ournal entry4
&%$IT Cash
&%$IT #na((lied Cash
CR%&IT #na((lied Cash
CR%&IT Receivables
'ote4 These e6am(les assume that the recei(t has a Remittance Method o. 'o
Remittance and a Clearance Method o. &irectly;
*hen you enter an unidenti9ed recei(t/ Receivables creates the .ollo-ing 5ournal
entry4
&%$IT Cash
CR%&IT #nidenti9ed
*hen you enter an on=account recei(t/ Receivables creates the .ollo-ing 5ournal
entry4
&%$IT Cash
CR%&IT #na((lied
&%$IT #na((lied
CR%&IT n=Account
*hen your recei(t includes a discount/ Receivables creates the .ollo-ing 5ournal
entry4
&%$IT Receivables
CR%&IT Revenue
&%$IT Cash
CR%&IT Receivables
&%$IT %arned?#nearned &iscount
CR%&IT Receivables
Receivables uses the de.ault Cash/ #na((lied/ #nidenti9ed/ n=Account/ #nearned/
and %arned accounts that you s(eci9ed in the Remittance $an+s -indo- .or this
recei(t class;
*hen you enter a recei(t and combine it -ith an on=account credit 7-hich increases
the balance o. the recei(t8/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Cash
CR%&IT #na((lied Cash
To close the receivable on the credit memo and increase the una((lied cash
balance/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Receivables
CR%&IT #na((lied Cash
*hen you enter a recei(t and combine it -ith a negative ad5ustment/ Receivables
creates the .ollo-ing 5ournal entries4
&%$IT Cash
CR%&IT Receivables 7Invoice8
&%$IT *rite=>
CR%&IT Receivables 7Invoice8
<ou set u( a *rite=> account -hen de9ning your Receivables Activity;
*hen you enter a recei(t and combine it -ith a (ositive ad5ustment/ Receivables
creates the .ollo-ing 5ournal entries4
&%$IT Cash
CR%&IT Receivables 7Invoice8
&%$IT Receivables 7Invoice8
CR%&IT *rite=>
*hen you enter a recei(t and combine it -ith a Chargebac+/ Receivables creates
the .ollo-ing 5ournal entries4
&%$IT Cash
CR%&IT Receivables 7Invoice8
&%$IT Receivables 7Chargebac+8
CR%&IT Chargebac+ 7Activity8
&%$IT Chargebac+ 7Activity8
CR%&IT Receivables 7Invoice8
<ou set u( a Chargebac+ account -hen de9ning your Receivables Activity;
Remittances4
*hen you create a recei(t that re@uires remittance to your ban+/ Receivables debits
the Con9rmation account instead o. Cash; An e6am(le o. a recei(t re@uiring
remittance -ould be a chec+ be.ore it -as cashed; Receivables creates the
.ollo-ing 5ournal entry -hen you enter such a recei(t4
&%$IT Con9rmation
CR%&IT Receivables
<ou can then remit the recei(t to your remittance ban+ using one o. the t-o
remittance methods4 "tandard or Factoring; I. you remit your recei(t using the
standard method o. remittance/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Remittance
CR%&IT Con9rmation
*hen you clear the recei(t/ Receivables creates the .ollo-ing 5ournal entry4
&%$IT Cash
&%$IT $an+ Charges
CR%&IT Remittance
I. you remit your recei(t using the .actoring remittance method/ Receivables creates
the .ollo-ing 5ournal entry4
&%$IT Factor
CR%&IT Con9rmation
*hen you clear the recei(t/ Receivables creates a short=term liability .or recei(ts
that mature at a .uture date; The .actoring (rocess let you receive cash be.ore the
maturity date/ and assumes that you are liable .or the recei(t amount until the
customer (ays the balance on the maturity date; *hen you receive (ayment/
Receivables creates the .ollo-ing 5ournal entry4
&%$IT Cash
&%$IT $an+ Charges
CR%&IT "hort=Term &ebt
n the maturity date/ Receivables reverses the short term liability and creates the
.ollo-ing 5ournal entry4
&%$IT "hort=Term &ebt
CR%&IT Factor
Ad5ustments4
*hen you enter a negative ad5ustment against an invoice/ Receivables creates the
.ollo-ing 5ournal entry4
&%$IT *rite=>
CR%&IT Receivables 7Invoice8
*hen you enter a (ositive ad5ustment against an invoice/ Receivables creates the
.ollo-ing 5ournal entry4
&%$IT Receivables 7Invoice8
CR%&IT *rite=>
&ebit Memos4
*hen you enter a debit memo in the Transactions -indo-/ Receivables creates the
.ollo-ing 5ournal entries4
&%$IT Receivables
CR%&IT Revenue 7i. you enter line amounts8
CR%&IT Ta6 7i. you charge ta68
CR%&IT Freight 7i. you charge .reight8
&%$IT Receivables
CR%&IT Finance Charges
n=Account Credits4
*hen you enter an on=account credit in the A((lications -indo-/ Receivables
creates the .ollo-ing 5ournal entry4
&%$IT Revenue 7i. you credit line amounts8
&%$IT Ta6 7i. you credit ta68
&%$IT Freight 7i. you credit .reight8
CR%&IT Receivables 7n=account Credit8
Receivable uses the Freight/ Receivable/ Revenue/ and Ta6 accounts that you
s(eci9ed in your AutoAccounting structure to create these entries;
nce the on=account credit is a((lied to an invoice/ the .ollo-ing 5ournal entry is
created4
&%$IT Receivables 7n=account Credit8
CR%&IT Receivables 7Invoice8
$elo- (ost -ill (rovide you a @uery -hich lists the customers -ith o(en invoices;
Test Instance4 R30;3;3
/* Query to fetch summary data*/
SELECT hc.cust_account_id
,min(hc.account_number) customer_number
,sum(amount_due_remaining) amount_due_remaining
,sum(aps.amount_due_original) amount_due_original
,count(aps.payment_schedule_id) open_invoices
FROM ra_customer_trx_all ra,
ra_customer_trx_lines_all rl,
ar_payment_schedules_all aps,
ra_cust_trx_types_all rt,
hz_cust_accounts hc,
hz_parties hp,
hz_cust_acct_sites_all hcasa_bill,
hz_cust_site_uses_all hcsua_bill,
hz_party_sites hps_bill,
ra_cust_trx_line_gl_dist_all rct
WHERE ra.customer_trx_id = rl.customer_trx_id
AND ra.customer_trx_id = aps.customer_trx_id
AND ra.org_id = aps.org_id
AND rct.customer_trx_id = aps.customer_trx_id
AND rct.customer_trx_id = ra.customer_trx_id
AND rct.customer_trx_id = rl.customer_trx_id
AND rct.customer_trx_line_id = rl.customer_trx_line_id
AND ra.complete_flag = 'Y'
AND rl.line_type IN ('FREIGHT', 'LINE')
AND ra.cust_trx_type_id = rt.cust_trx_type_id
AND ra.bill_to_customer_id = hc.cust_account_id
AND hc.status = 'A'
AND hp.party_id = hc.party_id
AND hcasa_bill.cust_account_id = ra.bill_to_customer_id
AND hcasa_bill.cust_acct_site_id = hcsua_bill.cust_acct_site_id
AND hcsua_bill.site_use_code = 'BILL_TO'
AND hcsua_bill.site_use_id = ra.bill_to_site_use_id
AND hps_bill.party_site_id = hcasa_bill.party_site_id
AND hcasa_bill.status = 'A'
AND hcsua_bill.status = 'A'
AND aps.amount_due_remaining <> 0
AND aps.status = 'OP'
GROUP by hc.cust_account_id;
/*Query to fetch the detail info about a particular customers open invoices */
SELECT hp.party_name
,hc.cust_account_id
,hc.account_number customer_number
,amount_due_remaining amount_due_remaining
,aps.amount_due_original amount_due_original
,ra.trx_number
FROM ra_customer_trx_all ra,
ra_customer_trx_lines_all rl,
ar_payment_schedules_all aps,
ra_cust_trx_types_all rt,
hz_cust_accounts hc,
hz_parties hp,
hz_cust_acct_sites_all hcasa_bill,
hz_cust_site_uses_all hcsua_bill,
hz_party_sites hps_bill,
ra_cust_trx_line_gl_dist_all rct
WHERE ra.customer_trx_id = rl.customer_trx_id
AND ra.customer_trx_id = aps.customer_trx_id
AND ra.org_id = aps.org_id
AND rct.customer_trx_id = aps.customer_trx_id
AND rct.customer_trx_id = ra.customer_trx_id
AND rct.customer_trx_id = rl.customer_trx_id
AND rct.customer_trx_line_id = rl.customer_trx_line_id
AND ra.complete_flag = 'Y'
AND rl.line_type IN ('FREIGHT', 'LINE')
AND ra.cust_trx_type_id = rt.cust_trx_type_id
AND ra.bill_to_customer_id = hc.cust_account_id
AND hc.status = 'A'
AND hp.party_id = hc.party_id
AND hcasa_bill.cust_account_id = ra.bill_to_customer_id
AND hcasa_bill.cust_acct_site_id = hcsua_bill.cust_acct_site_id
AND hcsua_bill.site_use_code = 'BILL_TO'
AND hcsua_bill.site_use_id = ra.bill_to_site_use_id
AND hps_bill.party_site_id = hcasa_bill.party_site_id
AND hcasa_bill.status = 'A'
AND hcsua_bill.status = 'A'
AND aps.amount_due_remaining <> 0
AND aps.status = 'OP'
AND hc.cust_account_id =1847;
Thur s day/ Febr uar y A/ 0233
Oracle Receivables Transaction
Types R12
Below post will give details about Transaction Types in Oracle Receivables R12. We have consolidated the
information provided here from various sources and our self learning .

In which order Transaction types have to be defined?
1. Credit memo
2. nvoice
!. "ebit memo
#. Chargebac$
%. "eposit
&. 'uarantee
How to define Transaction types in Receivables?
Navigation:
Example Invoice Transaction Type Screen:
Example Credit MemoTransaction Type Screen:
etails abo!t the col!mns "iven in the above screens:
(ields escription
Class
Categori)e transaction types by assigning them to a
class of nvoice* Credit +emo* "ebit +emo* "eposit*
'uarantee* or Chargebac$. Transaction types are
displayed in windows as lists of values
Creation
,ign
-ositive* .egative* or /ny ,ign for initial sign of
transaction. -ositive re0uired for guarantees and
deposits
Transaction
,tatus
/ssign a status of Open* Closed* -ending* or 1oid to
this transaction
.ote2 When creating transactions via /utoinvoice*
even if you use a transaction type that is setup with
Transaction ,tatus 3 Closed* once the data is
interfaced* it will have an O-4. status.
5/utoinvoice does not provide a feature to interface
C6O,4" or .CO+-64T4 transactions7.
-rinting
Option
,pecify whether to print transactions with this
transaction type
Terms
default payment terms for this transaction* this field
is disabled when Class is Bills Receivable or Credit
memo
Open
Receivable
,elect this chec$ bo8 to have transactions update
customer balances and aging reports. Re0uired for
deposits and guarantees. This simply indicates
whether this transaction9s balance impacts a
Customer9s Receivable balance
-ost to '6
,elect this chec$ bo8 to post transactions with this
transaction type to the Oracle 'eneral 6edger.
Re0uired for deposits and guarantees
/llow
(reight
indicates whether or not you can associate freight to
this transaction type
"efault
Ta8
Classification
defaults ta8 classification code for this transaction.
This value is only relevant in release 11.% or a release
12 instances that are using 4:business ta8 setups
defaulted from an upgraded release 11.% instance
.atural
/pplication
Only
Restrict the direction in which invoices* debit memos*
deposits* guarantees* credit memos* and on:account
credits can be updated by applications entered against
them.
.atural application does not apply to ad;ustments and
chargebac$s. f .atural /pplication Only is selected*
clear the /llow Overapplication chec$ bo8
/llow
Over
application
/llow items to be overapplied. Chec$ bo8 defaults to
cleared for guarantees and deposits. f this chec$ bo8
is selected* clear .atural /pplication Only chec$ bo8.
n other words* activities against this transaction can
cause the sign of the balance to change 48ample2 an
original positive amount <=1%>?* can change to
negative amount <:=%>? due to receipt applications
nteraction
between
5.atural
/pplication
Only7 and
5/llow
Over
application7
@#at!ral $pplication %nly& Chec'ed and
&$llow %verapplication& #ot Chec'ed
Oracle Receivables allows any application* other than
ad;ustments and chargebac$s* that reduces the
transaction amount toward or to )ero without
changing the sign of the transaction.
@#at!ral $pplication %nly& (nchec'ed and
&$llow %verapplication& Chec'ed or
(nchec'ed
Oracle Receivables allows any application that
reduces or increases the transaction* even if the
application changes the sign of the transaction.
Receivable
and
Revenue
accounts for all classes of transaction types
(reight
/ccount
if /llow (reight is selected and the transaction type
class is set to nvoice* "ebit +emo* Credit +emo* or
Chargebac$.
Clearing
/ccount
if the transaction type class is set to nvoice* "ebit
+emo* Credit +emo* or Chargebac$. The account
holds differences between the revenue amount and
selling price <pro:rated discounts from Oracle Order
4ntry?.
Anbilled
/ccount
if the transaction type class is set to nvoice* "ebit
+emo* Credit +emo* or Chargebac$. Ased when
billing in arrears
Anearned
/ccount
if the transaction type class is set to nvoice* "ebit
+emo* Credit +emo* or Chargebac$. Ased when
billing in advance.
Ta8 /ccount
if Ta8 Calculation is selected and the transaction type
class is set to nvoice* "ebit +emo* Credit +emo* or
Chargebac$
Loading
Home
Articles
Video Tutorials
Finance
Accounting
Account Payables
API's
Account Receivables
Cash Management
racle Payments
!eneral Ledger
"#$ L%&!%R ACC#'TI'!
"CM
Inventory
AL
Purchasing
rder Management
PM
i"u((liers
Technical
PL")L
")L
API's
racle Alerts
*or+,o-
#se.ul
"ho-ing more (osts -ith label AR; "ho- older (osts
"ho-ing more (osts -ith label AR; "ho- older (osts
Thur s day/ Febr uar y A/ 0233
Oracle Receivables Transaction
Classes
Below list will give you the different types of Transaction classes available in Oracle /pps Receivables. Breif
description was also given.
Class escription
nvoice Bill customers for products or services
Credit memo
Credit customers <On:account credits do not refer to specific
invoices.
"ebit memo
Bill customers for products or services that were not included on the
original invoice
"eposit Bill customers for contractual agreements
'uarantee
/ contractual agreement that is referenced by invoices <Bill
customers for the items on the invoice* not the guarantee.?
Chargebac$
/d;ust the remaining balance of an e8isting debit item to )ero* and
create a new debit item to bill customer for unpaid balance of
original
invoice.
Auto Loc+bo6 Inter.ace Processing in racle A((s
nce the loc+bo6 data is received .rom ban+s/ move it to a directory/ normally a
data directory; Control 9le -ill be (laced in BARCTP?bin? as a ;ctl 9le; nce can
customi:e the layout and ctl 9le by deciding -hat data you -ill be receiving and
-hat .ormat -ill be used;
Autoloc+bo6 has three ste(s4
Im(ort4 Reads the loc+bo6 data .rom ban+ 9le/ moving it to the loc+bo6 tables using
")LD loader scri(t;
Validation4 The validation (rogram chec+s data in the AutoLoc+bo6 tables .or
com(atibility -ith Receivables; nce validated/ the data is trans.erred into
)uic+Cash tables; At this (oint/ you can o(tionally @uery your recei(ts in the
)uic+Cash -indo- and change ho- they -ill be a((lied be.ore submitting the 9nal
ste(/ Post )uic+Cash;
Post )uic+Cash4 This ste( a((lies the recei(ts and u(dates your customersE
balances;
In the "ubmit Loc+bo6 Processing .orm4
F Chec+ = "ubmit Im(ort;
F %nter the GTransmission 'ameG .or this transmission 7!ive any suitable name
.or your transmission8; 'ote this name .or .uture use;
F For &ata 9le 9eld/ enter the data 9le name along -ith .ull (ath
F %nter the control 9le name;
F "elect the Transmission Format 'ame;
F Chec+ "ubmit Validation;
F "elect the a((licable Loc+bo6;
F Allo- Payment o. #nrelated Invoices H $etter not to chec+ this;
F %nter the a((ro(riate date in the !L &ate 7usually the de(osit date8; This -ill
usually de.ault to system date;
F "elect the Re(ort Format you -ish to use 7usually IAllE8;
F Chec+ = Com(lete $atches nly;
F Chec+ = "ubmit Post)uic+Cash;
F "ave;
The Loc+bo6 %6ecution Re(ort -ill indicate i. the data -as im(orted and validated; It
also lists the (ossible e6ce(tions and -hat they mean; I. the data .ails the im(ort/
the entire transmission .ails and -ill need to be run again;
Common errors -ould be -ith count and total amounts at the transmission/
Loc+bo6/ batch or at transaction level; <ou may use the Maintain Transmission data
.orm to correct many errors; "elect the GTransmission 'ameG o. the transmission
you -ish to 96 and start your @uery; <ou -ill see all o. the records that ma+e u( the
transmission/ along -ith the status .or each record; Position the cursor on the
record you -ish to correct and Clic+ on the $utton .or the data -ith the error;
Correct the error on the a((ro(riate (age/ and return to the 9rst .orm; Move to the
ne6t record to 96 and continue until you have corrected every error;
*e can continue the cycle o. correcting and validating the data until all records
have been Gtrans.erredG as indicated on the Loc+bo6 %6ecution Re(ort;
For re=running the validation/ return to submit Loc+bo6 Processing .orm;
F &o not chec+ = "ubmit Im(ort;
F %nter the GTransmission 'ameG you noted above;
F &o not chec+ = Allo- Payment o. #nrelated Invoices;
F "elect 7List8 the a((licable Loc+bo6;
F %nter the a((ro(riate date in the !L &ate 7usually the de(osit date8;
F Chec+ = "ubmit Validation;
F "elect 7List8 the Re(ort Format you -ish to use 7usually Re5ects only .or the
subse@uent (asses8;
F Chec+ = Com(lete $atches nly;
F &o not chec+ = "ubmit Post)uic+Cash; 7 Let us chec+ this -hen -hole
validation gets over and -e have (ro(er data8
F "ave;
*hen all records are Gtrans.erred/G they -ill be moved .rom the Loc+bo6 tables to
the tables used by )uic+Cash 7the Interim Cash Recei(t tables8;
To a((ly the recei(ts/ select the GTransmission 'ameG and Chec+ "ubmit
Post)uic+Cash;
Return to the "ubmit Loc+bo6 Processing .orm4
F &o not chec+ = "ubmit Im(ort;
F %nter the GTransmission 'ameG you noted above;
F &o not chec+ = "ubmit Validation;
F Chec+ = Com(lete $atches nly;
F Chec+ = "ubmit Post)uic+Cash;
F "ave;
A.ter recei(ts get created/ -e are allo-ed to ma+e changes through .orm also;
Loc+bo6 Inter.ace Processing in racle A((s H vervie- and Process Flo- !ra(hical
Re(resentation

vervie-4
*hat is Loc+bo6J
Loc+bo6 is a service .eatured in ban+s or other service com(anies -herein
customers -ill send the (ayments to the ban+ and recei(ts are immediately created
in oracle a((s;
*hat is Auto loc+bo6 in racle A((s ReceivablesJ
Auto loc+bo6 is a (rogram available in racle Receivables -hich hel(s you to im(ort
(ayments or recei(ts; In real -orld/ $an+s -ould (rovide data 9les -hich -ould
have in.ormation about the (ayments made by customers; Receivables auto=
loc+bo6 (rogram -ould hel( you in im(orting in.ormation .rom these data 9les into
your system;
*hat ty(ical Auto loc+bo6 transmissions doJ
A ty(ical Auto loc+bo6 transmission has various di>erent records/ each -ith relevant
data; Transmission/ Loc+bo6/ batch and recei(t are di>erent levels o. records it -ill
loo+ .or to (rocess the recei(ts; And at each level the validations -ill be done to
ensure the total transmission amount/ batch amount and total recei(t amount;
Counts at di>erent levels -ill be validated in the same -ay; Transmission also has
in.ormation about the ban+ account 7used -ith loc+bo68; Loc+bo6 data 9le has a
record ty(e that indicates the ty(e o. data the record has; racle (rovides a de.ault
layout but de(ending on the re@uirements -e can customi:e the layouts;
Process Flo-4 !ra(hical Re(resentation
&etail Processing "te(s is available in the belo- lin+4
htt(4??shareoraclea((s;blogs(ot;com?0233?20?auto=loc+bo6=inter.ace=(rocessing=
in;html
Tuesday/ February 3/ 0233
ARCR%C%IPTCAPICP#$;A((lyConCaccount 7 "cri(t to a((ly a recei(t on account 8
Payment Term Discounts
"ubmitted by Anonymous on Mon/ 32?32?0233 = 0A4K0
Tag4
Account Receivables ?
Receivables lets you give discounts to your customers when they pay for their debit items before
a certain date. Discounts are determined by the payment terms you assign to your customers. You
can also choose whether to allow discounts for partial payments and specify how you want
Receivables to calculate the discount on your invoices.
Earned and Unearned Discounts
Receivables lets you determine whether your customers can take earned and unearned discounts.
An earned discount is a discount you give to a customer who pays on or before the discount date
or within the discount grace period. For example, a customer may earn a ! discount off the
original invoice if payment is received within "# days. $he earned discount period is determined
by the invoice date, apply date of the receipt, and any discount grace days.
Receivables also lets you choose whether to allow unearned discounts. %nearned discounts are
discounts that you allow after the earned discount period has passed. &f the discount is unearned,
the default earned discount is 'ero and the maximum value of the unearned discount is dictated
by the payment terms. &f the discount is earned, the default discount is the amount of the earned
discount. Receivables lets you override the discount amount during payment entry and warns you
if you are taking an unearned discount. You specify whether your customers can take unearned
discounts in the (ystem )ptions window.
Discounts on Partial Payments
Receivables lets you choose whether to allow discounts when your customer remits partial
payment for an open debit item. &f you allow discounts on partial payments, Receivables prorates
the amount of the discount based on the applied amount. You can control whether your
customers can receive discounts for partial payments by setting the system option Discount on
*artial *ayment to Yes or
+o.
Tiered Discounts
,hen you define your payment terms, you can assign multiple discounts to each payment
schedule. You might want to assign different discount percents based on different discount dates.
For example, you might give your customers a "-! discount if they pay within "# days after the
invoice date, but only a -! discount if they pay within "- days.
Accounting Entries
L Automatic Recei(ts u( $ills Receivable M

$elo- scri(t -ill hel( you a((ly a recei(t on account using the API
ARCR%C%IPTCAPICP#$;A((lyConCaccount;
This scri(t -as tested in R30;3;3 instance;
"cri(t4
set serverout(ut onN
&%CLAR%
vCreturnCstatus VARCHAR0738N
vCmsgCcount '#M$%RN
vCmsgCdata VARCHAR070K28N
vCcount '#M$%RN
vCrecei(tCnumber VARCHAR070K28 4O '"HAR%RACL%APP"'N
vCorgCid '#M$%R 4O PAN
(Ccount '#M$%RN
vCconte6t varchar073228N
F#'CTI' setCconte6t7 iCuserCname I' VARCHAR0
/iCres(Cname I' VARCHAR0
/iCorgCid I' '#M$%R8
R%T#R' VARCHAR0
I"
vCuserCid '#M$%RN
vCres(Cid '#M$%RN
vCres(Ca((lCid '#M$%RN
vClang VARCHAR073228N
vCsessionClang VARCHAR0732284O.ndCglobal;currentClanguageN
vCreturn VARCHAR073284O'T'N
vCnlsClang VARCHAR073228N
vCorgCid '#M$%R4OiCorgCidN
?D Cursor to get the user id in.ormation based on the in(ut user name D?
C#R"R curCuser
I"
"%L%CT userCid
FRM .ndCuser
*H%R% userCname O iCuserCnameN
?D Cursor to get the res(onsibility in.ormation D?
C#R"R curCres(
I"
"%L%CT res(onsibilityCid
/a((licationCid
/language
FRM .ndCres(onsibilityCtl
*H%R% res(onsibilityCname O iCres(CnameN
?D Cursor to get the nls language in.ormation .or setting the language conte6t D?
C#R"R curClang7(ClangCcode VARCHAR08
I"
"%L%CT nlsClanguage
FRM .ndClanguages
*H%R% languageCcode O (ClangCcodeN
$%!I'
?D To get the user id details D?
P%' curCuserN
F%TCH curCuser I'T vCuserCidN
IF curCuserQ'TF#'&
TH%'
vCreturn4O'F'N

%'& IFN
CL"% curCuserN
?D To get the res(onsibility and res(onsibility a((lication id D?
P%' curCres(N
F%TCH curCres( I'T vCres(Cid/ vCres(Ca((lCid/vClangN
IF curCres(Q'TF#'&
TH%'
vCreturn4O'F'N

%'& IFN
CL"% curCres(N

&$M"C#TP#T;P#TCLI'% 7vCuserCidRR' ' RRvCres(CidRR ' ' RRvCres(Ca((lCid8N
?D "etting the oracle a((lications conte6t .or the (articular session D?
.ndCglobal;a((sCinitiali:e 7 userCid OS vCuserCid
/res(Cid OS vCres(Cid
/res(Ca((lCid OS vCres(Ca((lCid8N
?D "etting the org conte6t .or the (articular session D?
moCglobal;setC(olicyCconte6t7'"'/vCorgCid8N
?D setting the nls conte6t .or the (articular session D?
IF vCsessionClang TO vClang
TH%'
P%' curClang7vClang8N
F%TCH curClang I'T vCnlsClangN
CL"% curClangN
.ndCglobal;setCnlsCconte6t7vCnlsClang8N
%'& IFN ==IF vCsessionClang TO vClang
R%T#R' vCreturnN
%UC%PTI'
*H%' TH%R" TH%'
R%T#R' 'F'N
%'& setCconte6tN
$%!I'
&$M"C#TP#T;P#TCLI'%7'3'8N
==3; "et a((lications conte6t i. not already set;
vCconte6t 4O setCconte6t7'Vuserid'/'Vres(onsibility'/'VorgCid'8N
IF vCconte6t O 'F'
TH%'
&$M"C#TP#T;P#TCLI'%7'%rror -hile setting the conte6t'8N
%'& IFN
&$M"C#TP#T;P#TCLI'%7'0'8N
MC!L$AL;init7'AR'8N
ARCR%C%IPTCAPICP#$;A((lyConCaccount
7 (Ca(iCversion OS 3;2/
(CinitCmsgClist OS F'&CAPI;!CTR#%/
(Ccommit OS F'&CAPI;!CTR#%/
(CvalidationClevel OS F'&CAPI;!CVALI&CL%V%LCF#LL/
6CreturnCstatus OS vCreturnCstatus/
6CmsgCcount OS vCmsgCcount/
6CmsgCdata OS vCmsgCdata/
(Crecei(tCnumber OS vCrecei(tCnumber/
(CorgCid OS vCorgCid
8N
IF vCreturnCstatus O '"' TH%'
&$M"C#TP#T;(utCline7'Recei(t a((lied on account '8N
%L"%
&$M"C#TP#T;(utCline7'Message count ' RR vCmsgCcount8N
IF vCmsgCcount O 3 TH%'
&$M"C#TP#T;(utCline7'vCmsgCdata 'RRvCmsgCdata8N
%L"IF vCmsgCcount S 3 TH%'
LP
(Ccount 4O (CcountW3N
vCmsgCdata 4O F'&CM"!CP#$;!et7F'&CM"!CP#$;!C'%UT/F'&CAPI;!CFAL"%8N
IF vCmsgCdata I" '#LL TH%'
%UITN
%'& IFN
&$M"C#TP#T;(utCline7'Message' RR (Ccount RR'==='RRvCmsgCdata8N
%'& LPN
%'& IFN
%'& IFN
%'&N
?