Discounts ,discount grace periods in oracle apps r12 ,account receivable Setup Payment Terms

 

Discounts:

Current State

At present Vista uses a billing extension for the purposes of generating revenue and invoices.  However, Vista also has customers for which they apply discounts.  Due to the implementation of the billing extension the standard Discount functionality is not available therefore, the coding for the extension needs to be updated to take the discounts into account.

Approach

The billing extension will be modified to identify if a discount has been assigned on the project per the screen shots below:

 When a labor discount is identified the revenue and invoice amounts will be reduced by the amount of the discount.


 

Standard Process in Oracle Receivables

1. Overview

Receivables lets you apply discounts to your customers when they pay for their invoices 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 Discount: 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 2% discount on the original invoice if payment is received within 10 days. The earned discount period is determined by the invoice date, apply date of the receipt and any discount grace days.

When determining the discount percent for earned discounts, Receivables uses the invoice date, discount grace days, and the apply date of the receipt to determine the discount percentage for this payment term

Unearned Discount: Unearned discounts are discounts that you allow after the earned discount period has passed. The default discount taken is zero if the discount is unearned.

When determining the discount percent for unearned discounts, Receivables uses the maximum discount allowed for this payment term. To allow unearned discounts, set Allow Unearned Discounts to Yes in the System Options window

Entering Discounts:



Formulas Used to Calculate Discounts

Maximum Discount
Use the following formula to determine the maximum discount amount:
Maximum Discount = Amount Due Original * Highest Discount Percent - Discount Taken

Earned Discounts and Partial Payments Allowed

If the receipt amount is more than the amount due remaining less the discount, Receivables uses the following formula to determine the earned discount:
Earned Discount = Amount Due Remaining * Discount Percent
If the receipt amount is either the same or less than the amount due remaining less the discount, Receivables uses the following formula to determine the earned discount:
Earned Discount = (Receipt Amount * Discount Percent) / 1 - Discount Percent.

 

Unearned Discounts with Partial Payment Discounts Allowed
Receivables use the following formula to determine unearned discounts if partial payments are allowed:
Unearned Discount = Maximum Discount - Earned Discount

Earned Discounts with Partial Payment Discounts Not Allowed
If the Allow Discount on The partial Payments check box for your payment terms is not checked, Receivables only takes discounts if the receipt amount closes the installment
Receivables use the following formula to determine earned discounts if partial payment discounts are not allowed:
Earned Discount = Amount Due Original * Discount Percent

Unearned Discounts and Partial Payments Not Allowed
If the Allow Discount on Partial Payments check box for your payment terms is not checked, Receivables only takes discounts if the receipt amount closes the installment.
Receivables use the following formula to determine unearned discounts if partial payments are not allowed:
Unearned Discount = Amount Due Original * Maximum Discount Percent - Earned Discount

Discount on Lines Only
If the Discount Basis option for your payment term is set to Lines Only, Receivables does not take discounts on receipt amounts applied to tax, freight, or late charges and uses the following formula to determine the discount amount:
Line Percent = Discount Percent * (Sum of Lines + Sum of Line Adjustments - Sum of
Line Credits / Amount Due Original + Sum of Adjustments - Sum of Credits)
Once you determine the discount line percent, use this as the discount percent in the formulas above.

2. Setup for Discounts

2.1. Setup Payment Terms

Define your payment terms in the Payment Terms window. Enter a discount percent, choose whether to allow discounts on partial payments and select a discount basis.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Payment Terms

Define your payment terms in the Payment Terms window. Enter a discount percent, choose whether to allow discounts on partial payments and select a discount basis.

Click the Discounts push button


2.2 Setup System Options

Choose whether to allow partial and unearned discounts in the System Options window.

Responsibility:
 Receivables Manager
Navigation: Setup > System > System Options > Miscellaneous tab


In Vision demo instance:

 


 

2.3 Define earned and unearned discount accounts

Define your earned and unearned discount accounts in the Bank Accounts window

Responsibility:
 Receivables Manager
Navigation: Setup > Receipts >Receipt Classes > Query the class
Choose the Receipt Method >  
Click Bank Accounts to navigate to Remittance Bank Accounts window
In the GL Accounts tab
Earned and Unearned discounts are the receivable activities that need to be selected here

2.4 Setup Customer to allow discounts

Choose whether to allow discounts and assign discount grace days to your customers in the Customer Profile Classes window or the Profile: Transaction tabbed region of the Customers window.
The values you define in the Customers window take precedence over those in the Customer Profile Classes window.

