Maturity Date On Bill Payable Payment Is Incorrect

(Doc ID 1956497.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Payables - Version 12.1.3 and later
Information in this document applies to any platform.


When calculating the Maturity Date for Bill Payments Including Credit Memos the Due Date or Discount Date of the Credit Memo is also included for consideration.


Example Case


In the Build Payments Log File find...

 IBY_PAYGROUP_PUB.performMaturityDateCalculation:Earliest available due date
 for payment 242792 is 22-AUG-14
 IBY_PAYGROUP_PUB.performMaturityDateCalculation:Setting maturity date to due
 date 22-AUG-14 for payment 242792 because no discount date available.

In the Check_iby Diagnostic find Payment 242792

The Payment Shows

08-AUG-2014 00:00    22-AUG-2014 00:00     02-JUL-2014 00:00

It pays the following documents.

546577 01-OCT-2014 00:00 s*
546578 01-DEC-2014 00:00 s*
546579 15-NOV-2014 00:00 s*
546580 31-JUL-2014 00:00 c
546581 06-AUG-2014 00:00 s
546583 01-OCT-2014 00:00 s*
546584 04-AUG-2014 00:00 s
546585 02-AUG-2014 00:00 c
546586 30-NOV-2014 00:00 s*
546587 02-OCT-2014 00:00 s*
546588 09-JUL-2014 00:00 c
546591 30-SEP-2014 00:00 s*
546592 05-OCT-2014 00:00 s*
547573 22-AUG-2014 00:00 c*
546589 15-OCT-2014 00:00 s*
546590 02-JUL-2014 00:00 c

s = standard invoice
c = credit memo
* = Due Date > Payment Date

Therefore the MATURITY DATE has been taken from INVOICE_ID = 547573 which is
a Credit Memo.

It would seem that the Payment Due Date is set to be the Oldest Due Date and
then the Maturity Date is the first due date after the payment date,
irrespective of whether it is a standard invoice or a credit memo.



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms