Earned and unearned discounts - 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.

Types of discounts

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 2% discount off 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.

Receivables also lets you choose whether to allow unearned discounts. 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. If the discount is earned, the default discount taken is the amount of the earned discount. Receivables lets you override the discount taken amount during payment entry and warns you if you are taking an unearned discount.

Discounts on Partial Payments

Receivables lets you choose whether to allow discounts when your customer remits partial payment for an open debit item. If you allow discounts on partial payments, Receivables prorates the amount of the discount based on the receipt amount. You can control whether your customers can receive discounts for partial payments by setting the system option Discount on Partial Payment to Yes or No.


Tiered Discounts

When 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 15% discount if they pay within 10 days after the invoice date, but only a 5% discount if they pay within 15 days.

Comments

Post a Comment

Popular posts from this blog

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR
Read more

How to use lexical parameters in Data template (XML document) R12

Lexical parameters can be added in data definition using &variable name This is flexible variable string where you can execute runtime conditions based on user-inputs Example 1. Append &gc_journal_filter at the end of sql statement 2. Define beforereport function in package signature FUNCTION beforereport RETURN BOOLEAN; 3. Define all the report parameters as a package variable in package signature including lexical parameters 4. Implement beforereport function by building your runtime conditions to be added to SQL statements  FUNCTION beforereport RETURN BOOLEAN IS  BEGIN          IF p_journal_source IS NULL THEN       gc_journal_filter := ' AND jh.je_source IN (''AutoCopy'',''Manual'')';     END IF;          IF p_journal_category IS NULL THEN       gc_journal_filter := 'AND jh.je_category IN (''Other'') ';     END IF;    RETURN TRUE;  END;
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra
Read more