Responsibility: Receivables Manager
Navigation: Customer > Profile Classes

3. Defaulting Discount Amounts

When entering receipts manually, Receivables determines whether discounts are allowed based on the payment terms, discount grace days, system options, transaction date, and receipt apply date. If discounts are allowed, Receivables determines the amount of earned and unearned discounts and displays this information in the Discount field.

Receivables defaults applied receipt amounts into the receipt application windows. The default amount applied is the remaining amount of the transaction, less any available discount. However, if the remaining amount of the receipt is less then the balance of the transaction, the default amount applied is the remaining amount of the receipt and Receivables takes the discount available on the transaction.


 

Discounts are calculated based on the following setups:

1. Payment Term with Billing Cycle Assigned.
2. Payment Term without a Billing Cycle.

Discount Date calculation:
Code Used: AR_TRX_DISCOUNTS_V

1. Payment Term with Billing Cycle Assigned.

The discount date is calculated based on the Billing Date.
This is true whether the customer/customer site/transaction is enabled for Balance Forward Billing or not.

Example:
A.
   Create payment term: Due15th, Cut25
   Billing Cycle (Cutoff-day) 
                          -- Day of Month: 25

   Payment Schedule 
                           -- Day of Month: 15
                           -- Months Ahead: 1

   Discount            
            --  Day of Month: 01
                           --  Months Ahead: 1
                           --  Percent : 10

case 1(Discount to be calculated based on billing date):

    Transaction created with 
          Trx_date         : 26-JUN-2015
          Billing_date     : 25-JUL-2015
          Due_date        : 15-AUG-2015  
          Discount_date  : 01-AUG-2015 

case 2(Discount to be calculated based on billing date):

    Transaction created with 
        Trx_date    : 24-JUN-2015
          Billing_date    : 25-JUN-2015
          Due_date       : 15-JUL-2015  
          Discount_date : 01-JUL-2015 

B.
   Create payment term: Due15th,Cut25
   Billing Cycle (Cutoff-day) 
                           -- Day of Month: 25

   Payment Schedule 
                           -- Day of Month: 15
                           -- Months Ahead: 1

   Discount            
                           --  Days     : 10
                           --  Percent     : 10


    Transaction created with 
        Trx_date    : 26-JUN-2015
          Billing_date    : 25-JUL-2015
          Due_date    : 15-AUG-2015  
          Discount_date    : 04-AUG-2015 

2. Payment Term without Billing Cycle

The discount date is calculated based on the Transaction Date.


Example:
A.
   Create payment term: Due15th

   Payment Schedule 
                           -- Day of Month: 15
                           -- Months Ahead: 1

   Discount            
                           --  Day of Month: 01
                           --  Months Ahead: 1
                           --  Percent : 10

case 1(Discount to be calculated based on Trx_date):
     Transaction created with 
          Trx_date         : 26-JUN-2015
          Due_date        : 15-JUL-2015  
          Discount_date  : 01-JUL-2015 



case 2(Discount to be calculated based on Trx_date):
--------------------------------------------------------
    Transaction created with 
         Trx_date          : 24-JUN-2015
          Due_date        : 15-JUL-2015  
          Discount_date  : 01-JUL-2015 

B.
   Create payment term: Due15th

   Payment Schedule 
                           -- Day of Month: 15
                           -- Months Ahead: 1

   Discount            
                           --  Days     : 10
                           --  Percent     : 10


    Transaction created with 
          Trx_date       : 26-JUN-2015
          Due_date      : 15-JUL-2015  
          Discount_date: 04-JUL-2015 

 

 


 

Discount Rounding calculated for earned Discounts for Receipts within Oracle Receivables.

The example below, which will explain how Discount Rounding is calculated

Following are the terms:

1. Payment Terms/Discount on line -3% (days 30)
2. Tax rounding in system options -nearest/precision 2
3. Customer discount at site level-Allow discount (checked), grace days 0.
4. Tax inclusive rate 7 %
.
Casse1:
1.Create a transaction of line 1346.17, tax calculates to 94.23
2.Create a receipt of 1400.01
3.Apply receipt to invoice.
4. Before saving, the discount amount is 40.39 (40.385) -Rounded Up-
.
Case 2:
1.Create a transaction of line 5025.5, tax calculates to 351.79
2.Create a receipt of 5377.29
3.Apply receipt to invoice.
4. Before saving, the discount amount is 150.76 (150.765). -Rounded Down-


The reason behind the discounts being rounding to different sides in the above cases is due to the fact that system also takes the division of the line amount by the total invoice amount and amount due remaining into account while doing discount calculation. In the two test cases above there is a difference in the in the interim calculations due to which the final values are coming different.

This is how it is getting calculated in these two test cases (short names used):

Case 1:
L1: 1346.17 T1: 94.23, amt due remaining = 1440.4
l_multiplier = 1346.17/1440.4 = 934580672
disc pct = .03 , earned disc pct = 0.03 * 934580672 = .02803742016
Now earned discount uses amt due remaining in its calculation here:
earned discount = earned disc pct * amount due remaining.
so it is = .02803742016 * 1440.4 = 40.385099998464
This rounded off to 40.39 standard PL-SQL ROUND function.

 

 


Case 2:
L1: 5025.5 , T1: 351.79 , amt due remaining = 5377.29
l_multiplier : 5025.2/5377.29 = .9345785702
disc pct = .03 , earned disc pct = 0.03 * .9345785702 = .028037357106
Here the earned discount comes to be :
.028037357106 * 5377.29 = 150.76499999252274 which now finally Rounds to 150.76.
Hence the difference. So there may be differences due to difft l_multiplier values and its
product with amount due remaining values.

To add conclusion to above discussion, the discount calculation does not takes into account any
rounding rule defined anywhere, whether in the system options or in the currency details. The rounding rule which is defined in the system options is for TAX rounding and has nothing to do with discounts. So there is no such rule that discount should only round in any particular direction- up or down or nearest. It takes final value depending upon above calculations.

 

The following table’s stores discount amount information:

Similar to AP in AR the AR_PAYMENT_SCHEDULES_ALL table captures the discount details

 

ZX_LINES_DET_FACTORS.CASH_DISCOUNT

 

AR_RECEIVABLE_APPLICATIONS_ALL.LINE_EDISCOUNTED

AR_RECEIVABLE_APPLICATIONS_ALL.ACCTD_EARNED_DISCOUNT_TAKEN

AR_RECEIVABLE_APPLICATIONS_ALL.EARNED_DISCOUNT_TAKEN

 

AR_PAYMENT_SCHEDULES_ALL.DISCOUNT_REMAINING      

AR_PAYMENT_SCHEDULES_ALL.DISCOUNT_TAKEN_EARNED

Oracle apps r12 topic wise links

 

1)      https://www.oracleapps2fusion.com/2014/02/orader-to-cash-o2c-r12.html

2)      https://www.oracleapps2fusion.com/2014/02/rank-denserank-first-and-last-analytic.html

3)      https://www.oracleapps2fusion.com/2014/02/r12-tca-trading-community-architecture.html

4)      https://www.oracleapps2fusion.com/2014/02/sales-order-api-conversion.html

5)      https://www.oracleapps2fusion.com/2014/02/item-conversion-through-api.html

6)      https://www.oracleapps2fusion.com/2014/02/ar-receipt-creation-in-receivables-r12.html

7)      https://www.oracleapps2fusion.com/2014/02/xml-bursting.html

8)      https://www.oracleapps2fusion.com/2014/03/fndload-to-transfer-aol-objects-from.html

9)      https://www.oracleapps2fusion.com/2014/03/shell-script-tutorial.html

10)   https://www.oracleapps2fusion.com/2014/03/p2p-query-in-oracle-apps-r12.html

11)   https://www.oracleapps2fusion.com/2014/03/concurrent-program-whose-output-has-to.html#

12)   https://www.oracleapps2fusion.com/2014/03/register-executable-from-back-end.html

13)   https://www.oracleapps2fusion.com/2014/03/concurrent-program-whose-output-has-to.html

14)   https://www.oracleapps2fusion.com/2014/04/o2c-query.html

15)   https://www.oracleapps2fusion.com/2014/04/unable-to-open-report-builder-11g.html

16)   https://www.oracleapps2fusion.com/2014/04/purchase-order-report.html

17)   https://www.oracleapps2fusion.com/2014/04/ar-query.html

18)   https://www.oracleapps2fusion.com/2014/04/drop-ship-query.html

19)   https://www.oracleapps2fusion.com/2014/04/oracle-apps-faq.html

20)   https://www.oracleapps2fusion.com/2014/04/xml-publisher-tips.html


Introduction To Fusion Application



Introduction with these Five topics 



