Skip to main content

Payables Payment Terms Functionality

How Payment Terms Work And What Is The Functionality Of Payment Terms When ?

The Payment Terms defined works on three basic fields on which you have entered/defined information.
The below combinations along with Invoice date defaults your Invoice Due Date.
In the Define Payment terms screen

Method 1)
---------
Invoice Date and No of Days entered in Payment term Days field

a) Days

Say, Invoice date is 28-Nov-2001 then if you enter 60 days then due date will be 27-Jan-2001. 
It means it calculates no of days from the Invoice date. 

Method 2)
---------
Invoice Date + Cut Off day + Day of month with Months ahead. 

1) Cut-off Day
2) Day of Month with Months ahead

For example :

If you enter Payment Terms like this:
Cut of day 31 (Last day of a Month) Means even though invoice is 28th 1st what so ever, 
it calculates from the last day of month.

Day of a month  29
Months ahead    2   ( Two Months)

If invoice is dated 28-Nov-2001, with the above setup you get Due date as 29-Jan-2001 as due date.

It will always calculate from the End of Nov ie 30th Nov and Then it takes Two Months here it gives you always 29th of Second month from Invoice date.

ie

Invoice Date            Due Date

28-Nov-2001             29-Jan-2002
28-Dec-2001             28-Feb-2002
28-Jan-2002             29-Mar-2002

So on and so forth.

Either you give 29th or 30th what so ever, once you give the Day of Month you will get only that day as due date after Months specified in the Months ahead field.

This is how application works and designed to work.

Please refer documentation for the following terms

Cutoff Day.
Days.
Day of Month
Months Ahead.

Further,
In case, you have  two invoice payment terms which you are not able to define in AP and the due dates are not defaulting as expected;

The two terms are:-

(1) 60 DAYS END OF MONTH go to month end and add 60 days
E.G: invoice dated 28 NOV, due date is 29 JAN

(2) 90  DAYS END OF MONTH go to month end and add 90 days
 E.G: invoice dated 28 NOV,  due date is 28 FEB

How would you define these?

The Payment Terms functionality does not support the above example

Comments

Post a Comment

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  
Post a Comment
Read more

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l
Post a Comment
Read more

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table
Post a Comment
Read more