1) Oracle fusion application
2) cloud computing
3) On premises vs cloud
4) Cloud Options for customers
5) What are the new Features in Oracle cloud





Oracle Journey from   Database to Fusion cloud application



INTRODUCTION TO ORACLE FUSION CLOUD SERVICES

By going through this small write up, readers will understand about Oracle Fusion cloud and what are different challenges for oracle to implement the same in future. Also we will briefly understand oracle’s future strategy for Cloud services.

Over the past several years, there been a lot of talk regarding Oracle Fusion and many people struggle to understand what exactly this means. Fusion refers to Oracle’s Cloud infrastructure (Fusion Middleware) and the development of new applications specifically designed for the Cloud and subscription services. More recently, Oracle has focused communications on the business process value and business use of these applications and now refers to these applications and underlying technology simply as “Cloud”.


What are challenges for Oracle?
According to recent survey by Forrester Oracle has underperformed with its Oracle Fusion Applications. As customers are refusing to switch to the more expensive Fusion apps and Oracle customers are making it difficult for the company to grow application revenue.

As of now, 65% had no plans to move to Fusion Applications and another 24% were on the fence. The biggest barriers were Oracle’s muddled application strategy and the immaturity of Fusion, which became available in November 2011. Oracle has experienced low level of user adoption of its Fusion Applications, the next-generation enterprise application suite.
Recent acquisitions of software-as-a-service companies, such as Taleo and RightNow Technologies, are not bringing in enough revenue and customers showed little interest in trying the SaaS products, with only 11% of survey respondents interested in making the move. Oracle is in danger of losing business from some of its customers. Forrester found 29% of the companies it polled were planning to move to another vendor’s SaaS product or packaged application. The main reasons for their unhappiness with Oracle were high licensing costs, high maintenance costs and difficulty in upgrading.

What is Future Plan?
Oracle has invested heavily (both in terms of money and resource) in Fusion middleware and applications and this is one of the biggest areas of growth for the company and will not allow their customers to ignore them. At the same time Oracle will not allow Applications Unlimited customers to stay where they are forever.
Oracle will focus more on customers to move to Fusion or its cloud infrastructure products in near future. Soon or later customers will start feeling pressure from Oracle that stay with the older technology.
Fusion Applications are their main strategy for growing software revenue and defending against a number of fast-growing SaaS competitors. Oracle’s cloud offering of HCM [human capital management], CRM [customer relationship management] and ERP [enterprise resource planning] applications is the strongest and most complete in the industry.

Deploying Oracle Application on the Cloud
Cloud infrastructure is appealing to almost all IT organizations as these are scalable, reliable, secure and cost-effective. Oracle is not recommending customers to shift their Production environments to the Cloud right away, to make this process easier, Oracle has even published machine images of E-Business Suite 12.2.5, JD Edwards Enterprise One 9.2, and PeopleSoft HCM 9.2 on the Oracle Cloud Marketplace to create instances of these applications on the Oracle Cloud.

Customers will save lots of time by deploying an image from the Marketplace instead of the usual process of downloading and staging software, installing and configuring, etc. Once you have deployed the software in the cloud, you can use environments to create setups, test new functionality, implement business flows and conduct POCs or CRPs. For existing Apps Unlimited customer, they can also migrate Dev or Test environments to Oracle Cloud.
Under Oracle Applications Unlimited, Oracle continuously innovates the current applications and will also delivered the next generation of Cloud applications.
Oracle Cloud is the most integrated public cloud and offers best-in-class services across software as a service (SaaS), platform as a service (PaaS), and infrastructure as a service (IaaS). Oracle Cloud helps organizations drive innovation and business transformation by increasing business agility, lowering costs, and reducing IT complexity.

Conclusion
Broadly, Oracle Fusion applications were divided into four software categories-
1 Customer relationship management
2. Human capital management
3. Enterprise resource planning
4. Supply chain management.

Current Cloud Applications suite includes CRM; Financials; Governance, Risk, and Compliance; HCM; Procurement; Project Portfolio Management; and SCM and within each of these groups, there are sub-categories that provide companies multiple layers of services and modules.
These applications are being delivered through the Oracle Cloud in addition to on-premises setups. The Cloud application suite had rapidly gained momentum and there was new functionality being added regularly – with major releases up to three times per year.

Oracle Fusion Financials

The purpose of this blog , is to do Knowledge sharing with my Followers through my own Experiences. Do your comments , feedback and your suggestions to keep this going    


Thanks
Mungi